dependency-update

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dependency-update/SKILL.md

Quality

Content

68%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 tight, actionable dependency-sync check workflow with a concrete git command and a usable report template, organized into clean sections. Its main gap is the absence of explicit validation checkpoints in the workflow, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint after the diff, e.g. 'If no dependency-sensitive files changed, report IN SYNC and stop.'

Before offering to make edits in step 6, insert a verification step (re-read the manifest, confirm the needed change is real) to establish a validate-fix-retry feedback loop.

Provide one concrete example edit command per artifact (e.g., the `depends_on` line to add) to lift actionability toward 5.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence and avoids explaining what a Brewfile or formula is; the report template placeholders are useful structure rather than padding, leaving only minor trims — just short of the fully lean 5 anchor.	4 / 5
Actionability	Provides an executable `git diff --name-only HEAD~1..HEAD` command, concrete per-artifact review bullets, and a copy-paste report template — mostly executable with only minor gaps (no concrete commands for the Formula/Brewfile edits).	4 / 5
Workflow Clarity	A clear 6-step sequence with a structured report exists, but validation checkpoints are implicit (e.g., confirming the diff is dependency-relevant before reporting, verifying before applying edits) and step 6's edit offer lacks an explicit validation/feedback loop.	3 / 5
Progressive Disclosure	Well-organized single-level sections (When to Run, Steps) with no nested references and no bundle files present; as a compact single-purpose skill it is well-structured, just shy of the 5 anchor which expects clearly signaled one-level-deep references.	4 / 5
	Total	15 / 20 Passed

Description

58%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 concrete and targeted to a specific niche, naming the three relevant manifest artifacts and the triggering condition. Its main weakness is the absence of an explicit 'Use when...' trigger clause and a thin set of natural trigger synonyms, which cap completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when devflow dependencies change, or when Brewfile, Formula, or install.sh are modified.'

Include natural synonyms/extensions a user might say, such as 'homebrew', 'brew', 'brewfile', and '.rb formula'.

Optionally enumerate one concrete action per artifact (e.g., 'add depends_on entries', 'add brew packages', 'cover new tool installs') to lift specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions across three named artifacts ('Check if Brewfile, Formula, or install script need updating'), with only minor coverage gaps — below 5 because it doesn't enumerate multiple distinct concrete actions per artifact.	4 / 5
Completeness	A clear 'what' is present, and 'when' is only weakly implied via 'when project dependencies change' with no explicit 'Use when...' clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords like 'Brewfile', 'Formula', 'install script', and 'project dependencies change' are present, but common natural variations a user would say ('homebrew', 'brew', 'dependency sync') and file extensions are missing.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (keeping a Brewfile/Formula/install script in sync with code changes) with mostly distinct triggers and only minor overlap risk with related build/deploy skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: bd4b70c

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.