packaging-notarization — Codex skill for macOS packaging
This skill checks macOS app archives, signing, and notarization readiness. Use it when preparing a build for distribution or investigating failures that appear only in distributed builds.
npx skills add openai/plugins --skill packaging-notarization -a codexWhat packaging-notarization does
The skill starts by clarifying the distribution goal: local archive validation, a signed distributable app, or notarization troubleshooting. It then checks the app bundle structure, nested frameworks and helper tools, followed by hardened runtime, signing identity, nested code signatures, and entitlements.
The agent should report which artifact or settings it inspected, whether the app looks ready for distribution, the main missing prerequisite or failure mode, and a next validation or repair step. If the exported app itself is unavailable, conclusions drawn from project settings are inferences. Notarization is not required for ordinary local debug runs.
Install this skill when preparing a macOS app for distribution or diagnosing a failure limited to distributed builds. Skip it for routine local debugging.
What it helps with
- validate a macOS app archive before distribution
- find issues with nested code signatures
- assess an app's notarization readiness
- diagnose failures that appear only in distributed builds
Example prompts for the agent
- Check this macOS app archive for distribution readiness and list any missing prerequisites.
- Explain why the app runs locally but fails in the distributed build.
- Inspect this app bundle's signing settings, hardened runtime, and entitlements.
How to install packaging-notarization
1Skills CLI (Vercel)
npx skills add openai/plugins --skill packaging-notarization -a codex2Manually: put the files in place
.agents/skills/packaging-notarization/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill packaging-notarization -a claude-code2Manually: put the files in place
~/.claude/skills/packaging-notarization/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/packaging-notarization/
Manually: put the files in place
.cursor/skills/packaging-notarization/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins packaging-notarization2Manually: put the files in place
.github/skills/packaging-notarization/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/build-macos-apps/skills/packaging-notarizationManually: put the files in place
.devin/skills/packaging-notarization/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set201
The whole set →Similar
Questions about packaging-notarization
How do I install packaging-notarization in Codex?
Run npx skills add openai/plugins --skill packaging-notarization. To select Codex explicitly, use npx skills add openai/plugins --skill packaging-notarization -a codex.
What does packaging-notarization do?
It guides checks of macOS app packaging, code signing, and notarization readiness. It also helps distinguish packaging problems from trust-policy symptoms.
Is notarization required for local debug runs?
No. The skill says notarization is not required for ordinary local debug runs.
Source text
SKILL.md · MIT
--- name: packaging-notarization description: Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures. --- # 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 1. Confirm the distribution goal. - Local archive validation - Signed distributable app - Notarization troubleshooting 2. Inspect the artifact. - Validate app bundle structure. - Check nested frameworks, helper tools, and entitlements. 3. Inspect signing and runtime prerequisites. - Hardened runtime - Signing identity - Nested code signatures - Required entitlements 4. 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
© OpenAI · MIT · openai/plugins