frontend-slides

Generate animation-rich HTML presentations with visual style previews. Useful for online keynotes, embedded talks, and interactive briefs.

Quality

57%

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

Quality

Content

57%

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 token-efficient and well-organized as a thin catalogue pointer, but it offers almost no actionable guidance — it redirects to an external repo rather than instructing Claude how to perform the skill. Workflow clarity is adequate for a simple entry but lacks any verification step.

Suggestions

Add a concrete, self-contained example of generating an HTML slide deck (e.g. a minimal command or template snippet) so the skill is actionable without requiring an external fetch.

Include a verification step in the 'How to use' workflow so Claude can confirm the upstream bundle was installed and invoked correctly.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~24-line catalogue entry that does not restate concepts Claude already knows and contains no padded explanation; every section earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	The only executable instruction is 'open https://github.com/...' plus 'ask the agent to invoke this skill'; it describes a pointer to an upstream bundle rather than providing concrete, executable skill guidance, matching the 'describes rather than instructs' anchor.	1 / 3
Workflow Clarity	The steps (inspect upstream README, install the bundle, invoke by name or trigger) are listed as a loose sequence, but there are no validation checkpoints or error-recovery feedback for confirming the install succeeded.	2 / 3
Progressive Disclosure	For a short, single-purpose catalogue entry with no local bundle files, the body is well-organized into clear sections (What it does, Source, How to use) and its only reference is a single external URL, which is appropriate one-level disclosure.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 cleanly states a clear, distinctive purpose but only implies rather than explicitly states when to use it, and its natural trigger terms are weaker in the description text than in the frontmatter triggers. It is solid but capped at the mid level by the missing explicit 'Use when' guidance and limited keyword coverage.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger scenarios (e.g. 'Use when creating HTML slides, web decks, or interactive online presentations').

Surface common natural terms like 'slides', 'deck', and 'ppt' directly in the description so the description text alone covers user vocabulary.

Dimension	Reasoning	Score
Specificity	The phrase 'Generate animation-rich HTML presentations with visual style previews' names the domain and a composite action, but it is a single bundled action rather than a list of multiple specific concrete actions, so it sits at anchor 2 rather than 3.	2 / 3
Completeness	It states what the skill does, but 'Useful for online keynotes, embedded talks, and interactive briefs' only implies when to use it; there is no explicit 'Use when...' clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	The description includes 'HTML presentations', 'online keynotes', 'embedded talks', and 'interactive briefs', which are relevant keywords, but common natural variations users would say ('slides', 'deck', 'ppt') appear only in the frontmatter triggers, not the description text itself.	2 / 3
Distinctiveness Conflict Risk	The niche (animation-rich HTML presentation generation) is clear and distinct, and the trigger domain is specific enough that it is unlikely to be invoked for an unrelated skill.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/frontend-slides/SKILL.md
Commit: f2760fd

Reviewed: 3 days 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.