packaging-notarization

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/build-macos-apps/skills/packaging-notarization/SKILL.md

Quality

Content

65%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 body is well-structured and token-efficient for a focused instruction-only skill, with a clear workflow and good sectioning. Its main weakness is actionability: it tells Claude what to inspect but not the concrete commands to verify packaging, signing, and notarization state.

Suggestions

Add the concrete verification commands alongside the inspection bullets, e.g. `codesign --verify --deep --strict`, `spctl --assess --verbose`, and `xcrun notarytool history`/`submit`, so guidance is executable rather than only descriptive.

Insert an explicit validation checkpoint into the workflow (e.g. after step 2, 'Run `codesign --verify` and `spctl --assess`; only proceed to notarization analysis if both pass') with a fix-and-retry loop for failures.

Collapse the small overlap between the Quick Start scope sentence and the Output Expectations list to tighten the body further.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding of concepts Claude already knows, though the Quick Start scope statement and Output Expectations list overlap slightly, matching the score-4 anchor of efficient content with minor trim opportunities.	4 / 5
Actionability	It lists concrete inspection targets ("nested frameworks, helper tools, and entitlements", "hardened runtime", "signing identity") but omits the executable verification commands (e.g. codesign, spctl, xcrun notarytool), matching the score-3 anchor of some concrete guidance with key details missing.	3 / 5
Workflow Clarity	A clear four-step sequence (confirm goal, inspect artifact, inspect signing/runtime, explain readiness) is present, but validation checkpoints and error-recovery feedback loops are only implicit rather than explicit, matching the score-3 anchor.	3 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references (no bundle files exist), and is organized into clear sections (Quick Start, Workflow, Guardrails, Output Expectations), satisfying the simple-skill exception for a score of 5.	5 / 5
	Total	15 / 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.

The description is concise, third-person, and clearly pairs a concrete capability statement with an explicit 'Use when' trigger clause covering several natural phrases. Its only gap is slightly limited synonym/extension coverage (e.g. file extensions or signing terms).

Dimension	Reasoning	Score
Specificity	Names the domain ("macOS packaging and notarization workflows") and several concrete actions ("archiving apps, validating bundles, or explaining distribution-only failures"), comparable to the score-4 anchor listing several specific actions with minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ("Prepare macOS packaging and notarization workflows") and when ("Use when archiving apps, validating bundles, or explaining distribution-only failures") with concrete trigger phrases, matching the score-5 anchor; the 'Use when' cap does not apply since it is present.	5 / 5
Trigger Term Quality	Natural trigger phrases like "archiving apps", "validating bundles", and "distribution-only failures" are present and user-likely, but common synonyms/extensions (e.g. ".app", "signing", "notarize") are missing, matching the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	The macOS packaging/notarization niche with distinct distribution-oriented triggers is unlikely to fire for unrelated skills, matching the score-5 anchor of a clear niche with minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/build-macos-apps/skills/packaging-notarization/SKILL.md
Commit: 1e28582

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.