CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

get-skill-reference

Get skill reference documentation for additional guidance. When you need to get detailed technical docs, find examples, or understand advanced usage.

Quality

74%

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 ./skills/system/get-skill-reference/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 an exemplar of token efficiency: a minimal, well-organized tool description with a concrete parameter table and no wasted words. Its only weakness is actionability — it documents the parameters but gives no example invocation, no description of the response, and no guidance on discovering which reference documents exist. Adding a short usage example would close the gap without hurting conciseness.

Suggestions

Add a minimal example invocation showing skill_name and an optional ref_name, e.g. how to request REFERENCE.md versus another reference document.

Briefly state what the tool returns (the reference document's content) and how to enumerate available reference documents for a skill, so the reader knows what to do with the result.

DimensionReasoningScore

Conciseness

The body is roughly 15 lines with zero padding: a one-line purpose statement, a parameter table, and a short related-skills list. It assumes Claude's competence and never explains concepts Claude already knows, matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

The parameter table is concrete (names, types, required flags, and the REFERENCE.md default for ref_name), but there is no example invocation, no description of the returned output, and no guidance on how to discover available reference documents — concrete guidance that is incomplete rather than mostly executable.

3 / 5

Workflow Clarity

As a simple single-action tool skill, the parameter table makes the single action unambiguous (pass skill_name, optionally ref_name). Minor gaps keep it below 5: no example call, no note on what to do with the returned documentation, and no hint about when to pass a non-default ref_name.

4 / 5

Progressive Disclosure

The skill is well under 50 lines, needs no external reference files (none exist in the bundle), and is cleanly organized into Parameters and Related Skills sections — satisfying the rubric's simple-skill exception for a full score with just well-organized sections.

5 / 5

Total

17

/

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 follows the good pattern of a what-statement plus an explicit 'When...' clause, but its actions are generic and its trigger phrasing ('detailed technical docs') is broader than the skill's actual niche of retrieving reference documents for named skills. This creates moderate overlap risk with related skills-management tools. Tightening the wording around 'skill reference/documentation' would raise specificity, trigger quality, and distinctiveness together.

Suggestions

Replace the generic actions with concrete ones, e.g. 'Retrieve a skill's reference documents (e.g. REFERENCE.md) by skill name for detailed API details, examples, and advanced usage.'

Make the when-clause niche-specific instead of broad: 'Use when you need a skill's reference documentation, deeper technical details, or usage examples beyond the main SKILL.md description' rather than 'detailed technical docs' which could trigger on any documentation request.

Add natural trigger synonyms users would say — 'skill docs', 'skill reference', 'advanced skill usage' — to distinguish it from sibling skills like get-skill-info.

DimensionReasoningScore

Specificity

Names the domain ('Get skill reference documentation') and offers a couple of actions ('get detailed technical docs, find examples'), but these are generic rather than concrete and specific; it does not list several specific actions with comprehensive coverage as anchor 4 requires.

3 / 5

Completeness

Both parts are present: the what ('Get skill reference documentation for additional guidance') and an explicit when ('When you need to get detailed technical docs, find examples, or understand advanced usage'). The what is somewhat thin and the when-phrases are broad, so it falls short of the clear-and-concrete anchor 5.

4 / 5

Trigger Term Quality

'detailed technical docs', 'find examples', and 'advanced usage' are relevant keywords, but common natural variations like 'reference docs', 'skill documentation', or 'how to use a skill' are missing, matching the some-keywords-but-missing-synonyms anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

'skill reference documentation' carves out a niche, but the trigger phrase 'When you need to get detailed technical docs' is broad enough to fire on general documentation requests, and the skill's own body lists a closely related skill (get-skill-info) it could be confused with — somewhat specific with residual overlap, not 'mostly distinct'.

3 / 5

Total

13

/

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.

Validation — 15 / 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

openakita/openakita

Path

skills/system/get-skill-reference/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.