dependency-update

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

Quality

57%

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

Discovery

57%

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 identifies a clear niche around Homebrew dependency management and mentions specific artifacts (Brewfile, Formula, install script), which aids distinctiveness. However, it lacks an explicit 'Use when...' clause, could list more concrete actions, and would benefit from additional natural trigger terms like 'Homebrew' or 'brew'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when project dependencies change and Homebrew packaging artifacts (Brewfile, Formula, install script) may need updating.'

Include additional natural trigger terms such as 'Homebrew', 'brew', 'package manager', and 'tap' to improve keyword coverage.

List more specific concrete actions, e.g., 'Checks for missing or outdated formulae in Brewfile, updates install scripts, and syncs Formula versions with 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 variations like 'Homebrew', 'brew', 'package manager', '.rb formula', or 'tap'.	2 / 3
Distinctiveness Conflict Risk	The combination of Brewfile, Formula, and install script creates a clear niche around Homebrew packaging that is unlikely to conflict with other skills. The scope is well-defined and distinct.	3 / 3
	Total	9 / 12 Passed

Implementation

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 and clear structure. However, it lacks concrete, executable verification commands for steps 2-4 (relying on vague 'review whether' guidance instead of specific checks), and it's missing a validation/feedback loop after making updates. The skill would benefit from more actionable, automatable checks rather than manual review instructions.

Suggestions

Replace vague 'Review whether' instructions in steps 2-4 with concrete commands or grep patterns to detect mismatches (e.g., `grep -o 'depends_on.*' Formula/devflow.rb` compared against tools referenced in changed shell scripts).

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

Remove the trailing `$ARGUMENTS` placeholder or replace it with actual argument documentation if arguments are expected.

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 navigable.	3 / 3
	Total	9 / 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: b0b1bb6

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