Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

electron-builder-config · a5c-ai | DecimalAI

a5c-ai/electron-builder-config

SkillScore100Maintained

Generate and validate electron-builder configuration for multi-platform desktop builds with code signing, auto-update, and platform-specific packaging

DevOpsby a5c-ai

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

DevOps & SRE pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/a5c-ai-electron-builder-config/SKILL.md

decimalai skills pull a5c-ai-electron-builder-config --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/a5c-ai-electron-builder-config/SKILL.md https://app.decimal.ai/s/a5c-ai-electron-builder-config/SKILL.md

Raw file: /s/a5c-ai-electron-builder-config/SKILL.md ↗ · machine-readable summary at /s/a5c-ai-electron-builder-config.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 54d ago

Yes — +14% lift · at higher cost+100% tokens0% turns100% of whole cases pass with skill (22/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-07	✗→✓	▲ Improved	34%	0%
case-16	✗→✓	▲ Improved	57%	0%
case-17	✗→✓	▲ Improved	104%	0%
case-01	✓→✓	＝ Same ✓	97%	0%
case-02	✓→✓	＝ Same ✓	44%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 7/31/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

a5c-ai / babysitter

library/specializations/desktop-development/skills/electron-builder-config/SKILL.md

View on GitHub ↗

License MITImported 7/31/2026Version v1

Skill contents

SKILL.md

electron-builder-config

Generate and validate electron-builder configuration for multi-platform desktop builds. This skill handles the complete configuration for building Electron applications across Windows, macOS, and Linux with proper code signing, auto-update channels, and platform-specific installers.

Capabilities

Generate complete electron-builder.yml or electron-builder.json5 configuration
Configure platform-specific build targets (NSIS, DMG, AppImage, DEB, RPM, Snap, Flatpak)
Set up code signing for Windows (Authenticode) and macOS (Developer ID)
Configure auto-update settings with electron-updater
Optimize build artifacts with compression and deduplication
Validate existing configurations for common issues
Generate CI/CD build scripts for GitHub Actions, Azure DevOps, CircleCI

Input Schema

json
{
  "type": "object",
  "properties": {
    "projectPath": {
      "type": "string",
      "description": "Path to the Electron project root"
    },
    "appInfo": {
      "type": "object",
      "properties": {
        "appId": { "type": "string", "description": "Application bundle ID (com.company.app)" },
        "productName": { "type": "string" },
        "copyright": { "type": "string" }
      },
      "required": ["appId", "productName"]
    },
    "platforms": {
      "type": "array",
      "items": { "enum": ["windows", "macos", "linux"] },
      "description": "Target platforms to build for"
    },
    "targets": {
      "type": "object",
      "properties": {
        "windows": { "type": "array", "items": { "enum": ["nsis", "nsis-web", "portable", "appx", "msi", "squirrel"] } },
        "macos": { "type": "array", "items": { "enum": ["dmg", "pkg", "mas", "mas-dev", "zip"] } },
        "linux": { "type": "array", "items": { "enum": ["AppImage", "deb", "rpm", "snap", "flatpak", "tar.gz"] } }
      }
    },
    "codeSigning": {
      "type": "object",
      "properties": {
        "windows": {
          "type": "object",
          "properties": {
            "enabled": { "type": "boolean" },
            "certificateSubjectName": { "type": "string" },
            "timestampServer": { "type": "string" }
          }
        },
        "macos": {
          "type": "object",
          "properties": {
            "enabled": { "type": "boolean" },
            "identity": { "type": "string" },
            "hardenedRuntime": { "type": "boolean", "default": true },
            "notarize": { "type": "boolean" }
          }
        }
      }
    },
    "autoUpdate": {
      "type": "object",
      "properties": {
        "enabled": { "type": "boolean" },
        "provider": { "enum": ["github", "s3", "generic", "spaces", "keygen"] },
        "channel": { "enum": ["latest", "beta", "alpha"] }
      }
    },
    "generateCIScripts": {
      "type": "boolean",
      "description": "Generate CI/CD build scripts"
    }
  },
  "required": ["projectPath", "appInfo", "platforms"]
}

Output Schema

json
{
  "type": "object",
  "properties": {
    "success": { "type": "boolean" },
    "configPath": { "type": "string", "description": "Path to generated config file" },
    "config": { "type": "object", "description": "Generated electron-builder configuration" },
    "ciScripts": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "path": { "type": "string" },
          "description": { "type": "string" }
        }
      }
    },
    "warnings": { "type": "array", "items": { "type": "string" } },
    "recommendations": { "type": "array", "items": { "type": "string" } }
  },
  "required": ["success"]
}

Usage Instructions

Analyze project structure: Examine package.json, existing build configs, and project layout
Determine build requirements: Based on target platforms and distribution needs
Generate configuration: Create electron-builder.yml with all necessary settings
Validate configuration: Check for common issues and missing dependencies
Generate CI scripts: If requested, create GitHub Actions or other CI workflows

