CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dependency-update

Check if Brewfile, Formula, or install script need updating when project dependencies change.

Quality

82%

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

93%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 a model instruction-only skill: concrete, executable, and tightly organized around a single check-and-report workflow. Its only real gap is validation robustness — the diff command assumes exactly one prior commit and the flow ends at 'offer to make changes' without a re-verification step.

DimensionReasoningScore

Conciseness

The body is lean and efficient: no explanations of concepts Claude already knows, and every element (trigger file list, per-manifest checklists, report template, offer step) earns its place. It matches the 'lean and efficient; every token earns its place' anchor rather than 4, where minor padding would remain.

5 / 5

Actionability

It provides a copy-paste-ready command (git diff --name-only HEAD~1..HEAD), concrete per-manifest review criteria with examples (new depends_on entries, PATH setup handles new binaries), and an exact report template covering the common cases — the anchor-5 fit for an instruction-only skill.

5 / 5

Workflow Clarity

A clear six-step sequence with the report/verdict acting as the checkpoint, but minor validation gaps remain: step 1 only inspects the last commit (missing a fallback for multiple commits or uncommitted changes) and no re-check loop after applying updates. This fits 'most checkpoints present; minor validation gaps' rather than 5, and the skill is a read-only check so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

This is a simple, roughly 50-line, single-purpose skill with no bundle files and no need for external references; its well-organized sections (When to Run, Steps, report template) satisfy the rubric's simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

62%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 clear, third-person, and names its concrete artifacts, but it states only a single action and its trigger is an abstract condition rather than natural user phrases. It would benefit most from an explicit 'Use when...' clause with concrete trigger events and synonyms.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger events, e.g., 'Use when lib/*.sh, Makefile, install.sh, or package.json changes introduce new tool dependencies' — this would raise both completeness and trigger term quality.

Include natural synonyms users would actually say, such as 'Homebrew formula', 'brew packages', or 'dependency sync', to improve trigger term coverage.

Name one or two more concrete actions (e.g., 'audit Formula depends_on entries, diff Brewfile layers, and generate a sync report') to lift specificity from a single generic action.

DimensionReasoningScore

Specificity

"Check if Brewfile, Formula, or install script need updating" names concrete artifacts and a single action, but does not enumerate several distinct actions (e.g., audit, diff, sync, report), matching the 'names domain and 1-2 concrete actions' anchor rather than the 'lists several specific actions' anchor above.

3 / 5

Completeness

Both what ("check if Brewfile, Formula, or install script need updating") and when ("when project dependencies change") are explicitly present, but the 'when' is abstract rather than a concrete trigger phrase, so it fits 'when' could be more explicit or specific' rather than the 5 anchor.

4 / 5

Trigger Term Quality

Terms like "Brewfile", "Formula", "install script", and "when project dependencies change" are relevant, but common natural variations users would say ("Homebrew formula", "brew packages", "dependency sync") are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Brewfile/Formula/install-script combination carves a mostly distinct niche with minor overlap risk against generic dependency-update skills, fitting 'mostly distinct; minor overlap risk' rather than 5 since 'dependencies change' is broad.

4 / 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

AndreJorgeLopes/devflow

Path

skills/dependency-update/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.