CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slides

Build a premium PRESENTED slide deck — classic one-slide-at-a-time slides you advance with a clicker — as a Vite + React app. It keeps the Slidev navigation UI (floating glass dock + thumbnail rail + click-builds + presenter) but slides are RESPONSIVE React (reflow to any screen, no fixed canvas) and fully interactive. Use this for a deck you'll PRESENT (talk over, projector, screen-share) when you want web interactivity and responsiveness without Slidev's constraints. The repo IS the running app (Vite + React) — you install it in place, theme the tokens, and AUTHOR an original deck from the user's real topic/brand.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%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-sequenced, highly actionable skill body: numbered steps, hard rules, entry conditions per specialty layout, and a Definition-of-Done checklist with executable verification commands. The main structural weakness is that it is entirely monolithic — the large component catalog would sit better in a one-level-deep reference file — and the centering rule is repeated three times, adding trimmable tokens.

Suggestions

Move the Step 3 component catalog (the ~25 component/atom descriptions) into a references/ file (e.g. references/components.md) and keep a short workhorse list plus the entry-condition rules in SKILL.md, linked with a clearly signaled one-level-deep reference.

State the centering rule once as a hard rule and reference it ('per hard rule 3') from Step 3 and the checklist instead of re-explaining the mechanics in all three places.

Add one more complete executable slide snippet (e.g. a Split with a BrowserFrame mock) so the two most common composition patterns are copy-paste ready, and note the error-recovery loop when 'npm run build' fails (fix, re-run, re-audit).

DimensionReasoningScore

Conciseness

The body is dense and skill-specific throughout — exact paths ('src/deck/ … LOCKED', 'edit :root ONLY'), one-line component descriptions, named theme families, and CSS utilities — with almost no explanation of concepts Claude already knows. It falls short of anchor 5 mainly through repetition: the centering rule is stated three times (hard rule 3, the blockquote in Step 3, and the Definition-of-Done audit), and the specialty-layout entry conditions are listed then re-summarized in the checklist — trimmable without losing clarity. It is above anchor 3 because the padding is minor emphasis rather than unnecessary explanation.

4 / 5

Actionability

Guidance is highly concrete: runnable commands ('npm install && npm run dev'), exact editable surfaces ('src/styles/tokens.css :root', 'Change values, never variable names'), a complete executable <Build at={n}> JSX example, prop-level hints per component ('center', 'full', 'nav', 'notes', 'flip', 'highlight: true'), and CSS utilities ('.cols', '.appmock', '.hide-narrow'). It sits at anchor 4 rather than 5 because most of the 25+ component catalog is one-line prose API hints with only a single full code example — a second complete slide snippet would make the common cases copy-paste covered.

4 / 5

Workflow Clarity

The process is explicitly sequenced (Step 0 ground the input → Step 1 run in place → Step 2 theme → Step 3 author → Step 4 responsive check → Step 5 visuals → Step 6 motion → Step 7 structure) and closes with a Definition-of-Done checklist containing executable validation ('npm install && npm run dev runs with no console errors; npm run build passes', 'step through EVERY slide' for the alignment audit, 'looks right narrow + wide'). This matches anchor 5 — clear sequence, explicit validation steps, and a checklist for a complex process — though error-recovery loops (what to do when the build fails) are only implicit.

5 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/), so everything lives in one ~300-line SKILL.md. Sections are well-organized, but the ~90-line component catalog in Step 3 is API-reference-like content that the rubric expects in a separate one-level-deep reference file, matching anchor 3's 'content that should be separate is inline'. It is above anchor 2 (the file has clear section headers and navigable structure) but below anchor 4, where the bulk of reference material would live in separate files.

3 / 5

Total

16

/

20

Passed

Description

78%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 description that explicitly answers both what (responsive Vite+React presented slide deck with Slidev-style UI) and when (presented decks wanting web interactivity), with good natural trigger terms. The main deductions are the second-person voice ('you'll PRESENT', 'you install'), which the rubric penalizes on specificity, and missing common synonyms like 'presentation'.

Suggestions

Rewrite in third person to satisfy the rubric's voice rule: e.g. 'Builds a premium presented slide deck…' / 'Use when building a deck to present (talk over, projector, screen-share)…' instead of 'you'll PRESENT', 'you install', 'you want'.

Add the natural synonyms users say for this need — 'presentation', 'slide deck', 'PowerPoint-style' — to the trigger phrase list so lexical matching catches requests that never mention Slidev or Vite.

Lead with the concrete capability list before the Slidev comparison so the actions read as an enumeration rather than as framed by contrast with another tool.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Build a premium PRESENTED slide deck… as a Vite + React app', 'keeps the Slidev navigation UI (floating glass dock + thumbnail rail + click-builds + presenter)', 'you install it in place, theme the tokens, and AUTHOR an original deck' — which matches the anchor for several specific actions (4). However, it is written in second person ('a deck you'll PRESENT', 'you install it in place', 'when you want'), and the rubric penalizes non-third-person voice by reducing specificity by 1, giving 3. It is above anchor 3's bare '1-2 concrete actions' but the voice penalty and the Slidev-comparison framing of the action list keep it from scoring higher.

3 / 5

Completeness

Both questions are answered explicitly: what — 'Build a premium PRESENTED slide deck… as a Vite + React app… RESPONSIVE React (reflow to any screen, no fixed canvas) and fully interactive… install it in place, theme the tokens, and AUTHOR an original deck'; when — 'Use this for a deck you'll PRESENT (talk over, projector, screen-share) when you want web interactivity and responsiveness without Slidev's constraints.' The 'Use this for…' clause is explicit with concrete trigger contexts, matching anchor 5 exactly; it is clearly above anchor 4, where the 'when' is present but only loosely specified.

5 / 5

Trigger Term Quality

Natural user-facing terms are present: 'slide deck', 'slides', 'PRESENT', 'projector', 'screen-share', 'deck', and the comparison anchor 'Slidev' — matching anchor 4's 'good keyword coverage; a few natural terms missing'. It falls short of anchor 5 because common synonyms users actually say — 'presentation', 'PowerPoint', 'keynote', '.pptx' — are absent, so a user saying 'make me a presentation' may not lexically match.

4 / 5

Distinctiveness Conflict Risk

The Vite + React presented-deck niche with Slidev-UI chrome is quite distinct, and the 'when' clause explicitly separates it from Slidev and from static decks. It is not anchor 5: a request to 'make slides' or a 'presentation' could also plausibly route to a .pptx-oriented presentation skill, so minor overlap risk with closely related presentation skills remains — anchor 4's 'mostly distinct; minor overlap risk'.

4 / 5

Total

16

/

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

adamsardo/bolt-slides-couch

Path

.bolt/skills/slides/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.