CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

homebrew

Use when a project depends on Homebrew formulae or casks, when creating or editing a Brewfile, or when adding brew install/upgrade automation to a project.

Quality

75%

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/homebrew/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.

An exceptionally actionable, well-structured operational skill that concentrates on genuinely non-obvious Homebrew behaviors rather than basics Claude already knows. The only improvements are tightening a few persuasive passages and adding an explicit re-validate loop after the check step.

DimensionReasoningScore

Conciseness

Dense with non-obvious operational gotchas ('brew bundle install upgrades by default', 'check exits 1', 'cleanup uninstalls') and version-specific info is properly quarantined in the obsolete-lockfile section; only minor persuasive padding in 'Core Rule' and Step 5 could be trimmed.

4 / 5

Actionability

Fully executable throughout: detection grep commands, an entry-type table, exact flags ('brew bundle install --no-upgrade'), complete copy-paste justfile recipes, and explicit verify commands with exit-code semantics.

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation (Step 6 'brew bundle check'/'list' plus exit-code behavior) and strong warnings on the destructive 'cleanup'; only an explicit fix-and-re-check recovery loop is missing.

4 / 5

Progressive Disclosure

A single well-sectioned file with clear headers, tables, and no nested references; at ~200 lines the lockfile deep-dive and scope-resolution details could arguably live in a reference file, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

56%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 well-targeted, distinctive trigger description with good natural keywords, but it is missing any statement of what the skill does. Adding a leading capability clause would raise both completeness and specificity.

Suggestions

Add a 'what' clause before the triggers, e.g. 'Declares a project's Homebrew dependencies in a Brewfile and drives them with brew bundle. Use when...'

Include 'brew bundle' (and optionally 'brew outdated'/'brew upgrade' as trigger contexts) since bundle is the command the skill centers on.

Mention reviewing or migrating existing loose 'brew install' commands, which is one of the skill's primary use cases in the body but absent from the description.

DimensionReasoningScore

Specificity

Names the domain ('Homebrew formulae or casks') and concrete trigger actions ('creating or editing a Brewfile', 'adding brew install/upgrade automation'), but never states what the skill actually does, so coverage gaps are more than minor.

3 / 5

Completeness

The description is entirely a 'when' clause ('Use when a project depends on... when creating or editing a Brewfile, or when adding...') with no 'what' statement at all; the 'when' is specific but the 'what' is absent, matching the only-'when' anchor.

2 / 5

Trigger Term Quality

Strong natural terms — 'Homebrew formulae', 'casks', 'Brewfile', 'brew install', 'brew upgrade' — that users would genuinely say, but 'brew bundle', the skill's core command, is a notable missing term.

4 / 5

Distinctiveness Conflict Risk

'Homebrew formulae or casks' and 'Brewfile' are highly distinct niche triggers with minimal overlap risk against other skills.

5 / 5

Total

14

/

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

phatblat/dotfiles

Path

.agents/skills/homebrew/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.