create-theme

Use this skill when the user wants to create, draft, author, or extract a slide theme in this open-slide repo. Triggers on phrases like "create a theme", "make a theme called X", "extract a theme from <slide>", "build a theme from these images". Produces two paired files under `themes/` — `<id>.md` (palette, typography, layout, fixed Title/Footer components, motion) and `<id>.demo.tsx` (a runnable demo slide that the dev-UI Themes panel previews). Do NOT use for editing real slides — only for authoring the theme bundle.

Quality

94%

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

Quality

Content

88%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.

A strong, highly actionable single-file skill: concrete templates, a sequenced workflow with a validation checklist, and well-signaled external references. The only real slack is mild over-explanation in the conceptual framing and the density of keeping everything inline.

Suggestions

Tighten the opening 'A theme is distinct from a slide's design const' paragraph to the single disambiguating sentence the agent actually needs; the three-way distinction can be stated in one clause.

Consider extracting the full paste-ready Title/Footer/Eyebrow component templates into a `references/components.md` so SKILL.md stays a leaner overview, leaving the inline skeleton as the primary artifact.

Fold the Step 4b contract bullets into the Step 5 checklist so the validation items and the contract they check against live in one place.

Dimension	Reasoning	Score
Conciseness	Mostly lean and concrete — paste-ready templates, contracts, and a checklist with little general-knowledge padding — but the opening conceptual framing (theme vs. `design` const vs. demo) and minor restatements across steps could be trimmed slightly. Not a 5 because of those few over-explanatory passages; not a 3 because nothing is noticeably padded.	4 / 5
Actionability	Fully executable: exact section order, paste-ready React components (Title/Footer/Eyebrow) with concrete inline styles, a complete demo `.tsx` skeleton, required imports, and an explicit Step 4b contract — copy-paste ready and covering the common cases.	5 / 5
Workflow Clarity	Six clearly sequenced steps with an explicit validation checkpoint (Step 5 self-review checklist plus "verify it against the Step 4b contract by reading the file") and a hand-off step; the operation is additive (new files under `themes/`) with an explicit no-touch boundary on real slides, so the destructive/batch cap does not bind.	5 / 5
Progressive Disclosure	Well-organized into labeled steps and anti-patterns, with one-level-deep, clearly signaled external references (the `slide-authoring` skill for canvas/type-scale defaults and `references/webfonts.md` for font loading). No bundle files exist under this skill's `references/`/`scripts/`/`assets/` to delegate to, and the core template legitimately stays inline, but the ~250-line single file is dense enough that it stops short of the clean overview-plus-references ideal.	4 / 5
	Total	18 / 20 Passed

Description

100%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.

A model description: it states the capability concretely, lists natural trigger phrases, answers both what and when, and draws a sharp boundary against the related slide-editing skill. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ("create, draft, author, or extract a slide theme") and specifies the exact deliverables — "two paired files under `themes/`" with enumerated contents (palette, typography, layout, fixed Title/Footer components, motion) and a runnable demo — giving comprehensive coverage of what the skill produces.	5 / 5
Completeness	Clearly answers both 'what' (produces the paired `<id>.md` and `<id>.demo.tsx` bundle with specified contents) and 'when' ("Use this skill when the user wants to create..." plus concrete trigger phrases), and adds an explicit negative boundary ("Do NOT use for editing real slides").	5 / 5
Trigger Term Quality	Explicitly lists natural user phrasings — "create a theme", "make a theme called X", "extract a theme from <slide>", "build a theme from these images" — covering synonyms and common variations a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (slide-theme authoring in the open-slide repo) with distinct triggers and an explicit exclusion of slide editing, minimizing overlap with sibling skills like create-slide.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: 1weiho/open-slide
Path: packages/core/skills/create-theme/SKILL.md
Commit: dad4c24

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