CtrlK
BlogDocsLog inGet started
Tessl Logo

md-slides

Converts a markdown deck (slides separated by `---` HR boundaries or by `# ` H1 headings, with optional `<!-- notes: ... -->` presenter notes blocks) into a single-file HTML presentation with arrow-key / space / PgDn / PgUp / Home / End / P / Esc keyboard navigation, presenter mode (split view with current slide + speaker notes + clock + next-slide preview), URL-hash deep linking, and `@media print` page-per-slide for PDF export. Triggers when the markdown-html-orchestrator classifies an input as SLIDES, or when invoked directly via /cs:md-slides. Reuses md-document's markdown parser for slide-body rendering and reads design-system tokens via config_loader.py. Refuses if input has no clear slide boundaries, produces a 1-slide deck, or `--strict-notes` is on with < 50% notes coverage. Use after orchestrator routing.

72

Quality

89%

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

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 well-structured, actionable skill body with an executable pipeline and clear progressive disclosure into bundled scripts, references, and assets. Minor room to tighten rhetorical asides and add an explicit post-render verification step.

Suggestions

Trim rhetorical asides and the forcing-question 'Canon:' attributions to recover token budget while keeping the recommended actions.

Add an explicit post-render verification checkpoint (e.g. open deck.html, confirm slide count and keyboard nav) to the Pipeline section.

Confirm the three referenced reference files (presentation_ux, keyboard_nav_patterns, single_file_deck_conventions) match the citations listed under References for navigation consistency.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, but the forcing-question library's 'Canon:' attributions and a few rhetorical asides ('That's a poster, not a deck') add tokens that could be trimmed.

4 / 5

Actionability

Provides a fully executable three-stage pipeline with concrete 'python3 ... --input/--output' commands and full script paths, copy-paste ready and covering the common case.

5 / 5

Workflow Clarity

Clear numbered three-step pipeline sequence with exit-code refusal gates acting as checkpoints, but lacks an explicit output-verification step after rendering.

4 / 5

Progressive Disclosure

Overview body appropriately points to one-level-deep references/ (three clearly-named files, signaled at the end) and ships dedicated scripts/ and assets/, with content well split and easy to navigate.

5 / 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, concrete description that clearly states what the skill does and when to trigger it, with comprehensive capability listing and minimal conflict risk. The only gap is trigger-term breadth, which leans slightly on orchestrator routing terminology over natural user phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Converts a markdown deck ... into a single-file HTML presentation' with keyboard navigation, presenter mode, URL-hash deep linking, and '@media print page-per-slide for PDF export' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (converts markdown deck to single-file HTML) and when ('Triggers when the markdown-html-orchestrator classifies an input as SLIDES, or when invoked directly via /cs:md-slides', 'Use after orchestrator routing') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural keywords ('slides', 'presentation', 'deck', 'presenter notes', '/cs:md-slides') but leans on routing/orchestrator jargon and omits some common user synonyms; good but not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (markdown deck → HTML presentation) with distinct triggers and explicit refuse-and-route conditions separating it from md-document and md-review, minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation15 / 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
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.