CtrlK
BlogDocsLog inGet started
Tessl Logo

slides

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

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/slides/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The SKILL.md body is an efficient, well-structured index that routes cleanly to real one-level-deep references. Its main weakness is actionability: the in-body guidance stops at 'load the reference and execute', leaving the concrete doing entirely to the bundle files.

Suggestions

Replace the vague 'Execute with remaining arguments' step with a concrete indication of what execution produces (e.g. an output HTML file path) or a one-line example invocation.

Add a brief inline Quick start snippet (a minimal command or expected output) so the body is actionable without forcing a reference load for the common case.

Clarify how unknown or missing subcommands should be handled in the Routing section to make the workflow fully unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and well-organized — a short overview, a bullet list, two small tables, and a three-step routing section — with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

The routing gives concrete file-loading steps ('Load corresponding references/{subcommand}.md'), but the final 'Execute with remaining arguments' is vague and the actual executable guidance is delegated entirely to the reference files.

2 / 3

Workflow Clarity

The Routing section lays out a clear three-step sequence (parse subcommand, load reference, execute); slide creation is non-destructive, so absent validation checkpoints do not cap the score.

3 / 3

Progressive Disclosure

The body is a concise overview pointing to well-signaled, one-level-deep references in organized tables, and all five referenced files exist on disk, giving easy navigation.

3 / 3

Total

11

/

12

Passed

Description

67%

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 a clear niche, but it omits explicit 'when to use' trigger guidance and relies on a fairly narrow set of natural user terms. Adding a Use-when clause and broader trigger vocabulary would raise the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating slide decks, pitch decks, or data-driven HTML presentations.'

Add common natural terms users say, such as 'slide deck', 'pitch deck', and 'presentation slides', alongside the existing vocabulary.

Lead with the primary action verb set rather than a single 'Create' so multiple concrete actions are visible at a glance.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies' — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly answers 'what' the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

It includes some natural terms a user would say ('presentations', 'Chart.js') but misses common variations like 'slide deck', 'pitch deck', or 'PowerPoint', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The HTML-presentation-with-Chart.js niche is specific and distinct, with triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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