CtrlK
BlogDocsLog inGet started
Tessl Logo

update-project-dependencies

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

66

Quality

78%

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

100%

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 lean, fully actionable, well-sequenced workflow with explicit validation and a clear report structure, requiring no external references.

DimensionReasoningScore

Conciseness

The body is lean: direct commands with no concept over-explanation, no library comparisons, and no padding; the two brief notes tie directly to the semver-respecting intent rather than restating generic knowledge Claude lacks, matching anchor 3's lean-and-efficient standard.

3 / 3

Actionability

It provides fully executable, copy-paste-ready commands ("go get -u ./...", "go mod tidy", "pnpm update", "mise run test") with specific file paths (cli/go.mod, frontend/package.json) and a concrete report template, matching anchor 3.

3 / 3

Workflow Clarity

Five steps are clearly numbered with an explicit validation checkpoint (run tests) and an explicit failure policy (stop and report, do not rollback); the deliberate terminal handling is documented rather than implicit, matching anchor 3's clear-sequence-with-validation standard.

3 / 3

Progressive Disclosure

A single self-contained, well-organized file with clear sections and no need for external references fits the simple-skill carve-out (well-organized sections scoring 3), and no bundle files are referenced.

3 / 3

Total

12

/

12

Passed

Description

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 and includes an explicit trigger clause, but the trigger is circular and the action language is broad, with limited coverage of natural trigger terms.

Suggestions

Replace the circular trigger with distinct usage contexts, e.g. "Use when the user asks to bump/upgrade dependencies, fix outdated packages, or update Go/npm modules within semver ranges."

Add concrete actions to broaden specificity, e.g. "Update Go modules and frontend npm packages, then run the test suite."

Include more natural trigger terms users actually say ("bump", "upgrade", "outdated", "packages").

DimensionReasoningScore

Specificity

"update all project dependencies" names a concrete domain and a single action, but offers only one broad action rather than multiple specific concrete actions, matching anchor 2; it is more concrete than "Helps with documents" (1) but less rich than "Extract text and tables, fill forms, merge documents" (3).

2 / 3

Completeness

It states what the skill does and includes a "Use this if you want to..." trigger clause, but the when is circular (the trigger merely restates the action) rather than offering distinct trigger contexts, so it falls short of anchor 3's clearly distinct what-and-when; it is above 1 because both elements are present.

2 / 3

Trigger Term Quality

"update all project dependencies" and "semver compatibility" are reasonably natural terms, but common variations a user would say ("bump", "upgrade", "outdated packages", "npm/go") are missing, matching anchor 2's "some relevant keywords but missing common variations".

2 / 3

Distinctiveness Conflict Risk

"update all project dependencies while respecting semver compatibility" carves a clear niche (semver-respecting dependency updates) unlikely to fire for unrelated skills, matching anchor 3; it is more specific than anchor 2's "Works with document files".

3 / 3

Total

9

/

12

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.