mcpField
M
macos-release-readiness

macos-release-readiness

github.com/sylphxaiTesting & quality151 installsUpdated today
Repository

About macos-release-readiness

A skill for developers preparing macOS apps for release, covering signing, permissions, data, updates, and diagnostics. It produces a readiness matrix with evidence requirements for high-risk areas.

Key features

  1. 01Map distribution channels and app types
  2. 02Review signing, notarization, and permissions
  3. 03Check local data, backup, and uninstall
  4. 04Assess updates and diagnostics
  5. 05Separate blockers from improvements

Use cases

  1. 01Review macOS app safety before release
  2. 02Verify signature checks and recovery for auto-updates
  3. 03Document high-risk release items and required evidence

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill macos-release-readiness

After installing, type/macos-release-readinessin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/macos-release-systems.md

Details

From the project README

macOS Release Readiness

Use this skill to make macOS apps feel native, trustworthy, supportable, and safe to update.

Workflow

  1. Identify distribution channel, app type, privileged capabilities, data locations, update mechanism, and support posture.
  2. Read references/macos-release-systems.md.
  3. Audit identity/signing/notarization, sandbox/permissions, local data, keychain, login/background behavior, updates, backup, uninstall, and diagnostics.
  4. Separate release blockers from product polish and support improvements.
  5. Produce a macOS readiness matrix with proof needed for each high-risk area.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not hide login items, launch agents, background helpers, screen recording, accessibility, file access, or network behavior.
  • Do not store secrets in plist/json/plain local files when platform secure storage is appropriate.
  • Do not ship auto-update without signature verification and recovery path.

Output format

macOS context:
Distribution/update model:

Readiness matrix:
- Identity/signing:
- Permissions/sandbox:
- Data/backup/uninstall:
- Updates/diagnostics:
- Native UX:

Blockers:
- <blocker> -> proof required

Support diagnostics:
- <field/log/user action>

Comments

Markdown supported