Configuration Templates

Basic Multi-Platform Build

yaml
appId: com.example.myapp
productName: MyApp
directories:
  buildResources: build
  output: dist
files:
  - "**/*"
  - "!**/*.{md,txt}"
  - "!**/node_modules/*/{CHANGELOG.md,README.md,readme.md}"
win:
  target:
    - target: nsis
      arch: [x64, ia32]
  icon: build/icon.ico
mac:
  target:
    - target: dmg
      arch: [x64, arm64]
  icon: build/icon.icns
  hardenedRuntime: true
  gatekeeperAssess: false
linux:
  target:
    - target: AppImage
      arch: [x64]
    - target: deb
      arch: [x64]
  icon: build/icons
  category: Utility

With Code Signing and Notarization

yaml
win:
  sign: ./scripts/sign.js
  signingHashAlgorithms: [sha256]
  signDlls: true
mac:
  identity: "Developer ID Application: Company Name (TEAMID)"
  hardenedRuntime: true
  entitlements: build/entitlements.mac.plist
  entitlementsInherit: build/entitlements.mac.plist
afterSign: scripts/notarize.js

With Auto-Update

yaml
publish:
  provider: github
  owner: your-org
  repo: your-repo
  releaseType: release
nsis:
  oneClick: false
  perMachine: true
  allowToChangeInstallationDirectory: true
  differentialPackage: true

Best Practices

Always use hardenedRuntime: true for macOS to pass notarization
Enable signingHashAlgorithms: [sha256] for modern Windows compatibility
Use differentialPackage: true for efficient auto-updates
Configure files patterns to exclude unnecessary files and reduce bundle size
Set up separate channels (latest, beta, alpha) for staged rollouts
Store signing credentials in CI secrets, never in config files

Community References

Related Skills

electron-main-preload-generator - Generate secure main process and preload scripts
electron-auto-updater-setup - Configure electron-updater with advanced features
windows-authenticode-signer - Windows code signing with signtool
macos-codesign-workflow - macOS code signing and notarization

Related Agents

electron-architect - Expert in Electron architecture and best practices
desktop-ci-architect - CI/CD pipeline design for desktop builds

Illustrative Want to see what a5c-ai/electron-builder-config would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/1/2026, 02:42 UTC · 22 cases

Lift

+14%

100% vs 86%

Agent turns

1.0 vs 1.0

Tokens

+100%

3,364.68 vs 1,685.91

