unsigned-desktop-release-playbook
Unsigned Desktop Release Playbook
Overview
Use this skill when you must distribute desktop binaries without code-signing certificates, while keeping packaging integrity verifiable and onboarding steps beginner-friendly.
When to Use
- macOS and/or Windows desktop release is required, but signing credentials are unavailable.
- Users report macOS "app is damaged" or cannot find "Open Anyway".
- You need a repeatable GitHub release checklist for unsigned binaries.
Core Principle
- Differentiate corrupted package vs unsigned package:
- Corrupted package:
codesign --verify --deep --strictfails. Must be fixed in build pipeline. - Unsigned package:
codesign --verifycan pass, butspctl --assessrejects. This is expected without certificate/notarization.
- Corrupted package:
Packaging Validation Workflow
- Download release asset from GitHub.
- Mount DMG and check app integrity:
codesign --verify --deep --strict --verbose=2 "<App>.app"
More from peiiii/nextclaw
ui-ux-pro-max
Use when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset and Python search runtime.
2impeccable
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.
2lark-cli
Use when the user wants to operate Lark or Feishu via the local lark-cli (@larksuite/cli), including install, app credentials, OAuth, readiness checks, and safe read/write boundaries.
1opencli
Use when the user wants to use websites, browser login sessions, Electron apps, or external CLIs through a local OpenCLI setup, especially when setup guidance, readiness checks, and safe task execution are needed.
1find-skills
Use when the user wants to discover, evaluate, and install external agent skills from the open skills ecosystem, especially through the Vercel Skills CLI.
1superpowers
Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.
1