CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

Quality

87%

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

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, largely lean skill body with strong workflow structure and genuinely executable CSS/commands. Its main defects are the missing STYLE_PRESETS.md companion file (referenced three times but not shipped, breaking both the disclosure chain and the delegated CSS base) and some duplication between the inline density table, the checklist, and the presets file.

Suggestions

Ship STYLE_PRESETS.md in the bundle (e.g., references/STYLE_PRESETS.md) — it is referenced three times for the viewport-safe CSS base, density limits, preset catalog, and mandatory CSS block, but the file does not exist, so 'Before generating, read STYLE_PRESETS.md' cannot be followed.

De-duplicate: keep the density limits in exactly one place (either the inline table or STYLE_PRESETS.md) and trim the deliverable checklist and the 'Inspired by...' attribution line, which restate or add nothing.

Include a minimal inline skeleton of the presentation controller (keyboard/wheel/touch + Intersection Observer reveal) so the core JS requirement is executable even before consulting the presets file.

DimensionReasoningScore

Conciseness

The body is directive throughout — bullet lists, a density table, exact CSS and commands — and assumes competence (no explanation of clamp(), Intersection Observer, or what a browser automation tool is). Not 5: there is redundant padding — the density limits table duplicates limits also delegated to STYLE_PRESETS.md, the deliverable checklist restates earlier rules, and the 'Inspired by the visual exploration approach showcased in work by zarazhangrui' attribution line adds no actionable value. Not 3: over-explanation is minor, not pervasive.

4 / 5

Actionability

Concrete, executable guidance is present: exact CSS ('height: 100vh; height: 100dvh; overflow: hidden;'), exact platform openers ('open file.html', 'xdg-open file.html', 'start "" file.html'), specific validation sizes (1920x1080 through 667x375), and a quantified density table. Not 5: key executable material — the viewport-safe CSS base, preset catalog, and mandatory CSS block — is delegated to STYLE_PRESETS.md, which is not present in the bundle, and the JS presentation controller is only named, not exemplified; not 3: the written guidance itself is concrete with commands and code-level specifics.

4 / 5

Workflow Clarity

A clear seven-step sequence (Detect Mode → Discover Content → Discover Style → Build → Enforce Viewport Fit → Validate → Deliver) with an explicit validation step at five concrete sizes, a hard gate ('Treat this as a hard gate', 'never allow scrollbars inside a slide'), an error-recovery loop ('when content does not fit, split into multiple slides'), and a final deliverable checklist. This is not a destructive or batch operation, so the workflow-clarity cap does not apply. Not 4: validation is explicit and multi-point with feedback loops and a checklist, matching the top anchor.

5 / 5

Progressive Disclosure

The body correctly delegates bulky detail to a single, clearly-signaled, one-level-deep reference ('Before generating, read STYLE_PRESETS.md for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas') — a good pattern. However, scoring against the actual bundle structure: no references/, scripts/, or assets/ directories exist and STYLE_PRESETS.md is absent, so every reference to it is dangling and the disclosure chain is broken. Not 4: a missing referenced file is more than a minor organization gap; not 2: the SKILL.md itself is well structured and references are prominent, not buried or inlined monolithically.

3 / 5

Total

16

/

20

Passed

Description

91%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 pairs concrete capabilities with an explicit 'Use when...' trigger clause covering creation, conversion, and slide-building phrasing. Minor improvements would drop the 'stunning' puffery and mention the enhancement mode that the body supports.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Create ... animation-rich HTML presentations from scratch or by converting PowerPoint files' and 'discover their aesthetic through visual exploration' — with only minor gaps (e.g., enhancing existing decks is covered in the body but not the description). Not 5: 'stunning' is buzzword padding and coverage of the conversion/style-discovery modes stops slightly short of comprehensive; not 3: multiple specific concrete actions are named, exceeding the 1-2 action anchor.

4 / 5

Completeness

Explicitly answers both: what — 'Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files' — and when — 'Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch'. Not 4: the 'when' clause is explicit with concrete trigger phrases, not merely present-and-improvable.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensive with both synonyms and file extensions: 'build a presentation', 'convert a PPT/PPTX to web', 'create slides for a talk/pitch', 'PowerPoint files'. Not 4: coverage already spans synonyms (presentation, slides, talk, pitch, PowerPoint) and extensions (PPT/PPTX), matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

The HTML/web presentation niche is mostly distinct ('animation-rich HTML presentations', 'convert a PPT/PPTX to web'), with the visual-exploration framing adding identity. Not 5: PPT/PPTX and presentation triggers would also fire a general presentation-editing skill, creating minor overlap; not 3: the web/HTML focus keeps it well above the somewhat-specific anchor.

4 / 5

Total

18

/

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

ysyecust/everything-claude-code

Path

.agents/skills/frontend-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.