CtrlK
BlogDocsLog inGet started
Tessl Logo

squad-version-check

Internals of how @bradygaster/squad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.

59

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 ./.squad/skills/squad-version-check/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 body is a well-structured, token-efficient reference with executable one-liners, exact paths/regex, and a clear probe workflow including error fallback. It earns consistent 4s; reaching 5 would require fuller copy-paste function bodies and/or splitting long reference tables into bundle files.

DimensionReasoningScore

Conciseness

Lean bullets, exact regex, commands, and a summary table with no padding or re-explanation of concepts Claude already knows; a few explanatory parentheticals could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready one-liners (`npm view ... dist-tags --json`, the node cache reader, `npm install -g @bradygaster/squad-cli@latest`), exact regex, and precise file paths, with minor gaps where full function bodies are summarized rather than shown.

4 / 5

Workflow Clarity

The version-check probe is sequenced with explicit timeout (5s) and error fallback ('On any error ... show normal greeting'); as a reference/knowledge skill it has no destructive batch operation lacking validation.

4 / 5

Progressive Disclosure

Self-contained single file with well-organized section headers and a key-paths table; no bundle files exist and none are needed, with only minor organization gaps versus a fully split structure.

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 is specific and occupies a clear, low-conflict niche, but it lacks an explicit 'Use when' trigger clause and leans on technical jargon over natural user phrases. Adding a trigger clause and a few synonyms would lift completeness and trigger-term quality.

Suggestions

Append a 'Use when ...' clause naming concrete trigger phrases (e.g., 'Use when investigating squad-cli version stamping, planning a `squad upgrade`, or checking the latest squad-cli version from a coordinator prompt').

Add natural synonyms and file/extension cues users might say ('squad CLI', 'squad-cli upgrade', 'npm dist-tags') to broaden trigger-term coverage.

Rephrase in third-person action voice only if any first/second person creeps in; currently voice is fine but ensure the added trigger clause stays third-person.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('stamps its version', 'how `squad upgrade` works (what it preserves vs overwrites)', 'probe the npm registry for the latest version'), with only minor coverage gaps.

4 / 5

Completeness

Clearly answers 'what' the skill covers, but provides no 'when'/'Use when' trigger clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant natural terms ('squad upgrade', 'npm registry', 'latest version') but is jargon-heavy and missing common synonyms or a 'Use when' phrasing users would naturally say.

3 / 5

Distinctiveness Conflict Risk

Targets a highly specific niche (@bradygaster/squad-cli version stamping and upgrade internals) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.