Desktop Electron
OpenHands/OpenHands
This skill should be used when the user asks to "change the desktop app", "package Electron", "build a universal macOS app", "bundle Node or uv", "fix Electron startup", or changes electron/…
Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method.
Apache-2.0Auto-check passed
Install Electron Candidate Discovery
$ npx skills add SpecterOps/skills --skill electron-candidate-discovery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SpecterOps/skills electron-candidate-discovery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/payloads/skills/electron-candidate-discovery .claude/skills/electron-candidate-discovery && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "electron-candidate-discovery" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discovery into .claude/skills/electron-candidate-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-candidate-discovery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discoveryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SpecterOps/skills --skill electron-candidate-discovery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SpecterOps/skills electron-candidate-discovery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/payloads/skills/electron-candidate-discovery .agents/skills/electron-candidate-discovery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "electron-candidate-discovery" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discovery into .agents/skills/electron-candidate-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-candidate-discovery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpecterOps/skills --skill electron-candidate-discovery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SpecterOps/skills electron-candidate-discovery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/payloads/skills/electron-candidate-discovery .cursor/skills/electron-candidate-discovery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "electron-candidate-discovery" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discovery into .cursor/skills/electron-candidate-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-candidate-discovery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SpecterOps/skills.git --path plugins/payloads/skills/electron-candidate-discovery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SpecterOps/skills --skill electron-candidate-discovery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SpecterOps/skills electron-candidate-discovery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/payloads/skills/electron-candidate-discovery .gemini/skills/electron-candidate-discovery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "electron-candidate-discovery" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discovery into .gemini/skills/electron-candidate-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-candidate-discovery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SpecterOps/skills electron-candidate-discoveryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SpecterOps/skills --skill electron-candidate-discovery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/payloads/skills/electron-candidate-discovery .github/skills/electron-candidate-discovery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "electron-candidate-discovery" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discovery into .github/skills/electron-candidate-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-candidate-discovery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpecterOps/skills --skill electron-candidate-discovery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SpecterOps/skills electron-candidate-discovery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpecterOps/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/payloads/skills/electron-candidate-discovery .opencode/skills/electron-candidate-discovery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "electron-candidate-discovery" agent skill from https://github.com/SpecterOps/skills/tree/main/plugins/payloads/skills/electron-candidate-discovery into .opencode/skills/electron-candidate-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "electron-candidate-discovery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
electron-candidate-discovery- GitHub stars
- 702
- Token cost
- ~287 tokens
- SKILL.md length
- 112 words
- Files
- 4 (incl. assets)
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method.
- Building an actionable shortlist of candidate apps rather than a broad inventory
- SKILL.md covers Goal, For Each Candidate Include, Selection Bias and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Electron Candidate Discovery is an agent skill from SpecterOps/skills. Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method. Use when building an actionable shortlist of candidate apps rather than a broad inventory.
Its SKILL.md is about 290 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including assets (for example `agents/openai.yaml`).
The repository describes itself as: A marketplace for LLM skills. The licence is Apache-2.0.
When your agent uses it
- Building an actionable shortlist of candidate apps rather than a broad inventory
Example prompts
- “/electron-candidate-discovery”
What it can do on your machine
Read from SKILL.md and the folder at commit e655f93. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Electron Candidate Discovery loads about 287 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 112 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SpecterOps/skills at commit e655f93, republished under its Apache-2.0 licence (© SpecterOps). 112 words, ~287 tokens.
Download SKILL.mdSave it as
.claude/skills/electron-candidate-discovery/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- electron-candidate-discovery
- description
- Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method. Use when building an actionable shortlist of candidate apps rather than a broad inventory.
- metadata.author
- GhostWorks
Electron Candidate Discovery
Use this skill to identify practical Electron app candidates for the same patching and delivery method.
Goal
Return a ranked shortlist of realistic candidates, not a broad catalog.
For Each Candidate Include
- app name
- why it is practical
- packaging shape
- installer/update mechanism
- whether it appears Squirrel-like or similarly patchable
- likely main-process entrypoint location
- obvious blockers or drawbacks
Selection Bias
Prioritize apps that are:
- clearly Electron-based
- locally patchable without bespoke tooling
- packaged in a way that exposes entrypoints or repackable resources
- delivered through Squirrel or a closely similar updater/install chain
- realistic for user delivery and repeated rebuild workflows
Output
Return a ranked shortlist with concise, actionable reasoning for each entry.
© SpecterOps, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (assets) in plugins/payloads/skills/electron-candidate-discovery of SpecterOps/skills.
- SKILL.md
- agents/openai.yaml
- assets/icon.png
- assets/icon.svg
Open the folder on GitHubat commit e655f93
Compare with similar skills
Electron Candidate Discovery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Electron Candidate Discovery this skillSpecterOps/skills | 702 | — | ~287 | Automated safety check: Pass | Apache-2.0 | |
| Desktop ElectronOpenHands/OpenHands | 90k | — | ~302 | Automated safety check: Pass | MIT | |
| Electron App Automationvercel-labs/agent-browser | 44k | 5 repos | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Electron Developmentdavila7/claude-code-templates | 32k | 3 repos | ~7k | Automated safety check: Pass | MIT | |
| Mock Best Practicesthedaviddias/Front-End-Checklist | 74k | — | ~425 | Automated safety check: Pass | MIT | |
| Interactivity Best Practicesremotion-dev/remotion | 62k | — | ~147 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Electron App Automation
vercel-labs/agent-browser
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
Electron Development
davila7/claude-code-templates
Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.
Mock Best Practices
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices.
- Official
Interactivity Best Practices
remotion-dev/remotion
Best practices for writing Remotion animations that stay intuitive for agents and editable in Remotion Studio Visual Mode.
Use Vishot With Electron
moeru-ai/airi
Capture deterministic Electron windows with Vishot. An agent skill from moeru-ai/airi.
More from SpecterOps/skills
All 38 skills in this repoCodex Activity Report
SpecterOps/skills
Generate a normalized UTC timeline and evidence-based narrative from Codex activity artifacts.
Com Proxy Triage
SpecterOps/skills
A skill your agent uses when the user wants to triage Windows COM proxy/hijack candidates by capturing HKCU\Software\Classes\CLSID\{...}\InProcServer32 NAME NOT FOUND lookups for a process, mapping…
Cwe Code Review
SpecterOps/skills
Perform CWE-grounded security code reviews and precise weakness mapping using a locally derived MITRE CWE corpus, relationship graphs, mapping notes, detection methods, mitigations, and schema…
Ghostwriter Oplog
SpecterOps/skills
A skill your agent uses for Ghostwriter operation log entries from Codex, including config guidance, quick notes, evidence-backed entries, and guided oplog capture through the Ghostwriter MCP tools.
Nmap Parse
SpecterOps/skills
Parse nmap scan output and generate actionable recon notes. An agent skill from SpecterOps/skills.
Osint Recon
SpecterOps/skills
Perform OSINT and external reconnaissance for approved targets.
Questions about Electron Candidate Discovery
What does Electron Candidate Discovery do?
Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method. Electron Candidate Discovery is an agent skill from SpecterOps/skills. Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method.
When should I use Electron Candidate Discovery?
Electron Candidate Discovery fits situations like: building an actionable shortlist of candidate apps rather than a broad inventory.
How do I install Electron Candidate Discovery in Claude Code?
Run `npx skills add SpecterOps/skills --skill electron-candidate-discovery -a claude-code`. Or copy the skill folder (plugins/payloads/skills/electron-candidate-discovery in SpecterOps/skills) into .claude/skills/electron-candidate-discovery in your project. Claude Code loads it when a task matches its description.
How do I install Electron Candidate Discovery in Codex?
Run `npx skills add SpecterOps/skills --skill electron-candidate-discovery -a codex`. Or copy the skill folder (plugins/payloads/skills/electron-candidate-discovery in SpecterOps/skills) into .agents/skills/electron-candidate-discovery in your project. Codex loads it when a task matches its description.
Can I use Electron Candidate Discovery in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpecterOps/skills --skill electron-candidate-discovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/electron-candidate-discovery, .gemini/skills/electron-candidate-discovery, .github/skills/electron-candidate-discovery and .opencode/skills/electron-candidate-discovery in your project.
What does Electron Candidate Discovery need to run?
SKILL.md names no scripts, command-line tools or credentials: Electron Candidate Discovery is instructions for the agent only.
Does Electron Candidate Discovery access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Electron Candidate Discovery safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Electron Candidate Discovery use?
Electron Candidate Discovery is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Electron Candidate Discovery use?
About 287 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Electron Candidate Discovery?
Skills that share tags, products or a category with Electron Candidate Discovery: Desktop Electron (OpenHands/OpenHands, 90k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars), Electron Development (davila7/claude-code-templates, 32k stars) and Mock Best Practices (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Electron Candidate Discovery?
SpecterOps (a GitHub organization) maintains it in SpecterOps/skills, which has 702 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on September 23, 2026.
Source: SpecterOps/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.