CtrlK
BlogDocsLog inGet started
Tessl Logo

documentation-guidance

Use when changing documentation ownership, generated agent guidance, or review auto-fix guidance.

52

Quality

59%

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/documentation-guidance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured internal ownership map with concrete commands, file paths, and drift-check validation checkpoints; its main weakness is that several workflows are embedded in long prose sentences rather than explicit numbered sequences.

DimensionReasoningScore

Conciseness

The body is dense and information-rich with no padding about concepts Claude already knows; a few very long sentences (e.g. the ownership-map and axi-sync bullets) could be tightened slightly, matching the 'efficient with minor over-explanation' anchor.

4 / 5

Actionability

Concrete commands and file paths appear throughout ('Edit the body, then `make skill`', 'make lint fails CI on drift', specific docs/*.md paths), giving mostly executable guidance with only minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

Implicit multi-step sequences carry explicit validation checkpoints—edit body → make skill → make lint drift check, and change guidance → update skill body + axi strings → drift test—though the steps are embedded in prose rather than numbered.

4 / 5

Progressive Disclosure

At roughly 14 lines with two clearly labeled bold sections and no need for external reference files, the content is well-organized and fully self-contained, meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

40%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 gives a clear, specific trigger ('Use when changing...') covering three distinct internal domains, but it omits any statement of what the skill actually does, which caps completeness and specificity.

Suggestions

Add a leading 'what' clause before the trigger, e.g. 'Maintains documentation ownership and generated agent-guidance surfaces. Use when changing documentation ownership, generated agent guidance, or review auto-fix guidance.'

Include a concrete action verb beyond the generic 'changing' (e.g. 'update', 'audit', 'sync') to lift specificity.

Add a couple of natural synonyms users might say (e.g. 'docs ownership', 'agent instructions') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The phrase 'changing documentation ownership, generated agent guidance, or review auto-fix guidance' names three specific domains but the only action verb is the generic 'changing', matching the anchor that names the domain with minimal or generic actions.

2 / 5

Completeness

Only the 'when' is present ('Use when changing...') with no explicit statement of what the skill does, matching the anchor where only 'when' is present without 'what'.

2 / 5

Trigger Term Quality

Terms like 'documentation ownership', 'agent guidance', and 'review auto-fix' are relevant keywords with a clear 'Use when' trigger, but they lean technical and lack common synonyms or variations a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

Three specific internal niches (documentation ownership, generated agent guidance, review auto-fix) form a mostly distinct scope with only minor overlap risk against closely related skills.

4 / 5

Total

11

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
kunchenguid/no-mistakes
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.