fail → pass · 3pass → pass · 19

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 We are preparing our cross-platform desktop project at `/workspace/my-app` (`com.company.toolkit`, 'Company Toolkit') to build for Windows, macOS, and Linux. We also want GitHub Actions workflow files created alongside the configuration. Please return a structured result with `success` flag, `configPath`, `config`, a `ciScripts` list containing script paths and descriptions, plus `warnings` and `recommendations`.	pass→pass	10,820	11,677	+8%	1	1	0%	2,322	4,563	+97%	0	0	—
case-02 We are configuring an Electron application build for macOS distribution outside the Mac App Store. Developers often turn off hardened runtime during initial testing to avoid entitlements issues. Provide the recommended `mac` block configuration in YAML for distribution and notarization.	pass→pass	11,195	8,542	-24%	1	1	0%	2,486	3,578	+44%	0	0	—
case-03 When configuring Windows builds in electron-builder, legacy setups default to sha1 or unconfigured hash algorithms. We need a modern Windows signing configuration in electron-builder YAML format to avoid security warnings.	pass→pass	12,832	8,981	-30%	1	1	0%	2,057	3,612	+76%	0	0	—
case-04 Our Electron application uses NSIS on Windows with auto-updates. Network bandwidth for users is limited, so we want to enable fast incremental updates instead of downloading full installers every time. What NSIS setting in electron-builder handles this?	pass→pass	8,166	5,212	-36%	1	1	0%	1,515	2,829	+87%	0	0	—
case-05 Our Electron project build includes massive node_modules containing markdown changelogs and documentation files that inflate binary size. How should the `files` property in `electron-builder.yml` be configured to omit these unneeded files while preserving code?	pass→pass	13,729	8,766	-36%	1	1	0%	2,025	3,414	+69%	0	0	—
case-06 Configure the `publish` key in electron-builder configuration for a public repository `my-org/my-app` on GitHub for automated releases.	pass→pass	10,926	7,989	-27%	1	1	0%	1,762	3,622	+106%	0	0	—
case-07 We are setting up an NSIS installer for Windows users. By default, many installers run in one-click mode without letting users choose their installation directory or requiring per-machine installation. Produce an `nsis` configuration block that allows users to pick an install folder.	fail→pass	12,367	7,293	-41%	1	1	0%	2,378	3,189	+34%	0	0	—
case-08 We are invoking the electron-builder config generator with an input payload containing `projectPath: '/app'` and `platforms: ['windows']`, but omitting `appInfo`. Describe or return the schema validation outcome.	pass→pass	9,875	3,623	-63%	1	1	0%	1,806	2,618	+45%	0	0	—
case-09 An automated pipeline submits an electron-builder configuration request with `platforms: ['windows', 'freebsd']`. What validation response should be produced according to the skill schema?	pass→pass	5,985	4,366	-27%	1	1	0%	990	2,707	+173%	0	0	—
case-10 We need to build a macOS DMG targeting both Intel (x64) and Apple Silicon (arm64) architectures. Show the target configuration under `mac` in electron-builder YAML.	pass→pass	4,874	7,029	+44%	1	1	0%	1,028	2,999	+192%	0	0	—
case-11 Configure Linux targets in electron-builder to generate an AppImage and a Debian package (.deb) for 64-bit architecture.	pass→pass	8,058	8,052	-0%	1	1	0%	1,704	3,543	+108%	0	0	—
case-12 A developer wants to hardcode the macOS Developer ID certificate password and private key directly inside `electron-builder.yml` to simplify developer setup. Provide advice and the best practice recommendation regarding code signing credentials.	pass→pass	10,877	10,363	-5%	1	1	0%	1,978	3,793	+92%	0	0	—
case-13 We want to publish pre-release Electron builds to a separate channel so beta testers get updates before general availability. How is the release channel specified in auto-update settings?	pass→pass	9,671	8,248	-15%	1	1	0%	1,931	3,563	+85%	0	0	—
case-14 Rather than relying on default signtool flags, our team uses a custom JavaScript signing script located at `./scripts/sign.js`. How should this custom signing hook be configured under the `win` key in `electron-builder.yml`?	pass→pass	6,663	6,098	-8%	1	1	0%	1,024	3,023	+195%	0	0	—
case-15 To automate macOS notarization after code signing completes, electron-builder supports a post-signing hook. Show how to attach `scripts/notarize.js` as the after-sign script in `electron-builder.yml`.	pass→pass	4,289	6,388	+49%	1	1	0%	829	3,273	+295%	0	0	—
case-16 Generate a full JSON schema compliant response for configuring `com.acme.editor` ('Acme Editor') at `/projects/editor` targeting Windows (nsis) and macOS (dmg).	fail→pass	10,412	7,198	-31%	1	1	0%	2,356	3,695	+57%	0	0	—
case-17 We need an electron-builder configuration generated for `/app/desktop` (`com.corp.desk`, 'Corp Desk', target `windows`), and we also need automated build scripts generated for our GitHub Actions workflow. Specify `generateCIScripts` in the input and return the output schema structure.	fail→pass	8,189	8,297	+1%	1	1	0%	1,811	3,692	+104%	0	0	—
case-18 When building Linux desktop packages with electron-builder, desktop environment menus require an application category and icon folder path. Provide a `linux` configuration block using the `Utility` category and `build/icons` resource directory.	pass→pass	4,723	4,543	-4%	1	1	0%	982	2,804	+186%	0	0	—
case-19 We need an NSIS installer that installs the desktop application system-wide for all users on a Windows machine rather than per-user AppData. What property is set in the `nsis` section?	pass→pass	3,164	3,476	+10%	1	1	0%	575	2,565	+346%	0	0	—
case-20 Write a Secure Context Bridge preload script (`preload.js`) for Electron that exposes a safe `ipcRenderer` invocation method `window.api.sendData(channel, data)` to the renderer process without exposing the full IPC module.	pass→pass	9,931	9,167	-8%	1	1	0%	2,005	3,732	+86%	0	0	—
case-21 Write an `app.whenReady()` main process script in TypeScript (`main.ts`) that instantiates a secure `BrowserWindow` with `webPreferences.contextIsolation: true` and `webPreferences.nodeIntegration: false`.	pass→pass	6,600	7,042	+7%	1	1	0%	1,453	3,292	+127%	0	0	—
case-22 Provide the JavaScript runtime code using the `electron-updater` package inside an Electron main process (`main.js`) to check for updates on application startup and register event listeners for `update-downloaded`.	pass→pass	9,641	10,796	+12%	1	1	0%	2,073	3,917	+89%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +14 percentage points is the difference between those two pass rates over the 22 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 86.4%
Pass rate with the skill: 100%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 0
Skill version measured: v1
Run completed: 8/1/2026, 02:42 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-07

Prompt

We are setting up an NSIS installer for Windows users. By default, many installers run in one-click mode without letting users choose their installation directory or requiring per-machine installation. Produce an `nsis` configuration block that allows users to pick an install folder.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run100

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+108% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 54 days ago

Other measured skills in the registry, with their headline benchmark lift.