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

81%

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

The canonical home for this skill is frontend-slides in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

71%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, mostly lean instruction-only skill with a clear seven-step workflow, explicit validation sizes, and concrete CSS/density rules. Its main weakness is bundle integrity: STYLE_PRESETS.md is referenced three times as the source of the mandatory CSS base and preset catalog but is missing entirely, and the validation step lacks an explicit fix-and-recheck loop.

Suggestions

Add the referenced STYLE_PRESETS.md to the bundle (or inline the mandatory viewport-safe CSS block and preset catalog into SKILL.md) — the body cites it three times for content that exists nowhere.

Close the validation feedback loop in step 6: after checking the five sizes, add an explicit "if any slide overflows or navigation fails, fix and re-check that size" iteration.

Consolidate the viewport-fit rules currently repeated in Non-Negotiables, step 5, and the Deliverable Checklist into step 5, and drop the zarazhangrui inspiration credit line to trim tokens.

DimensionReasoningScore

Conciseness

The body is directive-dense with no explanations of concepts Claude already knows, but has minor trimmable padding: the "Inspired by the visual exploration approach showcased in work by zarazhangrui" credit line, and viewport-fit rules repeated across Non-Negotiables, step 5, and the Deliverable Checklist — matching anchor 4. Not 5 because of that repetition; not 3 since nothing is noticeably verbose.

4 / 5

Actionability

Concrete specifics abound — "height: 100vh; height: 100dvh; overflow: hidden;", exact validation sizes (1920x1080 through 667x375), the density-limits table, per-OS opener commands, and the python-pptx extraction path — matching anchor 4. Not 5 because the mandatory CSS base and preset catalog are deferred to STYLE_PRESETS.md, which does not exist in the bundle, leaving a key executable detail missing; not 3 because most guidance is concrete and executable as written.

4 / 5

Workflow Clarity

Seven clearly sequenced steps (Detect Mode through Deliver) with a hard gate ("Treat this as a hard gate"), explicit validation at five sizes, and a final Deliverable Checklist — matching anchor 4. Not 5 because there is no explicit fix-and-re-validate loop after the Validate step (only "when content does not fit, split into multiple slides" during build); not 3 because checkpoints are explicit, not implicit.

4 / 5

Progressive Disclosure

The body is cleanly sectioned and the single external reference is well signaled and one level deep ("Before generating, read STYLE_PRESETS.md for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas"), but scoring against the actual bundle reveals STYLE_PRESETS.md does not exist — no references/, scripts/, or assets/ directories at all — so the referenced detail content is unreachable. This lands at anchor 3: the structure is sound but the disclosure fails to deliver, which is more than the "minor organization gaps" of anchor 4; not 2 because the in-body organization is strong and the one reference is clearly signaled, not buried or nested.

3 / 5

Total

15

/

20

Passed

Description

83%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 with an explicit 'Use when' clause, concrete trigger phrases, and file extensions; it clearly communicates both what the skill does and when to invoke it. Minor improvements possible: replace "stunning" with a concrete quality cue, add "deck"/"slide deck" as trigger synonyms, and mention the enhancement mode to round out coverage.

DimensionReasoningScore

Specificity

"Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files" and "convert a PPT/PPTX to web" name several concrete actions with minor gaps (the enhance-existing-decks mode from the body is absent, and "stunning" is subjective fluff) — matching anchor 4. Not 3 because more than 1-2 actions are covered; not 5 because coverage is not comprehensive.

4 / 5

Completeness

Explicitly answers both: what — "Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files"; when — "Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch" with concrete trigger phrases, exactly matching the anchor 5 pattern. Not 4 because the when-clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: "presentation", "PowerPoint", "PPT/PPTX" (including extensions), "slides", "talk/pitch" — but the very common "deck" / "slide deck" phrasing is missing, matching anchor 4 ("a few natural terms missing"). Not 5 due to that gap; clearly above 3 since multiple synonyms and extensions are present.

4 / 5

Distinctiveness Conflict Risk

The HTML/web-presentation niche ("animation-rich HTML presentations", "convert a PPT/PPTX to web") is mostly distinct, but "presentation" and "PPT/PPTX" triggers overlap with native PowerPoint-file creation/editing skills — anchor 4 ("minor overlap risk with closely related skills"). Not 5 because of that overlap; well above 3 since the web/HTML framing differentiates it.

4 / 5

Total

17

/

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.

Validation — 15 / 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

valeriibeck-star/claude-skills

Path

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.