open-design-landing-deck

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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./design-templates/open-design-landing-deck/SKILL.md

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 well-structured, token-efficient overview with executable commands, a clear sequenced workflow, and a useful self-check checklist. Main gaps are a missing validate-retry loop in the workflow and a few referenced files not shipped in this skill's own bundle.

Suggestions

Add an explicit feedback loop after compose (e.g. 'If a slide overflows 100vh, trim copy or split into two slides and re-run') to reach a workflow_clarity of 5.

Ship or clearly mark the location of inputs.example.json and schema.ts, or note that they are inherited from the sister skill so references resolve unambiguously.

Trim the print-magazine analogy sentence to tighten conciseness further.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's intelligence (no explaining HTML/CSS/magazines), with only minor illustrative phrasing like the print-magazine analogy that could be trimmed.	4 / 5
Actionability	It provides concrete, executable commands (`npx tsx scripts/compose.ts inputs.json out/index.html`, imagegen/placeholder invocations) with a typed slide table, though referenced files like inputs.example.json and schema.ts are not present in this skill's own bundle.	4 / 5
Workflow Clarity	A clear four-step numbered workflow (Author inputs, Optional imagery, Compose, Self-check) with a concrete verification checklist, but it lacks an explicit validate-fix-retry feedback loop for the compose step.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with one-level-deep references to sister skills and bundle files, though several referenced paths (inputs.example.json, schema.ts) live outside this skill's bundle.	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 conveys a clear, premium deliverable and audience but reads as a product blurb rather than capability guidance, and it omits an explicit 'Use when' trigger clause. It is mostly distinct from sibling skills yet would benefit from action verbs and explicit trigger phrasing.

Suggestions

Rewrite the description in third person with capability verbs, e.g. 'Composes a horizontal brand-story deck... generates a self-contained HTML file from inputs.json.'

Add an explicit 'Use when...' clause with natural trigger terms (e.g. 'Use when creating a brand-story, pitch, or GTM deck, or when the user mentions slides, marketing decks, or launch decks.').

Include common synonyms and formats (pitch deck, slides, presentation) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names a concrete deliverable ("brand-story deck") and audience ("partners and press") but describes the product rather than listing concrete actions the skill performs; no capability verbs like 'composes' or 'generates'.	3 / 5
Completeness	It clearly states the 'what' (a deck explaining why OpenDesign exists, what it believes, where design is going) but lacks any explicit 'Use when...' trigger clause, capping completeness at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	It includes natural phrases a founder would say ("brand-story deck", "marketing & GTM deck", "partners and press"), though it misses common synonyms like 'pitch deck', 'slides', or 'presentation'.	4 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct ("OpenDesign's brand-story deck", "marketing & GTM"), with only minor overlap risk against the family of related deck/slide skills it explicitly references as sisters.	4 / 5
	Total	14 / 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: df84ae5

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