CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-slides

Create animation-rich browser-based HTML presentations from scratch, enhance existing HTML decks, or convert PowerPoint files into web presentations. Use only when the requested deliverable is HTML or a browser presentation; do not use when the user needs an editable native .pptx file.

63

Quality

75%

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 ./skills/frontend-slides/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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, largely actionable skill with clear phasing and validation, undermined by missing bundle files that the body instructs Claude to read and include. Tightening the verbose onboarding/coaching prose would further improve token efficiency.

Suggestions

Add the missing referenced files (STYLE_PRESETS.md, viewport-base.css, html-template.md, animation-patterns.md) to the bundle, or inline their essential contents — the body currently instructs Claude to read and include 'the FULL contents of viewport-base.css' which does not exist.

Add an explicit post-generation verification step in Phase 3 (e.g. open the deck and confirm every .slide fits 100vh with no scroll) to close the workflow validation gap.

Trim the Vercel signup walkthrough and repeated design-coaching paragraphs to reduce padding while keeping the actionable rules.

DimensionReasoningScore

Conciseness

Mostly efficient with dense actionable specifics (density tables, clamp rules, exact commands), but the Vercel onboarding walkthrough and repeated design-coaching prose ('You tend to converge toward generic...') add padding that could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready commands and exact CSS (e.g. 'height: 100vh; height: 100dvh; overflow: hidden;', 'bash scripts/deploy.sh <path-to-presentation>'), but the template/animation files that Phase 3 generation depends on are referenced rather than present, leaving a gap in executable guidance.

4 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced with validation in Mode C ('After ANY modification, verify: .slide has overflow: hidden...') and error-recovery loops for Playwright, but Phase 3 generation lacks an explicit post-generation viewport-fit verification checkpoint.

4 / 5

Progressive Disclosure

The 'Supporting Files' table with File/Purpose/When-to-Read columns is well signaled, but 4 of the 7 referenced files (STYLE_PRESETS.md, viewport-base.css, html-template.md, animation-patterns.md) are absent from the bundle, so the one-level-deep references do not resolve — navigation is broken for the core generation content.

3 / 5

Total

14

/

20

Passed

Description

87%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 clearly states capabilities and provides explicit positive and negative trigger guidance. It is concise, distinct, and answers both 'what' and 'when' with concrete phrases.

DimensionReasoningScore

Specificity

Lists three concrete actions — 'Create animation-rich browser-based HTML presentations from scratch', 'enhance existing HTML decks', 'convert PowerPoint files into web presentations' — but omits the sharing/export capabilities the body covers, a minor coverage gap.

4 / 5

Completeness

Explicitly answers both what (create/enhance/convert HTML presentations) and when ('Use only when the requested deliverable is HTML or a browser presentation'), plus a negative trigger ruling out editable .pptx — matching the strong anchor.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('HTML presentations', 'PowerPoint files', 'browser presentation', 'decks', '.pptx file'), but lacks common synonyms like 'slides' or 'slide deck' for full coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (browser-based HTML presentations) and the explicit 'do not use when the user needs an editable native .pptx file' disambiguates it from pptx-editing skills, minimizing conflict risk.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 9 missing

Warning

Total

15

/

16

Passed

Repository
OpenBMB/PilotDeck
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.