signing-entitlements — Codex skill: what it does, how to install
Diagnoses macOS code signing, App Sandbox, and Gatekeeper failures. Useful when a binary or app bundle refuses to launch on macOS.
npx skills add openai/plugins --skill signing-entitlements -a codexWhat signing-entitlements does
The skill inspects macOS application bundles and binaries when execution fails due to trust policies rather than build errors. It locates the executable inside Contents/MacOS/, reads entitlements with codesign, and queries Gatekeeper via spctl.
Failures are classified into explicit categories like missing entitlements, ad-hoc signatures, or Hardened Runtime issues. The agent then supplies the shortest sequence of repair commands. It explicitly keeps local debug signing separate from distribution prerequisites.
macOS developers dealing with launch denials will benefit most from this setup.
What it helps with
- diagnose Gatekeeper rejections and trust-policy failures
- verify embedded entitlements and App Sandbox permissions
- detect invalid signatures across nested application bundles
- separate local debugging issues from notarization requirements
Example prompts for the agent
- Inspect code signing and entitlements for MyApp.app
- Why is Gatekeeper rejecting this binary in Contents/MacOS?
- Classify the signing failure and give me the minimal fix commands
How to install signing-entitlements
1Skills CLI (Vercel)
npx skills add openai/plugins --skill signing-entitlements -a codex2Manually: put the files in place
.agents/skills/signing-entitlements/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill signing-entitlements -a claude-code2Manually: put the files in place
~/.claude/skills/signing-entitlements/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/signing-entitlements/
Manually: put the files in place
.cursor/skills/signing-entitlements/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins signing-entitlements2Manually: put the files in place
.github/skills/signing-entitlements/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/build-macos-apps/skills/signing-entitlementsManually: put the files in place
.devin/skills/signing-entitlements/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 signing-entitlements
How to install signing-entitlements in Codex?
Run npx skills add openai/plugins --skill signing-entitlements in your project root. It writes the configuration to .agents/skills/signing-entitlements/SKILL.md.
What does signing-entitlements do?
It inspects macOS binary signatures, validates property lists, and identifies reasons behind Gatekeeper launch rejections.
Which native tools does the skill invoke?
It relies directly on standard macOS utilities, specifically codesign, spctl, security, and plutil.
Source text
SKILL.md · MIT
--- name: signing-entitlements description: Inspect macOS signing, entitlements, and Gatekeeper issues. Use when diagnosing code signing, sandbox, hardened runtime, or trust failures. --- # Signing & Entitlements ## Quick Start Use this skill when the failure smells like codesigning rather than compilation: launch refusal, missing entitlement, invalid signature, sandbox mismatch, hardened runtime confusion, or trust-policy rejection. ## Workflow 1. Inspect the bundle or binary. - Locate the `.app` or executable. - Identify the main binary inside `Contents/MacOS/`. 2. Read signing details. - Use `codesign -dvvv --entitlements :- <path>`. - Use `spctl -a -vv <path>` when Gatekeeper behavior matters. - Use `plutil -p` for entitlements or Info.plist inspection. 3. Classify the failure. - Unsigned or ad hoc signed - Wrong identity - Entitlement mismatch - Hardened runtime issue - App Sandbox issue - Nested code signing issue - Distribution/notarization prerequisite issue 4. Explain the minimum fix path. - Say exactly what is wrong. - Show the shortest set of validation or repair commands. - Distinguish local development problems from distribution problems. ## Useful Commands - `codesign -dvvv --entitlements :- <app-or-binary>` - `spctl -a -vv <app-or-binary>` - `security find-identity -p codesigning -v` - `plutil -p <path-to-entitlements-or-plist>` ## Guardrails - Never invent missing entitlements. - Do not conflate notarization with local debug signing. - If the real issue is a build setting or provisioning profile, say so directly. ## Output Expectations Provide: - what artifact was inspected - what signing state it is in - the exact failure class - the minimum fix or validation sequence
© OpenAI · MIT · openai/plugins