dependency-update

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

Quality

53%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/dependency-update/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a reasonable checklist-style workflow for checking dependency sync, with a useful report template. Its main weakness is that steps 2-4 are abstract review instructions rather than concrete, executable checks—there are no actual commands or scripts to programmatically verify whether manifests are in sync. The workflow also lacks a validation/feedback loop after making updates.

Suggestions

Replace the vague 'Review whether' checklists in steps 2-4 with concrete commands or grep patterns that can programmatically detect missing dependencies (e.g., grep for tool names in lib/*.sh and cross-reference against Formula depends_on entries).

Add a validation step after updates are made: re-run the sync check to confirm everything is now in sync before finishing.

Trim the 'When to Run' section—Claude can infer trigger conditions from the steps themselves; a single sentence would suffice.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanation. The 'When to Run' section and step descriptions are slightly verbose—Claude could infer much of this context. The report template is useful but adds length.	2 / 3
Actionability	Provides a concrete git diff command and a clear report template, but steps 2-4 are review checklists with vague guidance ('Review whether new depends_on entries are needed') rather than executable commands or specific checks. No concrete code to actually verify sync.	2 / 3
Workflow Clarity	Steps are clearly sequenced and the report template provides a structured output format. However, there are no validation checkpoints or feedback loops—if something is out of sync, the skill just says 'offer to make them' without a verify-after-fix step.	2 / 3
Progressive Disclosure	For a skill of this size and scope (single-purpose, under 50 lines, no bundle files), the content is well-organized with clear sections and doesn't need external references. The structure is clean and easy to navigate.	3 / 3
	Total	9 / 12 Passed

Description

50%

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 adequately identifies its domain (Homebrew-related dependency management) and a core action (checking for needed updates), but it lacks explicit trigger guidance ('Use when...'), comprehensive action listing, and broader keyword coverage. It sits solidly at a mid-level quality—functional but not optimally discoverable or distinguishable.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when Homebrew dependencies, Brewfile, or Formula files may be out of sync with project changes.'

Include more natural trigger terms users would say, such as 'Homebrew', 'brew', 'package manager', 'brew install', 'tap'.

List more specific concrete actions, e.g., 'Checks Brewfile for missing or outdated formulae, validates Formula definitions, and updates install scripts to match current project dependencies.'

Dimension	Reasoning	Score
Specificity	Names the domain (Homebrew/Brewfile) and a general action (check if updating is needed), but doesn't list multiple concrete actions like 'add new formulae', 'remove stale entries', 'sync versions'.	2 / 3
Completeness	Describes what it does (check if Brewfile/Formula/install script need updating) and implies when (when project dependencies change), but lacks an explicit 'Use when...' clause with clear trigger guidance.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Brewfile', 'Formula', 'install script', and 'dependencies', but misses common user-facing terms like 'Homebrew', 'brew', '.rb', 'tap', or 'package manager'.	2 / 3
Distinctiveness Conflict Risk	The mention of Brewfile and Formula provides some specificity to the Homebrew ecosystem, but 'install script' and 'project dependencies change' are broad enough to potentially overlap with other dependency management skills.	2 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: AndreJorgeLopes/devflow
Commit: 8d872bf

Reviewed: 1 day 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.