Skip to content
TrustedSkillsbeta
Back to all skills

Electron Architect

Checked
tomlord1122·vlatest·frontend

Designs optimal molecular structures and predicts material properties based on electron configuration data.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tomlord1122/tomtom-skill --skill electron-architect -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tomlord1122

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tomlord1122/tomtom-skill at bfa41ed48c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
bfa41ed48c
Manifest
skills/electron-architect/SKILL.md
Scanned
2 files, 791 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in designing Electron desktop application architectures, focusing on security best practices and efficient communication between processes. It guides users through a structured process of analyzing application requirements, designing a secure Main/Renderer architecture, and establishing safe Inter-Process Communication (IPC). The goal is to create robust and secure Electron applications by carefully considering resource access, user interaction patterns, data sensitivity, and IPC design.

When to use it

  • When starting a new Electron desktop application project.
  • To review the security of an existing Electron application's architecture.
  • For designing complex IPC communication between the Main and Renderer processes.
  • When needing guidance on how to handle file system access, network requests, or native dialogs within an Electron app.
  • To ensure adherence to security principles like least privilege and defense in depth.

Key capabilities

  • Application Requirements Analysis: Identifies core functionality, resource needs, target platforms, offline requirements, and data sensitivity levels.
  • Architecture Design (Security First): Provides a framework for designing secure Main/Renderer architectures based on security principles.
  • IPC Design: Guides the selection of appropriate IPC patterns (invoke/handle, send, webContents.send, MessagePort) and emphasizes input validation and explicit communication channels.
  • Decision Point Guidance: Provides structured questions to guide architectural decisions regarding process access and IPC surface area.

Example prompts

  • "I'm building an Electron app that needs file system access. How should I handle this securely?"
  • "What are the best practices for designing IPC communication between the Main and Renderer processes in my Electron application?"
  • "My Electron app requires network requests; where should these be handled, and how can I avoid CORS issues?"

Tips & gotchas

  • The skill follows a structured three-step process (Requirements Analysis -> Architecture Design -> IPC Design). Follow the steps sequentially for best results.
  • Security is paramount: The skill prioritizes security principles like least privilege throughout the design process.
  • Pay close attention to the "Architecture Decision Matrix" and "IPC Security Checklist" for guidance on specific features and communication patterns.