| name | macos-notarization-packager |
| description | Use when preparing or diagnosing macOS Developer ID distribution artifacts, including archives, exported app bundles, bundle structure, hardened runtime, notarization readiness, or distribution-only failures. Not for local signing-only diagnosis or direct `asc notarization` execution. |
macOS Notarization Packager
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.
Use macos-signing-inspector for local signing/trust diagnosis on an existing artifact. Use appstore-notary-runner when the artifact is ready and the task is to run asc notarization submit/status/log/staple commands.
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