html-ppt-pitch-deck

Open Design's demo-day pitch: hook, traction, moat, and the raise — built to make a partner sit up by page three. Built as a decision-grade fundraising pitch deck for accelerator partners, angels.

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-pitch-deck/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 an efficient, highly actionable entry-point card that defers shared rules to the master skill and spells out a real asset-path gotcha with concrete recipes. Its main gap is the absence of an explicit verification step for the fragile URL-rewrite operation it itself flags.

Suggestions

Add a final verification step to the authoring workflow (e.g. open index.html and confirm the deck activates and keyboard navigation works) given the warned 404 failure mode.

Briefly note how to confirm the copied theme link resolves, since theme swapping depends on the same project-local asset layout.

Dimension	Reasoning	Score
Conciseness	The body is lean, points outward to the master skill for shared rules instead of duplicating them, and avoids explaining concepts Claude already knows; the detailed asset-path recipe earns its tokens by preventing a concrete 404 failure mode.	3 / 3
Actionability	It gives copy-paste-ready guidance: exact template and asset paths, the specific `../../../assets/...` to project-local rewrites, theme swapping via `<link id="theme-link">`, and speaker-notes markup via `<aside class="notes">`.	3 / 3
Workflow Clarity	The six-step authoring sequence is clear with a Recipe A/B decision branch, but it warns that mis-rewritten asset URLs leave navigation dead yet includes no verification checkpoint (e.g. open the deck and confirm navigation works).	2 / 3
Progressive Disclosure	The card is a thin, well-organized overview that signals one-level-deep references to the master skill, the full-decks catalog, template/theme folders, and the LICENSE, with no inline walls of reference material.	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 is a punchy marketing tagline anchored to a single example subject rather than a clear statement of the skill's general capability and trigger conditions. It names the right domain and audience but lacks an explicit 'when to use' clause and concrete action verbs.

Suggestions

Rewrite the description in third person as a general capability (e.g. 'Writes demo-day fundraising pitch decks...') rather than tying it to 'Open Design's demo-day pitch'.

Add an explicit 'Use when...' clause naming natural triggers like 'demo day pitch', 'fundraising deck', 'investor deck', or 'series A pitch'.

Replace output-description nouns with concrete skill actions such as 'generate slides', 'apply visual themes', and 'write speaker notes'.

Dimension	Reasoning	Score
Specificity	Names the domain and structural beats ('hook, traction, moat, and the raise') and audience ('accelerator partners, angels'), but describes the output artifact rather than concrete skill actions like generating slides or writing speaker notes.	2 / 3
Completeness	It states what the deck is, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2 with 'when' only implied.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('demo-day pitch', 'fundraising pitch deck', 'accelerator partners, angels'), but the example-specific framing ('Open Design's demo-day pitch') dilutes the trigger surface and omits common variants like 'investor deck' or 'series A'.	2 / 3
Distinctiveness Conflict Risk	The demo-day fundraising niche is fairly specific, but the description reads as one example deck and the body admits it is an entry point into the broader html-ppt family, leaving overlap risk with sibling deck skills.	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-pitch-deck/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.