CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-mac-app

macOS app release: Sparkle, notarization, GitHub Release, Homebrew, closeout.

Quality

81%

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

82%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 highly operational, executable reference: exact commands, a complete manifest specification, explicit validation criteria, and failure-resume rules, with heavy implementation detail correctly kept in the script bundle. The main weaknesses are duplicated codesign/1Password credential descriptions and an implicit (never explicitly ordered) release sequence.

Suggestions

Deduplicate the codesign keychain protocol, which appears in both the MAC_RELEASE_CODESIGN_IDENTITY manifest bullet and the 1Password rules section, into a single authoritative description.

Add a short ordered release sequence (e.g. status → notes → changelog-html → release → verify-appcast → check-assets → changelog bump) so the step order is stated rather than inferred from the command list.

Move the deep 1Password/codesign credential protocol into a one-level-deep references/ file to slim SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and operational with essentially no explanation of concepts Claude already knows, but the codesign keychain protocol and Sparkle OP-ref flow are each described twice — once in the Manifest bullets ("MAC_RELEASE_CODESIGN_IDENTITY + ... enable non-interactive Developer ID signing...") and again in the 1Password rules — which is trimmable redundancy. It is not 5 because of this duplication, and not 3 since nothing is padded with generally-known material.

4 / 5

Actionability

Fully executable guidance: a complete command block with absolute paths and subcommands (".../mac-release status", "release", "verify-appcast [version]"), a precisely enumerated env-var manifest with defaults and a concrete example ("NPM_TOKEN=op://Molty/npm Registry - steipete - Release Automation/registry_token"), and exact failure-recovery rules. This matches the copy-paste-ready, common-cases-covered anchor; not 4 because there are no meaningful gaps.

5 / 5

Workflow Clarity

Validation checkpoints are explicit — the Done checklist ("extracted app passes codesign, spctl, and stapler validate", "downloaded enclosure's EdDSA signature verifies against SUPublicEDKey") plus dedicated verify commands and an error-recovery rule ("inspect existing state and resume the failed step instead of deleting or retagging"). It is not 5 because the order in which to run the commands for a full release is never stated and must be inferred from the command listing; not 3 because checkpoints are explicit rather than implicit or missing.

4 / 5

Progressive Disclosure

The body is well-sectioned (Rules / Commands / Manifest / Done) and points to a real one-level-deep bundle script — "Use scripts/mac-release from this skill", verified to exist with the `#!/bin/bash -p` shebang the body mandates — while the ~1,900-line implementation correctly lives in scripts/lib/ rather than SKILL.md. It is not 5 because the deep credential/keychain protocol (the multi-sentence MAC_RELEASE_CODESIGN_* bullets and 1Password rules) is inlined in SKILL.md with no references/ file to offload it, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

70%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 distinctive, keyword-rich description that names a clear niche with natural trigger terms, but it reads as a tag list rather than action statements and contains no 'Use when...' trigger guidance. Completeness is the main weakness and is capped by the missing trigger clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when releasing or shipping a macOS app, updating the Sparkle appcast, notarizing a build, or publishing a GitHub Release."

Convert noun keywords into concrete actions ("Generate Sparkle appcasts, notarize and staple builds, publish GitHub Releases, bump Homebrew") to raise specificity.

Include common trigger synonyms such as appcast, codesign/Developer ID, and ship/distribute a Mac app.

DimensionReasoningScore

Specificity

The description enumerates five concrete pipeline components — "Sparkle, notarization, GitHub Release, Homebrew, closeout" — alongside a clear domain ("macOS app release"), which matches the 'several specific actions; minor gaps' anchor. It is not 3 (it goes well beyond 1-2 concrete items) and not 5 (coverage omits signing/codesign, appcast generation, and version bump, and items are nouns rather than stated actions).

4 / 5

Completeness

The 'what' is clear (a macOS app release pipeline covering Sparkle, notarization, GitHub Release, Homebrew, closeout), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

It contains natural phrases a user would actually say — "macOS app release", "notarization", "Sparkle", "Homebrew", "GitHub Release" — giving good keyword coverage. It falls short of 5 because common synonyms like appcast, codesign/Developer ID signing, and ship/distribute are missing.

4 / 5

Distinctiveness Conflict Risk

"Sparkle, notarization, GitHub Release, Homebrew" defines a clear macOS-app-release niche with distinct trigger terms and minimal conflict risk against other skills. It is not 4 because the combination is specific enough that no closely related skill would plausibly trigger instead.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

steipete/agent-scripts

Path

skills/release-mac-app/SKILL.md

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.