open-design-landing-deck

Open Design's brand-story deck for partners and press: why it exists, what it believes, and where design is going. Built as a decision-grade marketing & GTM deck for partners, press, community.

Quality

66%

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/open-design-landing-deck/SKILL.md

Quality

Content

85%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 an efficient, well-sequenced build guide with strong verification, but it leans heavily on a sister skill and several referenced files that are absent from this bundle, which weakens both copy-paste actionability and reference navigation. Bundling (or vendoring) the missing inputs.example.json, schema.ts, and the Atelier Zero stylesheet would close the gaps.

Suggestions

Bundle `inputs.example.json` and `schema.ts` (or inline their essentials) so the 'author inputs' step is self-contained and doesn't depend on the absent sister skill.

Vendor or clearly gate the dependency on `../open-design-landing/styles.css` and its image library so the compose and imagery steps resolve within this skill's bundle.

Add a short 'if the check fails' recovery note under the self-check (e.g. overflow -> trim copy or split the slide) to turn the verification list into a full validate-fix-retry loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what a deck, HTML, or a stylesheet is, and every element (pipeline diagram, slide-type table, command blocks, self-check list) carries concrete information, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	It provides copy-paste-ready commands (`npx tsx scripts/compose.ts inputs.json out/index.html`, the imagegen/placeholder invocations) and a concrete 11-slide example layout, but the imagery step and 'start from inputs.example.json' point at files/sister scripts that are not present in this bundle, leaving a minor gap versus fully executable everywhere.	4 / 5
Workflow Clarity	A clearly sequenced four-step workflow (author inputs -> optional imagery -> compose -> self-check) is followed by an explicit 8-item verification checklist covering keyboard nav, jumps, overview grid, responsive resize, reduced-motion, and Lighthouse, matching the 'clear sequence with explicit validation steps; checklists for complex processes' anchor.	5 / 5
Progressive Disclosure	Sectioning and one-level-deep references are well signaled (Workflow steps, Boundaries, See also), but several referenced bundle paths do not exist in this skill — `inputs.example.json`, `schema.ts`, the entire `../open-design-landing/` sister skill (styles.css, scripts, assets) and `../guizang-ppt/` — so navigation partly dead-ends, which caps the score below the 4 anchor whose 'minor organization gaps' assume references resolve.	3 / 5
	Total	17 / 20 Passed

Description

48%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 communicates what the artifact is and its audience, but it reads as positioning copy rather than a capability statement: it lacks concrete verbs and omits any explicit 'when to use it' guidance, which caps completeness. Adding an action-oriented verb list and a 'Use when...' clause would lift specificity and completeness.

Suggestions

Lead with concrete actions (e.g. 'Composes a horizontal brand-story HTML deck ... assemble slides, lay out stats/quote/cta sections, render a self-contained index.html') instead of thematic framing.

Add an explicit trigger clause, e.g. 'Use when the user asks for a pitch/brand-story deck, GTM slides, or a horizontal swipe presentation for partners or press.'

Include natural synonyms users would say ('pitch deck', 'slide deck', 'presentation') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and artifact ('brand-story deck', 'decision-grade marketing & GTM deck') but offers no concrete actions beyond 'Built as ...'; it frames the deck's themes ('why it exists, what it believes') rather than listing verbs like compose, assemble, or generate, matching the 'actions are minimal or generic' anchor and falling below the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It gives a clear 'what' ('Open Design's brand-story deck ... Built as a decision-grade marketing & GTM deck') but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap it cannot exceed 3; the audience mention ('for partners, press, community') only weakly implies 'when'.	3 / 5
Trigger Term Quality	It includes some relevant natural terms ('brand-story deck', 'marketing & GTM', 'partners and press') but misses common synonyms a user would actually say such as 'pitch deck', 'slide deck', or 'presentation', fitting the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'brand-story deck for partners, press, community' framing carves a fairly specific niche that is mostly distinct, with only minor overlap risk against generic pitch-deck or presentation skills, fitting the 'mostly distinct; minor overlap risk with closely related skills' anchor.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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 — 14 / 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: 2 missing, 5 suspicious	Warning

	Total	14 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/open-design-landing-deck/SKILL.md
Commit: f580271

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