Name: md-slides
Rating: 68.8 (1 reviews)
Author: alirezarezvani

md-slides

Converts a markdown deck (slides separated by `---` HR boundaries or by `# ` H1 headings, with optional `` 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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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

Quality

Content

76%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, highly actionable skill body with copy-paste-ready pipeline commands and clear hard rules. The main gap is workflow clarity: the batch conversion pipeline lacks explicit validation checkpoints or error-recovery feedback loops between steps.

Suggestions

Add validation checkpoints between pipeline steps (e.g. after slide_splitter, verify /tmp/slides.json has the expected slide count and well-formed titles before proceeding; abort with a clear message if not).

Include a validate→fix→retry feedback loop for the batch conversion (e.g. on a renderer error, point back to the offending slide index and re-run only the failed step).

Move the inlined canon citations from the forcing-question section into references/ to tighten the body and make the references pointer load-bearing.

Dimension	Reasoning	Score
Conciseness	The core (pipeline, hard rules, what-ships list) is efficient, but a few sections over-explain concepts Claude already knows (e.g. "Keynote / PowerPoint — those are graphic-design tools") and the inlined canon citations add tokens that could be trimmed; not a 5 because of these minor padding instances.	4 / 5
Actionability	Provides three fully executable, copy-paste-ready `python3 …` pipeline commands with concrete arguments and expected intermediate/output files, covering the common end-to-end case; the feature list and exit codes add actionable specificity.	5 / 5
Workflow Clarity	The three-step pipeline is clearly numbered and sequenced, but there are no explicit validation checkpoints or validate→fix→retry feedback loops between steps; because converting a whole deck is a batch operation, the batch-operations guideline caps this at 3 rather than 4-5.	3 / 5
Progressive Disclosure	Well-organized sections (When to invoke, Pipeline, What ships, Hard rules, References) with a clearly signaled, one-level-deep `references/` pointer; not a 5 because no bundle files are present to verify the referenced paths, and some citations are inlined in the body rather than moved to references.	4 / 5
	Total	16 / 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, specific description that clearly states both what the skill does and when to use it, with concrete trigger phrases and explicit refusal boundaries. The only weak spot is trigger-term quality, where some natural user phrasings are diluted by internal jargon.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (converts markdown deck to single-file HTML, keyboard navigation, presenter mode, URL-hash deep linking, print-to-PDF) plus explicit refusal conditions, matching the comprehensive-coverage anchor; not a 4 because coverage is broad rather than having only minor gaps.	5 / 5
Completeness	Explicitly answers both "what" (converts a markdown deck into a single-file HTML presentation with listed features) 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	Good natural-term coverage with synonyms ("markdown deck", "slides", "HTML presentation", "presenter notes", "PDF export"), but a few natural terms/file extensions are missing and several phrases are technical jargon (orchestrator, config_loader.py, design-system tokens) rather than user-spoken keywords.	4 / 5
Distinctiveness Conflict Risk	Clear niche (markdown deck → single-file HTML presentation) with distinct triggers (SLIDES routing, /cs:md-slides) and explicit refusal boundaries that separate it from md-document/md-review; minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/md-slides/SKILL.md
Commit: 19392f7

Reviewed: ~10 hours ago

Table of Contents

Discovery Implementation Validation

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.