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.

80

Quality

100%

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

100%

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

The body is a tight, actionable reference: concrete codesign/spctl/plutil commands, a clear diagnostic workflow with a classification checkpoint, and well-organized sections with no padding. It scores at the top of every dimension.

DimensionReasoningScore

Conciseness

Lean throughout with no explanation of concepts Claude already knows; every section (Quick Start, Workflow, Useful Commands, Guardrails, Output Expectations) earns its tokens with actionable content.

3 / 3

Actionability

Provides copy-paste-ready commands — 'codesign -dvvv --entitlements :- <path>', 'spctl -a -vv <path>', 'security find-identity -p codesigning -v', 'plutil -p' — fully executable rather than abstract direction.

3 / 3

Workflow Clarity

A clear 4-step sequence (inspect → read signing details → classify failure → explain fix) with the classification step acting as a decision checkpoint and validation explicitly part of the repair path; this is read-only diagnosis so the destructive-operation validation cap does not apply.

3 / 3

Progressive Disclosure

A single-purpose, well-organized command-reference skill with no need for external bundle files (references/scripts/assets absent) and clear sections, satisfying the simple-skill exemption for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

100%

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

The description is concise, specific, and uses natural third-person voice with a clear 'Use when' trigger clause. It names concrete capabilities and a distinct macOS-codesigning niche, hitting the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Inspect signing, entitlements, hardened runtime, and Gatekeeper issues' — matching the 'multiple specific concrete actions' anchor rather than the single-domain score-2 example.

3 / 3

Completeness

Explicitly answers both what ('Inspect signing, entitlements, hardened runtime, and Gatekeeper issues for macOS apps') and when via a literal 'Use when asked to diagnose...' clause, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Natural user-facing phrases like 'code signing failures', 'missing entitlements', 'sandbox problems', and 'notarization prerequisites' give good coverage of terms a user would actually say, beyond the partial-coverage score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

A clear macOS code-signing/entitlements niche with distinct triggers (notarization, Gatekeeper, trust-policy) makes overlap with unrelated skills unlikely.

3 / 3

Total

12

/

12

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.