CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-test

Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.

Quality

72%

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 ./.claude/skills/skill-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an exceptionally actionable, well-sequenced instruction set with complete output templates, explicit failure handling, and clear verdict logic — near the top of the actionability and workflow-clarity scales. Its weaknesses are the ~600-line monolithic layout that would benefit from per-mode reference files, and repetitive passages (the NOT ASSESSED ranking rules) that inflate token cost without adding guidance.

Suggestions

Move each mode's full specification (Phase 2A/2B/2C/2D) into references/ files (e.g. references/static-mode.md, references/spec-mode.md) and keep SKILL.md as the argument-parsing hub with one-line pointers, so a single-mode invocation loads only what it needs.

State the NOT ASSESSED ranking (FAIL < PARTIAL < NOT ASSESSED < PASS) once in a shared section and reference it from the three places that currently re-derive it.

Trim the justificatory blockquotes (e.g. the gate-verdict list rationale in Check 3) to a single sentence each — the design reason is useful, the full argument is not needed at run time.

DimensionReasoningScore

Conciseness

The body is mostly tight imperative instructions, but the NOT ASSESSED ranking is re-explained in three separate places (static output rules, spec assertion rules, category verdict) and several justificatory asides ("A linter that produces false failures on legitimate patterns stops being trusted") could be trimmed — mostly efficient but could be tightened.

3 / 5

Actionability

Fully executable for an instruction-only skill: exact commands ("bash .claude/scripts/agent-check.sh --skill [name]"), complete copy-paste output templates for every mode, exact error messages to print ("Spec file missing at [path]. Run /skill-test audit..."), and explicit verdict aggregation orderings — specific examples cover the common cases.

5 / 5

Workflow Clarity

Sequencing is explicit (Phase 1 parse arguments → mode-specific phases → Phase 3 handoff) with numbered steps inside each mode, and failure paths are handled everywhere (missing catalog, missing spec, unparsable frontmatter, script cannot run → "not run (<reason>)"), with verdict-to-Recommended-fix feedback loops throughout.

5 / 5

Progressive Disclosure

The single SKILL.md inlines ~600 lines including four substantial per-mode specifications that load into context on every invocation even when only one mode runs; internal structure is well-headed, but this content plainly belongs in one-level-deep references/ files, matching the 'content that should be separate is inline' anchor.

3 / 5

Total

16

/

20

Passed

Description

58%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 answers "what" concretely with a well-defined niche and four named modes, but entirely omits "when" guidance and misses the natural trigger terms (test, check) users would most likely say. It is a solid, specific description held back from good-to-excellent by the missing use-when clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked to test, lint, or audit skills in .claude/skills/ or agents in .claude/agents/" — this would raise completeness and trigger-term quality together.

Include natural synonyms users would say ("test", "check", "lint") alongside the formal terms to broaden trigger coverage.

Briefly say what each mode does (e.g. "static lints structure, spec checks behavior against test specs") so the four mode labels carry meaning on their own.

DimensionReasoningScore

Specificity

Names the domain ("skill files") and the action ("Validate ... for structural compliance and behavioral correctness") and lists four concrete modes ("static linter, spec, category rubric, audit"), but the modes are bare labels without saying what each does — minor gaps in coverage keep it below anchor 5.

4 / 5

Completeness

The "what" is clear (validates skill files across four named modes), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant keywords are present ("skill", "validate", "audit", "linter"), but common natural variations a user would say — "test", "check my skill" — are absent, and "spec" and "category rubric" are niche jargon, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — meta-validation of skill files — that few skills would overlap with, though "static linter" could mildly collide with a generic code-lint skill and no explicit triggers distinguish it; mostly distinct with minor overlap risk.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (617 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/skill-test/SKILL.md

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.