CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise, clearly sequenced skill body with strong validation gates, but it falls short on actionability for the core deliverable (no executable HTML/JS template) and on progressive disclosure because its primary referenced file, STYLE_PRESETS.md, is missing from the bundle.

Suggestions

Provide an executable, copy-paste-ready HTML/CSS/JS skeleton — at minimum the presentation controller class with keyboard/wheel/touch navigation, the Intersection Observer reveal setup, and the reduced-motion guard — instead of only listing what to include.

Either ship STYLE_PRESETS.md in a references/ folder (with the viewport-safe CSS base, preset catalog, density limits, and CSS gotchas the body promises) or inline its essentials so the repeated "read STYLE_PRESETS.md" instructions are not dangling references.

Add an explicit validate→fix→re-run feedback loop in the Validate step (e.g., "if a slide overflows, split it per the viewport-fit rules and re-check") rather than only listing the target sizes.

DimensionReasoningScore

Conciseness

The body is lean and list-driven with no padding explaining HTML, browsers, or libraries; sections like Non-Negotiables, density limits, and Anti-Patterns each earn their tokens. It assumes Claude's competence throughout.

3 / 3

Actionability

Concrete specifics exist (viewport CSS `height: 100vh; 100dvh; overflow: hidden`, `clamp()`, per-OS open commands, python-pptx steps, validation sizes), but the central artifact — the presentation controller class, keyboard/wheel/touch JS, and Intersection Observer reveal setup — is described by listing what to include rather than given as executable, copy-paste-ready code.

2 / 3

Workflow Clarity

A clearly sequenced 7-step workflow (Detect → Discover Content → Discover Style → Build → Enforce Viewport Fit → Validate → Deliver) with explicit checkpoints: viewport fit is a "hard gate," and Validate tests five named viewport sizes plus optional browser-automation verification, closed by a Deliverable Checklist.

3 / 3

Progressive Disclosure

Sections are well-organized and references are clearly signaled one level deep ("read STYLE_PRESETS.md"), but STYLE_PRESETS.md is referenced repeatedly and is not present in the bundle (no references/ directory), so the disclosure path is broken rather than navigable.

2 / 3

Total

10

/

12

Passed

Description

100%

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: concrete actions, explicit Use-when triggers, natural terminology, and a clearly bounded niche. Third-person voice is maintained throughout. Only minor nit is the marketing word "stunning."

DimensionReasoningScore

Specificity

"Create ... animation-rich HTML presentations from scratch or by converting PowerPoint files" and "convert a PPT/PPTX to web, or create slides" list multiple concrete actions; the only soft spot is the buzzword "stunning," but the actions remain specific.

3 / 3

Completeness

Answers both what (create/convert animation-rich HTML presentations) and when via an explicit "Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch" trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasing — "build a presentation," "convert a PPT/PPTX to web," "create slides for a talk/pitch," and "PowerPoint" — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The niche is clear — zero-dependency HTML slide decks and PPT/PPTX-to-web conversion — with distinct triggers unlikely to collide with other skills.

3 / 3

Total

12

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.