deploy

Dispatch the Claude Desktop for Linux build-and-release GitHub Actions workflow.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill deploy-patrickjaja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/patrickjaja/claude-desktop-bin/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill deploy-patrickjaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually starting the claude-desktop-bin release pipeline, letting you launch a packaged build and deployment flow from a single command.

Core Features & Use Cases

  • Workflow Dispatch: Starts the build-and-release GitHub Actions pipeline for the current repository.
  • Force Rebuild Option: Re-runs the pipeline with force_rebuild enabled when the upstream version has not changed and a new package release is still needed.
  • Run Visibility: Resolves the latest workflow run and reports its URL and status so you can monitor progress quickly.
  • Use Case: Use this Skill when a new upstream Claude Desktop release arrives, or when you need to publish a patch-only update without changing the tracked version.

Quick Start

Ask the deploy skill to trigger the build-and-release workflow, and include force only when you need a forced rebuild.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I trigger a GitHub Actions release workflow on demand?

Trigger a GitHub Actions release workflow on demand by dispatching the build-and-release pipeline via the GitHub CLI, which starts the packaging and deployment process and returns the run URL for monitoring.

Can I force a rebuild when the upstream version has not changed?

You can force a rebuild when the upstream version has not changed by enabling the force_rebuild option during workflow dispatch, re-running the pipeline to publish a patch-only update without modifying the tracked version.

Do I need GitHub CLI access to dispatch a build and release workflow?

GitHub CLI access is required to dispatch the build-and-release workflow, inspect recent runs, and report the run URL and status for end-to-end packaging across deb, rpm, appimage, pkgbuild, nix, and pages targets.

What packaging targets are supported by the workflow_dispatch deployment?

The workflow_dispatch deployment supports end-to-end packaging and deployment across deb, rpm, appimage, pkgbuild, nix, and pages targets, covering comprehensive Linux distribution formats.

How do I check the status of a recent GitHub Actions release run?

Check the status of a recent GitHub Actions release run by inspecting recent workflow runs through the GitHub CLI, which resolves the latest run and reports its URL and current status for quick progress monitoring.