mcpbeat

Packaging Notarization

openai/packaging-notarization

Prepare macOS packaging and notarization workflows. Use when archiving apps, validating bundles, or explaining distribution-only failures.

434 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4915
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/openai/plugins --skill packaging-notarization

What comes with it

304 bytes besides the instruction
agents/openai.yaml

The instruction itself

5 sections, as written by the author

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

How to use it

Copy the folder

Take openai/packaging-notarization from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.