slides

Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cli/assets/skills/slides/SKILL.md

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.

The body is a well-structured, concise overview that routes cleanly to real one-level-deep reference files. Its weakness is actionability: the body and the `create` reference defer actual executable slide-creation guidance, leaving the reader with routing rather than concrete steps.

Suggestions

Add a minimal concrete example to the body (e.g., a one-line Chart.js scaffold or the command to open the generated HTML) so the overview is actionable before opening references.

Flesh out `references/create.md`, which currently only restates the skill's purpose — include the actual creation steps or point to the file that holds them.

Specify what 'Execute with remaining arguments' means in Routing by naming the concrete action each subcommand performs, rather than leaving execution implicit.

Dimension	Reasoning	Score
Conciseness	The body is lean — a short intro, a 'When to Use' bullet list, two compact tables, and a three-step routing list — with no padding explaining concepts Claude already knows; the only mildly long section is the 'Script Paths' paragraph, which is non-obvious path-resolution semantics that earns its tokens, fitting the 'efficient; minor instances that could be trimmed' anchor.	4 / 5
Actionability	The Routing steps are concrete (parse subcommand, load references/{subcommand}.md, execute) but 'Execute with remaining arguments' is vague and the body itself contains no executable code or commands — the real guidance is deferred to references, and `references/create.md` is itself only a thin restatement, matching the 'some concrete guidance but incomplete; missing key details' anchor.	3 / 5
Workflow Clarity	The Routing section gives a clear, ordered three-step sequence and the operation (slide creation) is non-destructive, so the missing-validation cap does not apply; it stops at 4 rather than 5 because there are no explicit validation or verification checkpoints and the final 'execute' step is underspecified.	4 / 5
Progressive Disclosure	The body is a clean overview that points to one-level-deep, well-signaled references via two tables, and every referenced file (layout-patterns.md, html-template.md, copywriting-formulas.md, slide-strategies.md, create.md) exists in references/, matching the 'clear overview with well-signaled one-level-deep references; easy navigation' anchor.	5 / 5
	Total	16 / 20 Passed

Description

66%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 specific and well-scoped to HTML presentations with named capabilities, but it lacks any explicit 'Use when...' trigger guidance, which caps its completeness. Trigger-term coverage is solid yet misses common synonyms like 'slides' or 'pitch deck'.

Suggestions

Add an explicit 'Use when...' clause naming trigger situations (e.g., pitch decks, marketing decks, data-driven slide requests, or when the user mentions HTML slides).

Include natural synonyms users actually say — 'slides', 'slide deck', 'pitch deck', 'decks' — alongside 'presentations' to improve trigger discoverability.

Lead with more than one concrete verb (e.g., 'Design', 'Generate', 'Visualize') so the action list reads as multiple distinct capabilities rather than one 'Create' wrapping a feature list.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Create strategic HTML presentations') and lists several specific concrete capabilities — 'Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies' — which matches the 'lists several specific actions; minor gaps' anchor; it stops short of 5 because the only verb is 'Create' wrapping a feature list rather than multiple distinct actions.	4 / 5
Completeness	It gives a clear 'what' (create strategic HTML presentations with listed features) but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3 ('clear what but when missing or weakly implied').	3 / 5
Trigger Term Quality	It surfaces good natural keywords ('HTML presentations', 'Chart.js', 'slide strategies', 'design tokens') a user might say, but misses common variations like 'slides', 'slide deck', 'pitch deck', or 'decks', so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct — HTML presentations specifically built with Chart.js and design tokens — so overlap risk is limited to closely related HTML/presentation skills, matching the 'mostly distinct; minor overlap risk' anchor; it is not a 5 because 'presentations' alone still overlaps generic deck-making skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: cli/assets/skills/slides/SKILL.md
Commit: 09170ee

Reviewed: 2 hours ago

Table of Contents

Discovery Implementation Validation

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.