CtrlK
BlogDocsLog inGet started
Tessl Logo

md-document

Converts long-form markdown (specs, RFCs, reports, plans, explainers) into a single-file, lightly-interactive HTML document with sticky TOC, scrollspy, search filter, code-copy buttons, and design-system-driven brand tokens. Triggers when the markdown-html-orchestrator classifies an input as DOCUMENT, or when invoked directly via /cs:md-document. Reads the design-system config via config_loader.py and inlines the user's 12 derived CSS custom properties; refuses to render if onboarding hasn't run. Single-file output — Google Fonts + Prism.js CDN are the only externals; no framework runtime, no build step. Use after orchestrator routing or after design-system onboarding is confirmed.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 well-organized, action-dense skill body with an executable pipeline and disciplined offloading of detail to bundle files. Minor gaps are an absent explicit per-step validation/retry loop and per-file linking of the references inside the body.

Suggestions

Add an explicit validation/retry checkpoint to the pipeline (e.g., after rendering, assert the output is single-file with only the two permitted CDNs and re-run on failure) to lift workflow_clarity.

Name and link the individual reference files (e.g., 'See references/toc_and_nav_ux.md for TOC behavior selection') in the body so each bundle file is discoverable by path.

Optionally note that re-rendering with a different design_style is the intended recovery path when output looks wrong, making the implicit feedback loop explicit.

DimensionReasoningScore

Conciseness

~105 lines, lean and dense; assumes Claude's competence throughout, explaining no basic concepts, and the citation canon (Shihipar/Tufte/NN/g) is tied to design decisions rather than padding — every token earns its place.

5 / 5

Actionability

Provides a concrete, copy-paste three-step bash pipeline with real script paths and flags ('--features search,copycode,smoothscroll,scrollspy'), plus an all-in-one sample render — fully executable and covers the common case.

5 / 5

Workflow Clarity

The pipeline is clearly sequenced with numbered, commented steps and precondition refusal gates (< 100 lines, config_loader.setup_completed()), but there is no explicit per-step validate→fix→retry feedback loop within the pipeline itself.

4 / 5

Progressive Disclosure

Body is an overview pointing one level deep to a real references/ (3 files), scripts/ (3 files), and assets/ (template), with clearly signaled navigation ('See references/ for full citations'); individual reference files are not named/linked inline in the body, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, third-person description that names the domain, concrete actions, the output artifact, and explicit trigger conditions, while distinguishing itself from sibling converters. Only minor gap is broader natural-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and the output form: 'Converts long-form markdown (specs, RFCs, reports, plans, explainers) into a single-file, lightly-interactive HTML document with sticky TOC, scrollspy, search filter, code-copy buttons, and design-system-driven brand tokens' — comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (markdown→single-file HTML with named features) and when ('Triggers when the markdown-html-orchestrator classifies an input as DOCUMENT, or when invoked directly via /cs:md-document'; 'Use after orchestrator routing or after design-system onboarding is confirmed').

5 / 5

Trigger Term Quality

Strong natural terms ('specs, RFCs, reports, plans, explainers', 'HTML', 'DOCUMENT', '/cs:md-document') but leans on the converter's own taxonomy; common synonyms like 'docs', 'README', or '.md' extensions are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (long-form single-file documents) with stated routing away from md-review (diff blocks) and md-slides (deck boundaries), plus refusal of off-target input — minimal conflict risk.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.