build-desktop-app

Automate build, test, packaging, and release workflows for Mako Desktop and Local Agent.

11|6|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/mako-ai/mako --skill build-desktop-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-desktop-app
Source: https://github.com/mako-ai/mako/tree/main/.cursor/skills/build-desktop-app
Command: npx skills add https://github.com/mako-ai/mako --skill build-desktop-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the end-to-end process to build, test, package, and release Mako Desktop and the Mako Local Agent, simplifying desktop pipeline changes and debugging.

Core Features & Use Cases

  • Automates end-to-end release workflows for local-agent, desktop, and release pipelines.
  • Supports verification, packaging outputs, and release tagging for desktop builds.
  • Use case: When updating the desktop shell or local agent, run this Skill to perform a clean build and generate release artifacts.

Quick Start

Run the end-to-end build and release process for the desktop stack using the configured CI and local development commands.

Frequently Asked Questions about build-desktop-app

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

FAQPage Schema
How do I automate the desktop release workflow for an Electron application in CI?

Electron desktop release automation orchestrates end-to-end build, test, packaging, and tagging to generate release artifacts. It applies changes to the desktop shell and local agent, ensuring clean builds and proper artifact publication in CI environments.

What is the best way to package and release a desktop app and local agent together?

Packaging and releasing a desktop app and local agent together requires an end-to-end pipeline handling verification and release tagging. Running a dedicated build process ensures both components are compiled cleanly and packaged into unified release artifacts.

How does smoke testing work during the desktop build process?

Smoke testing during the desktop build process verifies the compiled application and local agent meet deterministic build requirements before publication. It acts as an automated validation step within the CI pipeline to catch critical failures before generating release tags.

Can I use this build and release pipeline for local development or is it only for CI environments?

The build and release pipeline supports both local development commands and CI environments. It satisfies deterministic build and artifact publication requirements, meaning the same end-to-end workflow can be triggered locally or within automated release pipelines.

Why are my desktop release artifacts failing verification in the CI pipeline?

Desktop release artifacts fail verification when the end-to-end build encounters incomplete changes in the desktop shell or local agent packages. Ensuring a clean build and verifying all package modifications are committed resolves pipeline failures and generates valid tags.