CtrlK
BlogDocsLog inGet started
Tessl Logo

update-project-dependencies

Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.

64

Quality

76%

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%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 exemplary: a tight, fully executable, well-sequenced workflow with explicit validation and a feedback loop, and no unnecessary explanation. No bundle files are referenced or needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: each numbered step adds only what Claude would not infer, with no padding or explanation of basic concepts, so every token earns its place.

5 / 5

Actionability

It provides fully executable, copy-paste-ready commands (e.g. "mise x -- go get -u ./...", "mise x -- go mod tidy", "mise x -- pnpm update", "mise test") tied to concrete paths (cli/, apps/frontend/), covering the common cases.

5 / 5

Workflow Clarity

A clear six-step sequence includes an explicit validation checkpoint (step 5: run tests, stop and report on failure) with a defined feedback loop (leave changes for review, do not auto-rollback), appropriate for this batch dependency operation.

5 / 5

Progressive Disclosure

This short single-purpose skill is under 50 lines, needs no external bundle files, and is well-organized into a clear numbered workflow, so the simple-skill exception applies and structure is optimal.

5 / 5

Total

20

/

20

Passed

Description

53%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 concise and names concrete actions with a clear scope, but it omits any explicit trigger guidance for when to use the skill, which caps completeness and limits trigger-term quality. Adding a "Use when..." clause would materially raise the score.

Suggestions

Append an explicit trigger clause, e.g. ".Use when updating Go (cli/go.mod) or frontend (apps/frontend/package.json) dependencies, or when the user asks to bump/refresh dependencies and run tests."

Broaden trigger-term coverage by mentioning concrete artifacts users reference, such as "go.mod", "package.json", "pnpm-lock.yaml", and "lockfile".

Surface the additional concrete actions the body covers (record current versions, review manifest/lockfile changes, report results) to move specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Chatto Go and frontend dependencies") and two concrete actions ("Update ... within their compatible version ranges" and "run tests"), but coverage is not comprehensive, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It gives a clear "what" (update dependencies within compatible ranges, then run tests) but provides no "when" / "Use when..." trigger guidance; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant natural terms like "dependencies", "frontend", "version ranges", and "tests", but misses common variations or synonyms a user might say (e.g. "packages", "pnpm", "go.mod", "lockfile").

3 / 5

Distinctiveness Conflict Risk

Naming the specific product scope ("Chatto Go and frontend dependencies") makes it mostly distinct with only minor overlap risk against generic dependency-management skills, sitting just above the midpoint anchor.

4 / 5

Total

13

/

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.