html-ppt-xhs-white-editorial

A staff-engineer promotion packet — scope, the proof moments, the artifacts, and the impact that clears the bar. Built as a decision-grade career deck for manager, calibration committee.

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-white-editorial/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 lean, highly actionable entry-point card with concrete paths and exact rewrites for a real footgun, and it is well sequenced. Its main gaps are a missing verification checkpoint and references to a master skill/template tree that are not bundled here and therefore do not resolve.

Suggestions

Add an explicit verification step to the workflow (e.g., after copying and rewriting assets, open index.html and confirm slides navigate and base.css/animations.css/runtime.js load without 404s).

Ensure the referenced master skill and template/asset files (../html-ppt/SKILL.md, design-templates/html-ppt/...) are either bundled or that the card clearly states they live in a shared sibling tree, so the one-level-deep references actually resolve.

Tighten the Recipe A/B section by listing the four shared asset files once and describing only the differing final step (copy+rewrite vs inline) per recipe.

Dimension	Reasoning	Score
Conciseness	The body is operational and assumes Claude's competence (no explaining of HTML/CSS basics), and the 404/relative-URL warning earns its tokens, but the dual Recipe A/B section repeats the same four asset file paths and could be tightened.	2 / 3
Actionability	It gives concrete, copy-paste-ready guidance: exact source paths to copy, the exact `.tpl-xhs-white-editorial` body class to keep, and exact before/after `<link>`/`<script>` rewrites (`../../../assets/...` to project-local paths) for both Recipe A and Recipe B.	3 / 3
Workflow Clarity	The six authoring steps are clearly numbered and sequenced, but there is no validation/checkpoint step (e.g., 'open index.html and confirm slide navigation works before shipping'), so the sequence lacks an explicit verification gate.	2 / 3
Progressive Disclosure	The card is well-structured as a thin overview with clearly signaled, one-level-deep references (to `../html-ppt/SKILL.md`, the template folder, and asset files), but those referenced paths are not present in this skill's own bundle (references/, scripts/, assets/ are absent and the parent/design-templates paths do not resolve), so the navigation cannot actually be followed.	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 reads as a topic statement for an example deck rather than a capability statement for the skill, and it entirely lacks explicit trigger guidance. It is reasonably niche but weak on concrete actions and the 'when to use' dimension.

Suggestions

Rewrite the description to state the skill's actual capability (e.g., 'Generates decision-grade HTML slide decks in the xhs-white-editorial visual system...') rather than describing the subject of one example deck.

Add an explicit 'Use when...' clause naming concrete triggers such as 'year-end self-review deck', 'staff-engineer promotion packet', or 'html slide deck'.

Include the medium/slide keywords (html deck, slides, presentation) so the description covers the terms users would actually say.

Dimension	Reasoning	Score
Specificity	The description names a domain and an output type ("a decision-grade career deck for manager, calibration committee") with elements like "scope, the proof moments, the artifacts, and the impact", but it states few concrete capabilities/actions of the skill itself and reads as a description of a deliverable's topic rather than what the skill does.	2 / 3
Completeness	It gestures at "what" (a career deck about a promotion packet) but provides no "when" — there is no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural career-side terms a user might say ("staff-engineer promotion packet", "career deck", "promotion", "calibration committee") but omits the medium terms users would also say (html deck, slides, presentation), so coverage of natural triggers is incomplete.	2 / 3
Distinctiveness Conflict Risk	The staff-engineer promotion / calibration-committee framing is fairly niche, but as one card in a family of parallel template-deck skills its description could still overlap with sibling career/self-review deck skills, so it is not fully distinct.	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-white-editorial/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.