CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs-onboard

Use when onboarding onto a module and need a quick summary of its structure, patterns, and key files.

Quality

78%

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 ./packs/react/skills/docs-onboard/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 lean, well-structured read-only skill that assumes Claude's competence and gives a concrete output template. Its main weakness is minor actionability gaps — the endpoint grep is described but not specified — and no handling for a missing module argument.

DimensionReasoningScore

Conciseness

Every line is directive with zero padding ('Components > 200 lines?', 'Legacy code not yet migrated? (class components, Redux, PropTypes)') and no explanation of concepts Claude already knows; the parentheticals like '(client state)' serve as disambiguation, not padding.

5 / 5

Actionability

Provides a copy-paste command ('find src/modules/$ARGUMENTS -type f | head -40') and concrete checks, but 'List the consumed endpoints (grep in services)' hints at a grep without giving the actual command. Mostly executable with minor gaps, matching anchor 4 rather than 3 since the template sections are specific and actionable.

4 / 5

Workflow Clarity

Clear 3-step sequence (map structure, summarize in defined format, output 2-minute-readable summary) with a concrete output template. Minor gaps: no handling for a missing or incorrect module argument, and endpoint discovery is loosely defined ('grep in services'); anchor 5's explicit validation checkpoints are absent, though the read-only nature means no destructive-operation cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no bundle files exist) and uses well-organized ## Steps / ### subsections, matching the simple-skill exception where progressive disclosure scores 5 with just well-organized sections.

5 / 5

Total

18

/

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 follows the 'Use when...' pattern and states both what and when in third person, but is thin on action specificity and trigger variations. It would benefit from naming the concrete actions performed (map structure, list endpoints, assess state management, flag legacy code) and additional natural trigger phrases.

Suggestions

Name the concrete actions the skill performs rather than one generic 'summary' — e.g., 'Maps module structure, lists endpoints and component responsibilities, identifies Zustand vs React Query state, and flags legacy code.'

Add trigger phrase variations users would naturally say, such as 'understand a module', 'get up to speed on', or 'module overview', to broaden natural keyword coverage.

Since the skill is frontend-specific (Zustand, React Query, TSX), mention the stack in the description so it does not trigger for non-React module onboarding.

DimensionReasoningScore

Specificity

Names the domain ('onboarding onto a module') and deliverables ('structure, patterns, and key files'), but the action itself is a single generic one — 'quick summary'. Matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 because it does not list several distinct actions.

3 / 5

Completeness

Explicitly answers both: what ('quick summary of its structure, patterns, and key files') and when ('Use when onboarding onto a module'). Not 5 because the when-clause offers a single trigger without concrete phrase variations or synonyms.

4 / 5

Trigger Term Quality

'onboarding onto a module' is a natural trigger phrase, but common variations users would say — 'understand this module', 'get up to speed on', 'module overview' — are missing. Some relevant keywords with missing variations matches anchor 3; not 4 because coverage is narrow for the niche.

3 / 5

Distinctiveness Conflict Risk

'Onboarding onto a module' carves a fairly distinct niche with a clear trigger that is unlikely to fire for unrelated skills. Minor overlap risk with general code-exploration/explanation skills keeps it at anchor 4 rather than 5.

4 / 5

Total

14

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

fernandezbaptiste/specialist-agent

Path

packs/react/skills/docs-onboard/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.