html-ppt-zhangzara-bold-poster

OpenDesign's Series A growth story: the traction curve, the expansion motion, and why it's venture-scale. Built as a decision-grade fundraising pitch deck for Series A partners.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./design-templates/html-ppt-zhangzara-bold-poster/SKILL.md

Quality

Content

76%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 concise, well-structured instruction skill with concrete workflow steps and a clear output contract. Its main weakness is the missing explicit validation/critic checkpoint in the workflow and bundle references that cannot be verified against the provided files.

Suggestions

Add an explicit validation/critic step to the Workflow (e.g. '7. Critic pass: re-read the deck and confirm an investor would understand why this is venture-scale and urgent; fix and re-check') to lift workflow_clarity above 3.

Inline a minimal runnable example.html skeleton (or a representative slide) so the output contract and actionability are fully copy-paste ready rather than depending on an external file.

Ensure the referenced bundle files (example.html, template.json, LICENSE, assets/) actually ship alongside the skill so the progressive-disclosure references resolve.

Dimension	Reasoning	Score
Conciseness	Lean ~60-line body with no padding and no explanation of concepts Claude already knows; every section (At a glance, Best for, Avoid for, Workflow, Output contract, Source & license) earns its place, matching 'lean and efficient, every token earns its place'.	5 / 5
Actionability	Concrete, executable workflow steps with a copy-paste <artifact> output contract and an explicit list of what to preserve (fonts, palette, corner brackets, grain, SVGs), but the actual template content lives in the referenced example.html rather than inline, leaving a minor gap versus fully copy-paste-ready code.	4 / 5
Workflow Clarity	A clear 6-step numbered sequence is present, but there is no explicit validation/critic checkpoint in the body workflow even though the skill's own prompt references a 'critic pass against this rubric'; checkpoints are only implicit, matching 'steps listed but validation gaps'.	3 / 5
Progressive Disclosure	Well-organized single-file overview with clearly signaled one-level-deep references (example.html, template.json, ./LICENSE, upstream repo), but the referenced bundle files are absent from the evaluated bundle so the structure cannot be fully verified, a minor organization gap keeping it at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

61%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 clearly conveys a niche Series A fundraising deliverable with natural trigger terms and a distinct identity, but it omits an explicit 'Use when' trigger clause and describes output more than enumerable skill actions. These gaps cap completeness and specificity at 3.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g. 'Use when the user needs a Series A fundraising deck, a venture-scale growth narrative, or an investor pitch deck for VC partners') to lift completeness above the cap of 3.

Enumerate concrete skill actions in the description (e.g. 'drafts the traction-curve and expansion narrative, structures a decision-grade slide plan, and runs a critic pass') to move specificity from 3 toward 5.

Include a few more natural trigger synonyms a user might actually say ('seed-to-A transition deck', 'raise deck', 'VC pitch') to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Series A fundraising) and a concrete deliverable ('Built as a decision-grade fundraising pitch deck'), but describes the output rather than listing several distinct skill actions, so it stops at 'names domain and 1-2 concrete actions, not comprehensive'.	3 / 5
Completeness	The 'what' is clear (build a venture-scale Series A growth-story deck), but there is no explicit 'Use when...' clause in the description prose — trigger guidance lives only in the separate triggers list — so per the rubric's 'missing Use when caps completeness at 3' rule, it cannot exceed 3.	3 / 5
Trigger Term Quality	Natural terms appear in the description ('fundraising pitch deck', 'Series A partners', 'growth story') and the frontmatter triggers add 'pitch-deck', 'investor-deck', 'html deck/slides', giving good coverage with only a few common synonyms missing; not quite comprehensive enough for a 5.	4 / 5
Distinctiveness Conflict Risk	'Series A growth story for Series A partners' is a fairly distinct niche unlikely to fire for unrelated skills, but the broader 'pitch-deck/investor-deck' framing still risks minor overlap with general presentation skills, so it sits at 'mostly distinct, minor overlap' rather than a clean 5.	4 / 5
	Total	14 / 20 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: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-zhangzara-bold-poster/SKILL.md
Commit: 81044a0

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