Skill

packaging-notarization

Prepare and troubleshoot packaging, signing, and notarization workflows for macOS distribution. Use when asked to archive a Mac app, validate bundle structure, reason about notarization readiness, or explain distribution-only failures.

npx claudepluginhub robinebers/converted-plugins --plugin build-macos-apps

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/build-macos-apps:packaging-notarization

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Use this skill when the work is about shipping the app rather than merely

SKILL.md

48 lines · ~383 tokens

Similar Skills

using-superpowers

193.2k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

LanguagePython

Parent stars0

MaintenanceGood

Last CommitMay 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Packaging & Notarization

Quick Start

Use this skill when the work is about shipping the app rather than merely running it locally: archives, exported app bundles, notarization readiness, hardened runtime, or distribution validation.

Workflow

Confirm the distribution goal.

Local archive validation
Signed distributable app
Notarization troubleshooting

Inspect the artifact.

Validate app bundle structure.
Check nested frameworks, helper tools, and entitlements.

Inspect signing and runtime prerequisites.

Hardened runtime
Signing identity
Nested code signatures
Required entitlements

Explain notarization readiness or failure.

Separate packaging issues from trust-policy symptoms.
Point to the minimum follow-up validation commands.

Guardrails

Do not present notarization as required for ordinary local debug runs.

Call out when you lack the actual exported artifact and are inferring from project settings.

Keep advice concrete and verifiable.

Output Expectations

Provide:

what artifact or settings were inspected

whether the app looks distribution-ready

the top missing prerequisite or failure mode

the next validation or repair step