html-ppt-zhangzara-bold-poster

Open Design'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

56%

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-zhangzara-bold-poster/SKILL.md

Quality

Content

57%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 content is concise and well-organized with a concrete output contract, but it is undermined by missing bundle files referenced throughout and by a workflow that lacks any validation checkpoints. Fixing the dangling references and adding a verification step would materially raise the score.

Suggestions

Ship the referenced `example.html`, `template.json`, and `LICENSE` (and any `assets/deck-stage.js`) so the workflow's first step is actually executable, or remove the references if the template is fetched from upstream at runtime.

Add a validation/checkpoint step to the workflow (e.g., after replacing placeholders, verify the deck opens, the navigation runtime is intact, and no placeholder text remains).

Tighten editorial padding such as "stay inside this one" and the trailing license paragraph to push conciseness toward fully lean.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence ("Editorial poster aesthetic with massive Shrikhand display", tight Best for / Avoid for sections, direct workflow steps) with only minor editorial padding such as "stay inside this one" that could be trimmed.	4 / 5
Actionability	Steps name concrete actions and files ("Clone `example.html`", "Replace placeholder content", the `<artifact>` output contract), but the foundational `example.html`, `template.json`, and `LICENSE` files referenced by the workflow are not present in the bundle, so the primary action cannot actually be executed as written.	3 / 5
Workflow Clarity	The six workflow steps are clearly numbered and sequenced, but there are no validation checkpoints (e.g., verify the deck renders, confirm all placeholders were replaced, check that the navigation runtime still works), so the sequence has explicit validation gaps.	3 / 5
Progressive Disclosure	The body is well sectioned (At a glance, Best for, Avoid for, Workflow, Output contract, Source & license) and signals one-level-deep references, but those references (`example.html`, `template.json`, `LICENSE`, `assets/deck-stage.js`) point to files that are not bundled, so the disclosed navigation does not actually resolve.	3 / 5
	Total	13 / 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 is specific in subject and audience but reads as a deck abstract rather than a capability statement, and it omits an explicit "Use when" trigger. It is mostly distinct from other skills but would benefit from naming concrete actions and an explicit use-when clause.

Suggestions

Lead with a concrete action verb (e.g., "Generates a decision-grade Series A fundraising pitch deck...") instead of describing the artifact.

Add an explicit "Use when..." clause naming trigger phrases users would actually say (e.g., "Use when creating a Series A pitch deck, investor deck, or fundraising raise materials for VC partners").

Broaden trigger synonyms to include "investor deck", "raise", and standalone "pitch deck" for fuller keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("decision-grade fundraising pitch deck for Series A partners") and subject matter ("traction curve, the expansion motion, and why it's venture-scale") but names no concrete actions the skill performs — it describes the artifact, not what the skill does.	2 / 5
Completeness	It gives a clear "what" (a decision-grade Series A fundraising pitch deck about Open Design's growth) but no explicit "Use when..." trigger clause, so per the rubric guidance completeness is capped at 3 with "when" only weakly implied by the audience mention.	3 / 5
Trigger Term Quality	Natural phrases a user would say are present ("Series A growth story", "fundraising pitch deck", "Series A partners", "venture-scale"), but common synonyms like "investor deck", "raise", or standalone "pitch deck" are absent, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Open Design / Series A growth-story framing carves a clear niche, but the surrounding trigger vocabulary (pitch deck, fundraising, investor deck) overlaps with other fundraising skills, leaving minor conflict risk.	4 / 5
	Total	13 / 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: 1a7a23d

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