html-ppt-zhangzara-coral

Open Design's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.

Quality

57%

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

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with a clear sequenced workflow and an explicit output contract, but it is held back by abstract guidance for designing missing layouts, absent validation checkpoints, and references to bundle files (example.html, LICENSE, template.json) that do not exist in the skill.

Suggestions

Add a verification step to the workflow (e.g., open the cloned example.html in a browser / check the artifact renders before finalizing) so the sequence has an explicit checkpoint.

Make the 'designing missing layouts' step more actionable by specifying the concrete constraints to reuse (font stack, palette hex values, spacing rhythm) rather than abstract vocabulary.

Either ship the referenced bundle files (example.html, LICENSE, template.json, assets/) or remove the dangling references so progressive-disclosure navigation does not dead-end.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — 'A single self-contained HTML deck — typography, palette, decorative system, and slide vocabulary are all tuned together' — with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Concrete steps appear ('Clone example.html', 'Replace placeholder content', emit '<artifact>' tags), but 'design it from scratch using the same fonts, palette, decorative vocabulary' is abstract direction rather than executable guidance, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	A clear six-step sequence is present, but there are no validation or verification checkpoints (e.g., confirming the cloned file renders or the artifact is well-formed), matching 'steps listed but validation gaps; checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	Sections are well organized and one-level-deep references are signaled, but the referenced bundle files (example.html, LICENSE, template.json, assets/deck-stage.js) are not present in the skill bundle, so navigation leads to dead ends — 'references present but not clearly signaled / backed by actual structure'.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 subject and audience but reads as a product blurb rather than actionable skill guidance: it lacks concrete actions and any explicit 'Use when...' trigger clause, which caps both completeness and trigger quality. It is distinguishable but not sharply so without trigger phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when planning a community-growth campaign across GitHub/Discord/X, or when the user asks for a marketing & GTM deck').

Replace abstract topics ('the loops, the content calendar, and the pipeline math') with concrete actions the skill performs (e.g., 'drafts the slide plan, builds written slides, and runs a critic pass against a growth rubric').

Add common natural keyword variations users would actually say (e.g., 'community growth', 'go-to-market plan', 'marketing deck', 'growth campaign') to improve trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain ('community-growth campaign across GitHub, Discord, and X') and a few activities ('the loops, the content calendar, and the pipeline math'), but these are abstract topics rather than concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the deck is ('a decision-grade marketing & GTM deck for growth team, community lead') but provides no 'Use when...' or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Relevant terms appear (community-growth, GitHub, Discord, X, content calendar, pipeline, marketing & GTM, deck) but natural trigger phrasing a user would say is thin and missing common variations, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The community-growth / marketing-GTM deck niche is fairly specific, but without explicit triggers it could still overlap with other marketing or deck-building skills, matching 'somewhat specific but could still overlap'.	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: 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-coral/SKILL.md
Commit: f2760fd

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