CtrlK
BlogDocsLog inGet started
Tessl Logo

update-project-dependencies

Use this if you want to update all project dependencies while respecting semver compatibility.

60

Quality

68%

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/update-project-dependencies/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, executable workflow with concrete commands and a validation checkpoint, scoring consistently strong across all dimensions. Its main limitation is the absence of a true error-recovery feedback loop and minor redundant command explanations.

DimensionReasoningScore

Conciseness

The body is lean with numbered steps and short code blocks, but the two explanatory notes restating what 'go get -u' and 'pnpm update' do are minor over-explanation Claude does not need.

4 / 5

Actionability

Provides copy-paste-ready commands for both ecosystems plus a concrete report template, but leaves programmatic previous-vs-updated version extraction to inference rather than showing a complete example.

4 / 5

Workflow Clarity

A clear five-step sequence includes an explicit test-validation checkpoint and a halt-on-failure rule, but it deliberately omits a fix-and-re-validate feedback loop, which is a minor validation gap versus anchor 5.

4 / 5

Progressive Disclosure

A self-contained, single-purpose skill is well-organized into clean sections with no nested references, but it is a flat file slightly over the 50-line simple-skill benchmark with no overview-to-detail split.

4 / 5

Total

16

/

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 clearly states its purpose and includes an explicit trigger clause, but it relies on a single action verb and one restating trigger phrase rather than enumerating specific actions and varied trigger terms. It is distinct but not yet comprehensive.

Suggestions

List concrete actions explicitly (e.g., 'updates Go and npm dependencies, runs go mod tidy, and verifies with tests') to lift specificity toward 5.

Add varied natural trigger phrases and synonyms such as 'bump dependencies', 'upgrade packages', or 'keep deps fresh' alongside file hints like go.mod and package.json.

Provide multiple 'when' situations (e.g., 'Use when the user asks to update, upgrade, or bump project dependencies') rather than restating the action as the trigger.

DimensionReasoningScore

Specificity

Names the domain (project dependencies) with one concrete action (update) plus a semver constraint, but does not list several specific actions as required for a 4.

3 / 5

Completeness

Both 'what' (update dependencies respecting semver) and an explicit 'when' ('Use this if you want to...') are present, but the trigger is a single restating clause rather than diverse concrete trigger phrases.

4 / 5

Trigger Term Quality

'update all project dependencies' is a genuinely natural phrase, but no synonyms ('bump deps', 'upgrade packages') or file/extension terms are included, leaving coverage incomplete.

3 / 5

Distinctiveness Conflict Risk

The semver-compatibility constraint carves a clear niche, though 'update dependencies' is common enough to carry minor overlap risk with broader dependency skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
chattocorp/chatto
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.