CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-ppt-taste-editorial

16:9 HTML deck in editorial-minimalist taste. Warm cream slides, serif display + grotesque body, hairline rules, monospace meta, generous macro-whitespace, one accent. Distilled from Leonxlnx/taste-skill `minimalist-skill`.

60

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 ./design-templates/html-ppt-taste-editorial/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is an exceptionally dense, actionable style spec with strong validation via the pre-flight checklist, and it wastes no tokens. Its main defects are a missing example.html file referenced as the code anchor and the absence of an explicit ordered build workflow.

Suggestions

Ship the referenced example.html (or remove the 'See example.html in this directory' line) — as written, the skill's only code reference is a dead path.

Add a short ordered build sequence (e.g. scaffold from example.html → apply required archetypes → verify against the pre-flight checklist) to convert the spec into a workflow.

Consider moving the ten slide archetypes to a references file with one minimal HTML snippet each, keeping SKILL.md as the overview.

DimensionReasoningScore

Conciseness

The body is a lean spec — hex codes, clamp() sizes, spacing values, a banned list, ten archetypes, and a pre-flight checklist — with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Guidance is highly concrete with copy-paste-ready values ('#FBFBFA', 'clamp(56px, 6.5vw, 96px)', 'letter-spacing: 0.18em', 'cubic-bezier(0.16, 1, 0.3, 1)') and ten specific slide archetypes. It stops short of 5 because the referenced executable example ('See example.html in this directory') does not exist in the bundle, leaving no complete starter code.

4 / 5

Workflow Clarity

The spec is well-ordered (substrate/type rules → banned → archetypes → motion → pre-flight checklist) and the pre-flight checklist provides explicit validation checkpoints. It is not 5 because there is no explicit build sequence (e.g. start from example.html, apply archetypes, then run pre-flight) tying the pieces into an ordered procedure.

4 / 5

Progressive Disclosure

The body is short and well-sectioned, which would suit a 5 under the simple-skill note, but its single external reference — 'See example.html in this directory' — is broken: no example.html (or references/scripts/assets bundle) exists. A dangling reference with no other navigation structure matches the 'references present but' defective-organization anchor rather than a good-structure one.

3 / 5

Total

16

/

20

Passed

Description

58%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.

The description is concrete and stylistically distinctive, communicating a precise visual identity in few tokens, but it omits any 'Use when...' trigger guidance and lacks common synonyms like 'presentation' or 'PPT'. It describes what the output looks like more than what the skill does.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating HTML presentations, slide decks, or 16:9 decks — investor updates, design reviews, lecture decks.'

Include natural synonyms users would say: 'presentation', 'slides', 'PPT', 'slide deck'.

State the action explicitly (e.g. 'Builds/generates a 16:9 HTML slide deck...') rather than only naming the artifact.

DimensionReasoningScore

Specificity

The description lists several concrete design tokens ('Warm cream slides, serif display + grotesque body, hairline rules, monospace meta, generous macro-whitespace, one accent'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because no explicit action verb (create/generate a deck) states what the skill does.

4 / 5

Completeness

The 'what' is clear (a 16:9 HTML deck in editorial-minimalist taste with named traits), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because 'when' is entirely absent rather than merely implicit-but-present.

3 / 5

Trigger Term Quality

'16:9 HTML deck' and 'slides' are natural terms, but common user phrasings like 'presentation', 'PPT', 'slide deck', or 'PowerPoint-style' are absent — the anchor for 'some relevant keywords but missing common variations or synonyms'. Not 4, since multiple obvious synonyms a user would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct (editorial-minimalist HTML decks with named fonts and palette), but it could still overlap with generic presentation/deck-building skills since terms like 'presentation' are unclaimed — matching 'mostly distinct; minor overlap risk'. Not 5 because the domain (decks/slides) is broad and shared with many presentation skills.

4 / 5

Total

14

/

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

nexu-io/open-design

Path

design-templates/html-ppt-taste-editorial/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.