CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docs-router

Word/PDF/PPTX/HTML→MD;MD/Word→PDF;new Word;PDF HTML/translate;Excel/xlsm/Mac;photo/signed scan;Mermaid;DOCX review;doc cleanup Reads one bundled Daymade specialist. New slide decks use deck-creator when installed; generic PDF reading/editing and spreadsheet analysis stay with their own Skills. Retired ppt-creator stays manual-only.

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 ./daymade-docs/docs-router/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 router body provides a genuinely actionable selection table with strong disambiguation rules and sensible stop/ask checkpoints, and it avoids teaching Claude anything it already knows. Its main weaknesses are duplicated trigger text, scattered special-case paragraphs, and an abstract path-resolution procedure without a worked example or child-verification failure branch.

Suggestions

Deduplicate the docs-cleaner trigger list, which appears verbatim in both the table row and the closing paragraph — state it once and cross-reference it.

Consolidate the slide-deck guidance (currently spread across two paragraphs plus the description) into a single 'Out of scope' block.

Add a failure branch for child-path verification (what to do when the resolved sibling SKILL.md does not exist) mirroring the existing 'stop instead of guessing' rule for the router's own path.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens, but the docs-cleaner trigger list ('authorized code, script, config, environment, path, deployment, auth, test, or procedure change') appears verbatim twice and slide-deck/PPT guidance is split across overlapping paragraphs, so it could be tightened.

3 / 5

Actionability

The routing table supplies exact copy-paste sibling paths and worked disambiguation examples ('Markdown → PDF selects pdf-creator'), and the instruction-only format is appropriately actionable; the symlink/suite-root resolution step, however, is described abstractly with no concrete command or worked example.

4 / 5

Workflow Clarity

The sequence is clearly ordered ('First find the path...', 'Read the selected child SKILL.md in full before acting; Then load every reference') with explicit checkpoints ('verify that it exists under a docs-router directory', 'stop instead of guessing', 'ask for the missing input or output'), but there is no failure branch for when the selected sibling path fails verification.

4 / 5

Progressive Disclosure

The routing table is a clear, well-signaled one-level index to the sibling SKILL.md files and no bundle files exist to organize, but the body uses a single heading with special-case prose blocks (Chinese guide, website→Markdown, deck-creator, docs-cleaner) run together, leaving minor navigation gaps.

4 / 5

Total

15

/

20

Passed

Description

66%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 broad set of concrete document capabilities and thoughtfully excludes neighboring skills, but its telegraphic abbreviation style obscures some actions and it entirely lacks an explicit 'when to use' trigger clause. Adding natural trigger phrasing and unpacking compressed tokens would materially improve it.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks to convert Word/PDF/PPTX/HTML to Markdown, produce a PDF from Markdown, or extract DOCX review comments') — its absence currently caps completeness at 3.

Replace telegraphic domain tokens with named actions, e.g., 'Excel/xlsm/Mac' → 'Create Excel workbooks, parse .xlsm models, control Excel on macOS', and 'doc cleanup' → 'check documentation impact after code changes'.

Spell out natural synonyms and extensions users actually say — 'Markdown' instead of 'MD', 'convert', '.docx', '.pdf', '.html' — to strengthen trigger-term matching.

DimensionReasoningScore

Specificity

The description lists multiple concrete conversion actions ('Word/PDF/PPTX/HTML→MD;MD/Word→PDF', 'photo/signed scan', 'DOCX review'), but telegraphic tokens like 'Excel/xlsm/Mac' and 'doc cleanup' name domains without expressing the action, leaving minor clarity gaps.

4 / 5

Completeness

A clear 'what' is present ('Reads one bundled Daymade specialist' plus the conversion list), but there is no 'Use when...' clause or equivalent explicit trigger guidance — only exclusion statements about what stays with other skills — which caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage including file extensions ('PPTX', 'xlsm', 'Mermaid', 'translate', 'signed scan'), but abbreviations like 'MD' and missing synonyms/extensions ('Markdown', 'convert', '.pdf', '.docx') leave a few natural terms absent.

4 / 5

Distinctiveness Conflict Risk

Explicit carve-outs ('generic PDF reading/editing and spreadsheet analysis stay with their own Skills', 'Retired ppt-creator stays manual-only') mark a deliberate niche, but the trigger terms (Word, PDF, Excel) overlap heavily with generic document-skill domains, keeping minor conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

daymade/claude-code-skills

Path

daymade-docs/docs-router/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.