CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-ppt-pitch-deck

OpenDesign'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

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/examples/html-ppt-pitch-deck/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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, well-structured entry card that gives concrete, executable authoring guidance — exact files to copy, exact asset-path rewrites, theme mechanics, and speaker-note placement — with a genuinely valuable warning about the template's parent-relative asset URLs. Its main gaps are the absence of an explicit post-build verification step and the fact that all referenced materials live outside the skill's own bundle, which cannot be verified from this card alone.

DimensionReasoningScore

Conciseness

The ~55-line body is efficient and bundle-specific — it does not explain concepts Claude already knows, and detail like the relative-URL breakage in step 3 is non-obvious and load-bearing. Minor instances of over-explanation could be trimmed (e.g., "meaning the deck never activates and slide navigation is dead", and the "When this card is picked" meta-context), keeping it below a 5 but above a 3.

4 / 5

Actionability

Guidance is concrete and executable: exact template folder and files to copy ("templates/full-decks/pitch-deck/", "index.html", "style.css"), the exact four asset files and their rewritten target paths, "keep the `.tpl-pitch-deck` body class", theme swap via "<link id=\"theme-link\">" and "T" cycle, and notes in "<aside class=\"notes\">". It is not a 5 because the rewrites are described in prose rather than shown as copy-paste-ready snippets (e.g., no example of the rewritten <link> tag).

4 / 5

Workflow Clarity

A clear six-step sequence (read master skill → copy template → bring runtime via Recipe A/B → pick theme → replace demo content → speaker notes), with step 3 explicitly flagging the 404 failure mode and offering two alternative recipes — a preventive checkpoint. It is not a 5 because there is no explicit post-build verification step (e.g., confirming the four links resolve or the keyboard runtime activates); this is not capped at 3 since the operation is neither destructive nor batch.

4 / 5

Progressive Disclosure

The body is a thin, well-organized entry card that appropriately delegates detail to the master skill ("[../html-ppt/SKILL.md]"), the full-decks catalog, and the template folders — good one-level-deep structure. It is not a 5 because the referenced paths point outside this skill's own bundle (no references/, scripts/, or assets/ exist here), so navigation cannot be satisfied from the skill itself, and the delegation chain (card → master skill → catalog) adds indirection.

4 / 5

Total

16

/

20

Passed

Description

56%Weight 40%Scale 1-5

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 establishes a clear, distinctive niche (demo-day fundraising pitch decks for accelerator partners and angels) with natural domain vocabulary, but it reads as a product tagline for one example deck rather than a statement of the skill's capabilities. It lacks any 'use when' trigger guidance and lists no concrete actions, relying instead on marketing phrases like "decision-grade" and "built to make a partner sit up by page three".

Suggestions

Add an explicit 'Use when...' clause naming triggering scenarios (e.g., 'Use when the user asks for a demo-day, Series A, or investor pitch deck, or mentions fundraising slides') — the missing 'when' currently caps completeness at 3.

Replace marketing phrases like "decision-grade" and "built to make a partner sit up by page three" with concrete capabilities the skill performs (e.g., 'Builds a fundraising pitch deck structured as hook, traction, moat, and ask, with speaker notes') to lift specificity.

Describe the skill's actions in third person ("Builds...", "Structures...") rather than framing the description around one example company's deck ("OpenDesign's demo-day pitch"), so the stated capability generalizes beyond the sample subject.

DimensionReasoningScore

Specificity

The description names the domain ("decision-grade fundraising pitch deck for accelerator partners, angels") and deck sections ("hook, traction, moat, and the raise"), but contains no concrete actions the skill performs — it is composed of noun phrases and marketing claims like "built to make a partner sit up by page three" rather than capabilities. It matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because no 1-2 concrete skill actions are listed, and not a 1 because the domain and output are genuinely named.

2 / 5

Completeness

The 'what' is stated ("Built as a decision-grade fundraising pitch deck for accelerator partners, angels"), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, capping this dimension at 3 per the judging guidelines. It is not a 4 because 'when' is not even weakly implied, and not a 2 because the 'what' is clearly stated rather than vague.

3 / 5

Trigger Term Quality

Natural phrases users would say are present: "demo-day pitch", "fundraising pitch deck", "pitch", "fundraising", plus audience terms "angels" and "accelerator partners". It is not a 5 because common variations like "investor pitch", "investor deck", "slides", "presentation", and "Series A" are absent; it is above a 3 because the core natural vocabulary of the domain is covered.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly clear — demo-day fundraising pitch decks aimed at accelerator partners and angels — so overlap with unrelated skills is low, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because generic terms like "pitch" and "fundraising" could collide with other pitch-deck or presentation skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

plugins/_official/examples/html-ppt-pitch-deck/SKILL.md

Reviewed

Table of Contents

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.