html-ppt-product-launch

Open Design Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.

Quality

68%

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-product-launch/SKILL.md

Quality

Content

87%Weight 40%Scale 1-3

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 authoring guide with concrete file paths and two copy-paste recipes, appropriately deferring detail to the upstream master skill. Its main gap is the absence of an explicit validation step to confirm the copied deck's runtime and navigation actually work before shipping.

Suggestions

Add an explicit validation checkpoint after copying/rewriting assets, e.g. 'Open index.html and confirm slides advance and base.css/animations.css/runtime.js load without 404s before replacing demo content.'

Trim the explanatory aside about why the ../../../assets/... URLs break to a single clause, since the recipes already make the fix self-evident.

State the verification outcome expected (slides navigate, theme cycles with `T`) so the checkpoint is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it provides exact paths and two concrete recipes rather than explaining what HTML/CSS or decks are, and nearly every token earns its place.	3 / 3
Actionability	Guidance is concrete and executable — exact files to copy (e.g. design-templates/html-ppt/assets/base.css), precise <link>/<script> path rewrites for Recipe A and B, the `T` theme cycle, and the `<aside class="notes">` rule are all copy-paste ready.	3 / 3
Workflow Clarity	The numbered authoring sequence (read master skill, copy template, bring runtime, pick theme, replace content, add notes) is clearly ordered, but there is no explicit validation/verification checkpoint despite the skill itself warning that 'slide navigation is dead' if the asset URLs 404.	2 / 3
Progressive Disclosure	The card is a focused entry point with well-organized sections that defer detail to the master skill via one-level-deep, clearly signaled references (../html-ppt/SKILL.md, ../html-ppt/references/full-decks.md); no bundle files are present to organize.	3 / 3
	Total	11 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 identifies a clear B2B sales-deck deliverable and audience but is framed as the artifact rather than the actions Claude takes, and it omits any explicit 'Use when' trigger guidance. It is specific enough to avoid being generic yet would benefit from concrete capability verbs and explicit trigger terms.

Suggestions

Rewrite the description around concrete actions (e.g., 'Builds, writes, and critiques a decision-grade B2B sales deck...') instead of describing the artifact.

Add an explicit trigger clause such as 'Use when the user wants a B2B SaaS sales proposal, team-rollout pitch, or renewal/decision deck.'

Include natural user phrasings ('sales proposal', 'pitch deck', 'rollout deck') to broaden trigger-term coverage and reduce overlap with sibling deck skills.

Dimension	Reasoning	Score
Specificity	Names a concrete deliverable and audience ('a launch-and-adoption proposal', 'decision-grade B2B sales deck for design team lead, IT') but describes the artifact rather than listing multiple concrete actions Claude performs, so it is not comprehensive enough for a 3.	2 / 3
Completeness	It states what the skill produces (a launch-and-adoption sales deck) but provides no explicit 'Use when...' clause or equivalent trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Contains some relevant keywords ('B2B sales deck', 'mid-market', 'design team') but the description itself lacks broad coverage of natural user phrasings; 'decision-grade B2B sales deck' leans toward jargon rather than common variations.	2 / 3
Distinctiveness Conflict Risk	The 'Open Design Teams' / 'product-launch' / B2B sales deck niche is fairly specific, but a sales-deck proposal could still overlap with sibling html-ppt skills or other sales skills, so it is not maximally 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-product-launch/SKILL.md
Commit: f2760fd

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