electron-mac-packaging

Name: electron-mac-packaging
Availability: InStock
Author: phuhao

Automate Electron desktop app packaging for macOS and Windows.

12|3|Updated Jun 17, 2026

Search Tags:#automation #deployment #packaging #macos #electron #windows

Ready to run

npx skills add https://github.com/phuhao00/bony-agent --skill electron-mac-packaging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: electron-mac-packaging
Source: https://github.com/phuhao00/bony-agent/tree/main/.agent/skills/electron-mac-packaging
Command: npx skills add https://github.com/phuhao00/bony-agent --skill electron-mac-packaging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pillow, mingw-w64, and includes scripts (resource) components.

What problem does it solve?

This skill automates the complex, multi-step packaging process for the AI Media Agent desktop application, ensuring consistent builds across macOS and Windows while managing internal dependencies like Python, Node.js, and Playwright.

Core Features & Use Cases

Cross-Platform Packaging: Orchestrates DMG creation for macOS and zip/portable/NSIS builds for Windows.
Environment Synchronization: Automatically handles backend environment variable merging and resource bundle synchronization to prevent 404 errors and configuration drift.
Use Case: When you need to release a new version of the desktop app, use this skill to ensure the bundled Python runtime, Node.js, and all backend services are correctly packaged and verified for end-user deployment.

Quick Start

Use the electron-mac-packaging skill to build the Windows desktop package and verify the bundled environment configuration.

Frequently Asked Questions about electron-mac-packaging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Electron desktop app packaging for macOS and Windows?▼

Electron cross-platform packaging handles environment variable injection, backend resource synchronization, and automated validation of packaging assets to prevent configuration drift and 404 errors during deployment.

Can I bundle standalone Python and Node.js runtimes in an Electron build?▼

Cross-compiling sidecar services ensures that internal dependencies like Python, Node.js, and Playwright are correctly packaged and verified within the Electron desktop application.

What is the best way to prevent configuration drift in Electron cross-platform builds?▼

Automated validation of packaging assets further ensures production-ready artifacts by checking cross-platform compatibility and verifying bundled environment configurations.

Does cross-compilation for Electron sidecar services require specific dependencies?▼

These dependencies support the automated end-to-end build lifecycle, ensuring backend services are correctly packaged for macOS and Windows deployment.

Why do my Electron desktop app builds fail with 404 errors on backend resources?▼

Automating environment variable merging and resource bundle synchronization prevents these 404 errors and ensures production-ready artifacts for deployment.

When do I need automated validation for Electron packaging assets?▼

This validation step verifies the environment configuration and prevents configuration drift before generating DMG, zip, or NSIS installation artifacts.