CtrlK
BlogDocsLog inGet started
Tessl Logo

slides

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

48

Quality

53%

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 ./.claude/skills/slides/SKILL.md

The canonical home for this skill is slides in nextlevelbuilder/ui-ux-pro-max-skill

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill body is a clean, token-efficient router with genuinely well-structured one-level-deep references, but it never descends into concrete execution guidance — and its main subcommand target is an empty circular stub, so following the workflow yields no actual instructions for creating slides.

Suggestions

Replace the circular stub in references/create.md with the actual creation steps (e.g. token/design-token loading, template selection, Chart.js integration, output location).

Add a minimal quick-start example in the body (e.g. one concrete invocation for `slides create "seed pitch" 10`) so the core path is executable without chasing references.

Tighten or trim the "Script Paths" section, and remove or correct references to a scripts/ folder that is not part of this bundle.

DimensionReasoningScore

Conciseness

The ~45-line body is efficient with no explanations of concepts Claude already knows; the only trimming candidate is the dense "Script Paths" paragraph, which over-explains a path convention and references a scripts/ folder that does not exist in this bundle.

4 / 5

Actionability

The body is pure routing with no code, commands, or templates, and "Execute with remaining arguments" defers all real guidance to references/create.md — which is itself a circular stub ("Invoke `slides` skill") containing no executable steps, leaving only high-level hints.

2 / 5

Workflow Clarity

The 3-step routing sequence (parse subcommand, load reference, execute) is coherent and ordered, but step 3 is a large undefined gap and there are no checkpoints for what executing actually involves, matching the 'steps listed but gaps' anchor.

3 / 5

Progressive Disclosure

The body provides a clear overview with two well-signaled tables pointing to 5 real reference files that are one level deep and substantive (layout patterns, templates, formulas, strategies); the hollow create.md stub behind the primary subcommand is the notable organization gap keeping this below 5.

4 / 5

Total

13

/

20

Passed

Description

53%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 communicates a clear, fairly distinct capability but reads as a feature list rather than a trigger-oriented description. Its biggest gaps are the complete absence of a "when to use" clause and of natural trigger phrases like "deck" or "slides".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for slides, a deck, a pitch presentation, or data-driven HTML slides."

Include natural user phrasings ("slides", "deck", "pitch deck", "presentation") as trigger terms alongside the technical vocabulary.

Replace the buzzword "strategic" with another concrete action (e.g. "build responsive slide decks with animated transitions") to strengthen specificity.

DimensionReasoningScore

Specificity

"Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies" names the domain and one concrete action plus its component features, but offers only a single verb of action rather than several specific actions, matching the 'domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

The "what" is clear (create HTML presentations with the listed capabilities) but there is no "Use when..." clause or any trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes some relevant natural keywords ("presentations", "slide", "Chart.js") but misses common variations users would actually say such as "slides", "deck", "pitch deck", or "PowerPoint", matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"HTML presentations with Chart.js" carves a mostly distinct niche with specific technology triggers, though "strategic" is mild buzzword and there is minor overlap risk with generic presentation or data-visualization skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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