CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

developer-docs

Find, read, and apply authoritative developer documentation during implementation

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/dev/developer-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, well-structured instruction-only skill: lean prose, an explicit 5-step procedure, guardrail pitfalls, and a verification checklist. The only gaps are the absence of concrete examples/commands and explicit error-recovery loops.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with zero padding: every line in 'When to Use', 'Procedure', 'Pitfalls', and 'Verification' is directive guidance, with no explanations of concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

Concrete, directive steps ('Prefer the vendor's or project's primary documentation, source repository, release notes, and API reference', 'add a focused regression test... and run it before reporting completion') give mostly executable guidance for an instruction-only skill. It falls short of 5 because there are no concrete examples or commands (e.g., a sample doc citation, an example verification command).

4 / 5

Workflow Clarity

A clear 5-step numbered sequence with explicit checkpoints (step 5 requires running a regression test before reporting completion, and the 'Verification' section is an explicit checklist). It misses 5 because error-recovery feedback loops (e.g., what to do when retrieved docs don't match the installed version) are only implicit, not stated as validate -> fix -> retry.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into four well-labeled sections (When to Use, Procedure, Pitfalls, Verification), which per the rubric's simple-skill guideline earns a top score with just well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

50%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 communicates a clear purpose but is middling across all dimensions: generic verbs, sparse trigger keywords, no explicit 'Use when' clause, and moderate overlap risk with other documentation-oriented skills. It is serviceable but leaves discovery and routing under-specified.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks how a library, framework, API, protocol, CLI, or SDK works, or when implementation depends on version-specific behavior' — the body's 'When to Use' section already contains this text and can be lifted into the description.

Include natural synonyms and trigger terms users actually say, such as 'docs', 'API reference', 'release notes', and 'version-specific behavior', to raise trigger-term coverage.

Make the actions more outcome-specific (e.g., 'Check vendor docs, release notes, and API references for the exact version; apply documented behavior and flag assumptions') instead of the generic 'find, read, and apply'.

DimensionReasoningScore

Specificity

'Find, read, and apply' names three actions on the 'authoritative developer documentation' domain, but the verbs are generic and coverage is not comprehensive (no mention of API references, release notes, version pinning, or code changes). This matches anchor 3 (domain plus limited concrete actions) better than anchor 4's several specific, outcome-oriented actions.

3 / 5

Completeness

The 'what' is clear ('Find, read, and apply authoritative developer documentation'), but there is no 'Use when...' clause; 'during implementation' is only a weak, implied trigger context, so completeness is capped at 3 per the judging guidelines. Not 4, which requires an explicit 'when' like 'Use when working with X'.

3 / 5

Trigger Term Quality

'developer documentation' and 'implementation' are relevant keywords, but the description misses the natural terms users actually say ('docs', 'API reference', 'library', 'framework', 'SDK', version-specific behavior). Some relevant keywords with missing variations and synonyms maps to anchor 3.

3 / 5

Distinctiveness Conflict Risk

'developer documentation' names a recognizable niche but is broad enough to overlap with general web-search, API-reference, or vendor-specific documentation skills. It is somewhat specific with residual overlap risk (anchor 3) rather than 'mostly distinct' (anchor 4).

3 / 5

Total

12

/

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

odysseus-dev/odysseus

Path

resources/skills/dev/developer-docs/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.