CtrlK
BlogDocsLog inGet started
Tessl Logo

release-mac-app

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

64

Quality

76%

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 ./skills/release-mac-app/SKILL.md
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.

The body is highly actionable with executable commands, a concrete manifest schema, and a verification checklist, structured into clear sections with real bundle-file references. It could improve by moving the large inline manifest/1Password reference to a separate file and adding an explicit numbered workflow with error-recovery loops.

Suggestions

Extract the long manifest env-var and 1Password rules block into a references/ file (e.g. MANIFEST.md) and link to it from SKILL.md to tighten the overview.

Add an explicitly numbered release workflow (status → notes → changelog-html → make-appcast → verify-appcast → check-assets → release) with 'if validation fails, fix and re-run' feedback loops.

Note that the Commands section uses absolute paths under /Users/steipete/Projects/...; prefer a portable reference (e.g. scripts/mac-release relative to the skill) to avoid environment-specific breakage.

DimensionReasoningScore

Conciseness

Prose is lean and assumes Claude's competence (no explaining what notarization or Sparkle is), with concrete reference detail throughout; only the large inline manifest/env-var block could be trimmed or moved.

4 / 5

Actionability

Provides fully executable commands with full paths and arguments in the Commands section, a concrete manifest schema, and a copy-paste-ready Done checklist covering common cases.

5 / 5

Workflow Clarity

Commands are listed in a natural release sequence with explicit validation checkpoints (verify-appcast, check-assets, Done checklist with codesign/spctl/stapler checks); minor gap is the lack of an explicitly numbered workflow with error-recovery feedback loops.

4 / 5

Progressive Disclosure

Clear section structure (Rules, Commands, Manifest, Done) with one-level-deep references to real bundle files ('scripts/mac-release' verified present); the sizeable inline manifest/1Password reference is the main organization gap that could live in a separate file.

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.

The description is specific and distinct, naming concrete release phases and tooling, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Trigger terms are strong but omit a few natural synonyms.

Suggestions

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

Include a few more natural synonyms users might say ('app signing', 'distribute', 'app update') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('macOS app release') and several concrete phases — 'Sparkle, notarization, GitHub Release, Homebrew, closeout' — giving multiple specific actions, though they are phase labels rather than fully articulated operations.

4 / 5

Completeness

The 'what' is clear (macOS app release with listed phases) but there is no explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural domain terms a release engineer would say ('Sparkle', 'notarization', 'GitHub Release', 'Homebrew', 'closeout'), but misses common synonyms like 'signing', 'distribute', or 'app update'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (macOS app release via Sparkle) with distinct triggers (notarization, Homebrew, Sparkle) 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.