CtrlK
BlogDocsLog inGet started
Tessl Logo

signing-entitlements

Inspect signing, entitlements, hardened runtime, and Gatekeeper issues for macOS apps. Use when asked to diagnose code signing failures, missing entitlements, sandbox problems, notarization prerequisites, or trust-policy launch errors.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is signing-entitlements in openai/plugins

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured diagnostic skill with concrete, executable codesign/spctl/plutil commands and a clear workflow. Removing the command-list duplication and adding a small aid for the classification step would tighten it further.

Suggestions

Collapse the standalone "Useful Commands" list into the workflow steps (or keep only the two commands not already shown there, e.g. `security find-identity`) to remove duplication.

Add a one-line command or decision hint next to each "Classify the failure" entry (e.g. how to detect ad-hoc vs. wrong identity) so the classification step is as actionable as the inspection step.

Add an explicit validation checkpoint such as re-running `codesign -dv --verify` or `spctl -a -vv` after the proposed fix to confirm the failure class is resolved.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explaining what codesigning is), but the "Useful Commands" section repeats `codesign -dvvv` and `spctl -a -vv` already given in the workflow, a minor trim opportunity.

4 / 5

Actionability

It gives copy-paste-ready commands (`codesign -dvvv --entitlements :- <path>`, `spctl -a -vv <path>`, `plutil -p`, `security find-identity -p codesigning -v`), but the "Classify the failure" step lists failure classes without an accompanying command or decision aid, leaving a minor gap.

4 / 5

Workflow Clarity

A clear four-step sequence (Inspect → Read signing details → Classify → Explain fix) is present; reading signing details acts as implicit validation for this read-only diagnostic skill, though no explicit verify/retry checkpoint is stated.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, the content is well-organized into clear sections (Quick Start, Workflow, Useful Commands, Guardrails, Output Expectations), satisfying the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that cleanly answers both what the skill does and when to use it, with concrete macOS code-signing trigger phrases. Minor gains are available by adding action variety and a few common synonyms.

DimensionReasoningScore

Specificity

"Inspect signing, entitlements, hardened runtime, and Gatekeeper issues for macOS apps" names the domain plus several concrete inspection targets, but the action vocabulary is effectively one verb ("inspect"/"diagnose"), leaving minor coverage gaps versus the comprehensive multi-action anchor.

4 / 5

Completeness

It explicitly states the "what" (inspect signing/entitlements/hardened runtime/Gatekeeper for macOS apps) and the "when" ("Use when asked to diagnose code signing failures, missing entitlements, sandbox problems, notarization prerequisites, or trust-policy launch errors") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"code signing failures, missing entitlements, sandbox problems, notarization prerequisites, or trust-policy launch errors" are natural user phrases with good coverage, but common synonyms/extensions (codesign, Gatekeeper, .app, provisioning) are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (macOS code signing/entitlements/notarization) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
robinebers/openusage
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.