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.

64

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 ./.gemini/skills/md-document/SKILL.md

The canonical home for this skill is md-document in alirezarezvani/claude-skills

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.

A well-structured, actionable skill body with a clear pipeline, decision table, and hard rules. The main weakness is conciseness — named-source 'canon' attributions pad the forcing-question library and references without aiding execution.

Suggestions

Trim the provenance attributions ('Canon: ...', named-author discipline labels) from the forcing-question library; keep the recommendations, drop the citations or move them entirely to references/.

Add an explicit post-render validation step (e.g., open the HTML / check for unexpanded tokens) to turn the pipeline into a validate→fix→retry loop.

Ensure the referenced `references/` directory and the three scripts actually ship alongside SKILL.md so the one-level-deep references resolve.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining basics, but provenance padding ('Canon: Shihipar; Tufte Envisioning Information', 'Matt Pocock grill discipline', repeated named-source attributions) adds tokens that do not aid execution and could be tightened.

3 / 5

Actionability

The Pipeline section gives full, concrete `python3 ... --input/--output` commands and a sample all-in-one render, which is mostly copy-paste ready; only minor gaps remain from templated `<path>.md` placeholders and omitted flag defaults.

4 / 5

Workflow Clarity

A clearly numbered three-step pipeline plus a 'When to invoke' decision table and precondition refusals gives a clear sequence with most checkpoints present; no explicit validate→fix→retry loop on the rendered output, a minor validation gap.

4 / 5

Progressive Disclosure

Well-organized into distinct sections (When to invoke, Pipeline, What gets rendered, Hard rules, Distinct from, References) with one-level-deep signaling ('See references/ for full citations'); the referenced references/ and scripts/ bundle paths are not present in this review workspace, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

88%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 states concrete capabilities and explicit trigger conditions with clear what/when coverage. Minor room to add user-natural synonyms and file extensions to the trigger terms.

Suggestions

Add natural trigger synonyms users actually say ('.md files', 'markdown specs', 'convert this report to a webpage') alongside the orchestrator-routing language.

Keep the explicit 'Triggers when ... / Use after ...' clauses — they are the strongest part of the description and should not be trimmed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and features — 'sticky TOC, scrollspy, search filter, code-copy buttons, and design-system-driven brand tokens' over 'specs, RFCs, reports, plans, explainers' — giving comprehensive coverage rather than a vague verb.

5 / 5

Completeness

Explicitly answers both what ('Converts long-form markdown ... into a single-file ... HTML document') and when ('Triggers when ... DOCUMENT', 'Use after orchestrator routing or after design-system onboarding is confirmed') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('specs, RFCs, reports, plans, explainers', 'markdown', 'HTML', '/cs:md-document'), but triggers lean on orchestrator routing language and omit common synonyms like '.md' files, so a couple of natural phrases are missing.

4 / 5

Distinctiveness Conflict Risk

The DOCUMENT-routing niche and explicit orchestrator trigger distinguish it from sibling converters, though it could overlap with general markdown-to-HTML skills absent the routing context — mostly distinct with minor overlap risk.

4 / 5

Total

18

/

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.