Desktop Electron
Use when the user asks about Electron, main and renderer process IPC security, contextBridge and preload scripts, contextIsolation and sandbox, Electron Forge or electron-builder packaging, code signing or auto-update. Produces a secure Electron app structure and release setup. Not for Tauri apps (use desktop-tauri).
Install
npx skills add j4flmao/agent-skills --skill desktop-electrongit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/desktop/electron ~/.claude/skills/desktop-electronPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Electron
## Purpose
Build cross-platform desktop applications using Electron — combining Chromium (for rendering) and Node.js (for system access). Electron enables web technologies (HTML, CSS, JavaScript/TypeScript) to deliver native-capable desktop experiences with access to the file system, operating system APIs, native menus, and auto-updating.
## Agent Protocol
### Trigger
Exact user phrases: "Electron app", "main process", "renderer process", "IPC", "preload script", "contextBridge", "electron-builder", "electron-forge", "native module", "auto-updater", "BrowserWindow".
### Input Context
- Electron version (>= 28 recommended for security)
- Framework (React, Vue, Svelte, Angular, vanilla)
- Build tool (Vite, webpack, esbuild)
- Required OS APIs (file system, notifications, clipboard, USB/serial, native dialogs)
- Distribution needs (Windows, macOS, Linux; auto-update; code signing)
- Performance constraints (memory, startup time, renderer count)
### Output Artifact
Electron architecture plan with process model, IPC strategy, security configuration, build pipeline, and distribution setup.
### Response Format
```
Processes: main {responsibilities} | preload {exposed API} | renderer {framework}
Security: contextIsolation, sandbox, nodeIntegration=false, CSP, fuses
IPC: {channel -> invoke/handle signature, validation}
Build/Update: {Electron Forge|electron-builder}, signing, autoUpdater
Code: {files}
```
### Completion CriteriaDetails
- Skill name
desktop-electron- Repository
- j4flmao/agent-skills
- Path
skills/desktop/electron/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Desktop Electron skill do?
Use when the user asks about Electron, main and renderer process IPC security, contextBridge and preload scripts, contextIsolation and sandbox, Electron Forge or electron-builder packaging, code signing or auto-update. Produces a secure Electron app structure and release setup. Not for Tauri apps (use desktop-tauri).
How do I install the Desktop Electron skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill desktop-electron. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Desktop Electron popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Dev Loop Security Auditor
45j4flmao/agent-skills
Use when the user asks for a security audit of a codebase, dependency vulnerability scan (npm audit, pip-audit, Trivy), secret scanning, Semgrep or CodeQL findings, or OWASP Top 10 review. Produces prioritized findings with fixes. Not for SAST/DAST pipeline design (use security-sast-dast) or pentest engagements (use pentesting).
Cloud Native Security Offensive
45j4flmao/agent-skills
Use when the user asks about AWS privilege escalation paths, cloud attack paths, IMDS SSRF, iam:PassRole abuse, Azure managed identity abuse, or a cloud threat model for an authorized review. Explains each path with its detection and remediation. Not for building guardrails (use cloud-native-security-defensive) or general pentest method (use red-team-pentest-methodology).
Enterprise Compliance Audit
45j4flmao/agent-skills
Use when the user asks to prepare evidence for a SOC 2 audit, ISO 27001 certification, GDPR, HIPAA or PCI DSS compliance, control mapping, auditor requests or continuous compliance monitoring. Produces a control matrix, evidence plan and audit-readiness checklist. Not for vulnerability scanning (use dev-loop-security-auditor) or pentests (use pentesting).
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.