@xopoko/macos-notarization-packager
AUse 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.
Install
agr install @xopoko/macos-notarization-packager --target claudeWrites 1 file into .claude/skills/, pinned to git-65239df4.
- .claude/skills/macos-notarization-packager/SKILL.md
Document
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
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-65239df42fe12026-07-31