html-ppt-xhs-pastel-card

A personal manifesto: a year of saying yes — the premise, the scenes, the turn, and the meaning that lands. Built as a decision-grade story deck for community, talk audience.

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 ./design-templates/html-ppt-xhs-pastel-card/SKILL.md

Quality

Content

65%

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 tight, highly actionable entry-point card with exact paths, tag rewrites, and a well-flagged 404 gotcha, but it repeats asset paths and omits any build-verification step. Its references point to a sibling master skill whose files are not present in this skill's own bundle.

Suggestions

Add an explicit verification step after authoring, e.g. 'Open index.html and confirm slides advance with the arrow keys and the theme cycles with T before delivering.'

De-duplicate the four asset paths in step 3 — state them once in a shared list, then have Recipes A and B reference that list instead of repeating each path.

Clarify or relativize the `../html-ppt/...` and `design-templates/...` references so they resolve within this skill's actual bundle, or note explicitly that the card must be installed inside the html-ppt package for those links to work.

Dimension	Reasoning	Score
Conciseness	The body is focused and avoids explaining concepts Claude already knows, but step 3 repeats the same four asset paths across the warning, Recipe A, and Recipe B, and the recipe prose ('Pick one of these two recipes per project:', 'Either way, do not ship...') could be tightened. Mostly efficient with some removable repetition.	2 / 3
Actionability	Guidance is concrete and copy-paste-oriented: exact template folder and files to copy, the body class to keep (`.tpl-xhs-pastel-card`), two explicit recipes with exact `<link>`/`<script>` rewrites from `../../../assets/...` to project-local paths, the theme mechanism (`<link id="theme-link">`), and the notes class (`<aside class="notes">`).	3 / 3
Workflow Clarity	The six steps are clearly sequenced and unambiguous, and the critical 404 failure mode is prominently explained with two fix recipes. However there is no verification checkpoint (e.g., 'open index.html and confirm slides advance / navigation works'), so explicit validation is missing per the anchor-3 requirement.	2 / 3
Progressive Disclosure	The card is cleanly sectioned and intentionally delegates detail to the master skill via one-level markdown links. But the referenced paths (`../html-ppt/SKILL.md`, `../html-ppt/references/full-decks.md`, `design-templates/html-ppt/...`) do not exist in this skill's bundle (no references/scripts/assets folders), so the signaled references do not resolve against the actual bundle structure.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys a clear subject and deliverable type but is written passively with no explicit action verbs and no 'Use when' trigger guidance, leaving both capability specificity and trigger completeness at the midpoint. It is a recognizable niche yet does not distinguish itself sharply from related deck skills.

Suggestions

Lead with an active verb and concrete actions, e.g. 'Builds a personal-manifesto talk deck: drafts the premise, scenes, turn, and landing meaning, then assembles it in the xhs-pastel-card visual system.'

Add an explicit 'Use when...' clause naming when to pick this card over sibling html-ppt templates (e.g., 'Use when the user wants a personal-manifesto or narrative-talk deck in the pastel-card visual style').

Surface natural trigger variations users actually say — 'slides', 'presentation', 'manifesto talk', 'speech deck' — alongside 'story deck'.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and deliverable ('story deck', 'personal manifesto', 'decision-grade') but uses the passive 'Built as a decision-grade story deck' rather than explicit action verbs, and 'the premise, the scenes, the turn, and the meaning that lands' describes deck content rather than capabilities. It is more concrete than 'Helps with documents' but does not list multiple specific actions like the anchor-3 example.	2 / 3
Completeness	The 'what' is implied (produce a personal-manifesto story deck) but there is no 'Use when...' clause or equivalent trigger guidance, so 'when' is entirely missing. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Contains some natural terms a user might say ('personal manifesto', 'story deck', 'talk audience') but misses common variations such as 'slides', 'presentation', or 'speech'. Coverage is partial rather than the broad set of natural terms in the anchor-3 example.	2 / 3
Distinctiveness Conflict Risk	The personal-manifesto / narrative-talk framing is a recognizable niche, but 'story deck' and 'deck' overlap with sibling html-ppt template skills, and the description lacks distinctive explicit trigger phrasing that would prevent mis-selection among them.	2 / 3
	Total	8 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 5 missing, 2 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-xhs-pastel-card/SKILL.md
Commit: f2760fd

Reviewed: 2 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.