CtrlK
BlogDocsLog inGet started
Tessl Logo

release-mac-app

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

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/release-mac-app/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, highly actionable, and well-structured with concrete commands and explicit verification checkpoints appropriate to a destructive release workflow. Minor gaps are non-portable command paths and an implicit rather than numbered step sequence.

DimensionReasoningScore

Conciseness

Dense, technical, and free of concepts Claude already knows; a few manifest entries (codesign keychain, OP env refs) run long and could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Concrete, copy-paste-ready commands (status, notes, make-appcast, release, codesign-run) and explicit required manifest fields; the hardcoded /Users/steipete/ absolute paths are a minor portability gap.

4 / 5

Workflow Clarity

Validation is present (verify-appcast, check-assets, and a 'Done' checklist of codesign/spctl/stapler checks), satisfying the destructive-operation requirement; the step sequence is only implicit via command order rather than an explicit numbered flow, so it does not reach 5.

4 / 5

Progressive Disclosure

Well-organized into Rules, Commands, Manifest, and Done with a real one-level bundle reference (scripts/mac-release); the large inline manifest reference could arguably live in a separate file, a minor organization gap.

4 / 5

Total

16

/

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.

The description is specific and well-targeted to a distinct macOS release niche, with good trigger keywords. Its main weakness is the absence of an explicit 'Use when...' clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when releasing or updating a Sparkle-updated macOS app, notarizing a build, or publishing a GitHub Release / Homebrew formula.'

Include a few more natural synonyms such as 'sign', 'distribute', and 'appcast' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete release phases ('Sparkle, notarization, GitHub Release, Homebrew, closeout'), giving comprehensive coverage of the macOS release pipeline; falls short of 5 because they are terse nouns rather than fully spelled-out actions.

4 / 5

Completeness

The 'what' is clear (macOS app release with named phases) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural keywords ('macOS app release', 'notarization', 'GitHub Release', 'Homebrew') that a user would say; a few natural synonyms like 'sign', 'distribute', or 'appcast' are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Sparkle-updated macOS app releases with notarization and Homebrew) with distinct triggers and minimal overlap risk with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.