CtrlK
BlogDocsLog inGet started
Tessl Logo

macos-packaging-notarization

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

57

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/macos-packaging-notarization/SKILL.md

The canonical home for this skill is packaging-notarization in openai/plugins

SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The content is well-structured and admirably concise, treating Claude as competent and organizing a clear workflow with guardrails. Its main weakness is actionability: it stays at the level of abstract steps without the concrete commands or tool invocations that would make the guidance executable.

Suggestions

Add concrete, executable commands for key steps (e.g., 'codesign --verify --deep --strict ...', 'spctl --assess --verbose=4 ...', 'xcrun notarytool submit ...').

Insert an explicit validation checkpoint with a verify-fix-retry loop, e.g. validate the bundle signature before declaring it distribution-ready.

Name the specific tools/commands to inspect (e.g., 'codesign -d --entitlements -', 'xcrun stapler validate') so the steps are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it states the workflow and guardrails without explaining what notarization or hardened runtime is, with every section earning its place.

5 / 5

Actionability

Guidance is high-level and abstract ('Validate app bundle structure', 'Check nested frameworks, helper tools, and entitlements') with no concrete commands, code, or specific tools named, so it describes rather than instructs.

2 / 5

Workflow Clarity

A clear four-step sequence is present and the Output Expectations act as an implicit checklist, but there are no explicit validation commands or verify-fix-retry checkpoints for an operation that involves validating bundles and distribution readiness.

3 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with no external bundle files and clean section structure (Quick Start, Workflow, Guardrails, Output Expectations), which the simple-skill guidance rewards with a top score.

5 / 5

Total

15

/

20

Passed

Description

66%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.

The description clearly states what the skill does and when to use it with natural trigger terms, placing it in a distinct niche. It is solid but not exemplary: the action list is modest and lacks some obvious synonyms and technical specifics that would push it to the top anchor.

Suggestions

Expand the action list with more concrete capabilities (e.g., 'inspect hardened runtime, verify nested code signatures, troubleshoot notarization tickets').

Add natural synonyms and file-specific triggers to the 'Use when' clause (e.g., 'signing .app bundles', '.dmg', 'hardened runtime', 'notarization failures').

Make the 'when' clause more explicit about distribution vs local-debug context to sharpen trigger matching.

DimensionReasoningScore

Specificity

Names the domain ('packaging and notarization workflows') and a couple of concrete actions ('archiving apps, validating bundles'), but the action list is thin and 'explaining distribution-only failures' is an outcome rather than a concrete capability.

3 / 5

Completeness

Has both a clear 'what' ('Prepare macOS packaging and notarization workflows') and an explicit 'when' ('Use when archiving apps, validating bundles, or explaining distribution-only failures'), though the 'when' could be more specific with additional trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('archiving apps', 'validating bundles', 'distribution-only failures') with good coverage, but misses common synonyms or specifics like 'notarization', 'signing', '.app', or 'hardened runtime'.

4 / 5

Distinctiveness Conflict Risk

The macOS packaging/notarization niche is fairly distinct with specific triggers, with only minor overlap risk against a generic build/release or code-signing skill.

4 / 5

Total

15

/

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.