CtrlK
BlogDocsLog inGet started
Tessl Logo

signing-entitlements

Inspect macOS signing, entitlements, and Gatekeeper issues. Use when diagnosing code signing, sandbox, hardened runtime, or trust failures.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is well-structured, actionable, and tightly scoped to read-only macOS signing diagnostics with a clear sequenced workflow and a useful classification taxonomy. The only meaningful weakness is mild redundancy between the Useful Commands list and the command already embedded in the Workflow.

Suggestions

Remove the duplicate command listings from 'Useful Commands' that already appear in Workflow step 2, or collapse the two into a single command reference to eliminate redundancy.

Add a brief verify-the-fix step (e.g., re-run 'spctl -a -vv' or 'codesign --verify' after applying a repair) so the workflow closes with an explicit validation checkpoint even though inspection itself is read-only.

Trim the Quick Start paragraph, which restates trigger language already present in the frontmatter description, to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is lean and free of concept-explaining padding, but the 'Useful Commands' section repeats commands already given in step 2 of the Workflow and Quick Start restates trigger language from the description, so it could be tightened to fully earn anchor 3.

2 / 3

Actionability

Provides real, copy-paste-ready commands with exact flags ('codesign -dvvv --entitlements :- <path>', 'spctl -a -vv <path>', 'security find-identity -p codesigning -v') and a concrete classification taxonomy, matching the 'fully executable commands' anchor.

3 / 3

Workflow Clarity

A clear 4-step Inspect → Read → Classify → Explain sequence with the classification list acting as a decision checklist; the diagnostic commands are read-only, so the missing-validate cap for destructive/batch operations does not apply.

3 / 3

Progressive Disclosure

A short, single-purpose skill with no external references needed and clearly organized sections (Quick Start, Workflow, Useful Commands, Guardrails, Output Expectations), qualifying for the anchor 3 small-skill exception.

3 / 3

Total

11

/

12

Passed

Description

90%

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 tight, well-targeted description with an explicit Use-when clause and strong natural trigger terms specific to the macOS signing niche. It is only slightly held back on specificity, where the action verbs are broader than a full enumeration of concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and several inspection targets ('Inspect macOS signing, entitlements, and Gatekeeper issues'), but relies on the broad verbs 'inspect' and 'diagnosing' rather than enumerating many distinct concrete actions, so it stops short of the comprehensive anchor 3.

2 / 3

Completeness

Explicitly states what it does ('Inspect macOS signing, entitlements, and Gatekeeper issues') and when to use it ('Use when diagnosing code signing, sandbox, hardened runtime, or trust failures'), satisfying both halves of the anchor 3 example.

3 / 3

Trigger Term Quality

Strong natural-term coverage a developer would actually say — 'signing', 'entitlements', 'Gatekeeper', 'sandbox', 'hardened runtime', 'trust failures' — matching the 'good coverage' anchor.

3 / 3

Distinctiveness Conflict Risk

The macOS codesigning niche and distinctive terms (Gatekeeper, entitlements, hardened runtime) make it unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

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
openai/plugins
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.