CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 strong, highly actionable skill: concrete copy-paste code, a clear multi-step workflow with a validation checklist, and a self-contained structure with one-level-deep external pointers. The main weakness is conciseness — component definitions and caveats recur and could be de-duplicated.

Suggestions

Define the Title/Footer/Eyebrow components once and reference them from both Step 4 and Step 4b (or extract the shared JSX into a references file) to remove the duplicated component blocks.

Consolidate the repeated "do not modify real slides" guidance into a single prominent statement (e.g. once in the intro and once in Anti-patterns) rather than restating it across Steps 1–6.

DimensionReasoningScore

Conciseness

Content is dense and assumes Claude's competence (no basic-concept explanations, real JSX), but the same Title/Footer/Eyebrow component definitions appear twice (Step 4 template and Step 4b skeleton) and the "do not edit real slides" caveat is repeated several times, so it could be tightened — matching the score-2 anchor of mostly efficient but with some redundancy.

2 / 3

Actionability

Provides fully executable, copy-paste-ready JSX components with concrete inline styles, exact hex values and file paths, a fixed section-order template, and a 9-item self-review checklist, matching the score-3 anchor for fully executable, copy-paste-ready code.

3 / 3

Workflow Clarity

A clear six-step sequence (Identify input → Gather inputs → Pick id → Write .md → Write .demo.tsx → Self-review → Hand off) with an explicit validation checkpoint (the Step 5 self-review checklist, including "verify it against the Step 4b contract by reading the file") and conflict-resolution guidance, matching the score-3 anchor for a clear sequence with explicit validation steps and a checklist.

3 / 3

Progressive Disclosure

No bundle directories exist, so the SKILL.md is appropriately self-contained; the only external pointers ("see `references/webfonts.md` in `slide-authoring`", "read the `slide-authoring` skill") are one level deep and clearly signaled, and content is organized into well-labeled sections — matching the rubric's allowance for score 3 when a skill needs no external references.

3 / 3

Total

11

/

12

Passed

Description

100%

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 comprehensive and well-crafted: it states concrete actions and concrete file outputs, provides natural trigger phrases, answers both what and when, and scopes itself with an explicit anti-trigger. Voice is appropriately third-person/imperative. It is one of the stronger examples in the reference set.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("create, draft, author, or extract a slide theme") with concrete file outputs ("two paired files under `themes/` — `<id>.md` (palette, typography, layout, fixed Title/Footer components, motion) and `<id>.demo.tsx"), matching the score-3 anchor for listing multiple specific concrete actions.

3 / 3

Completeness

An explicit "Use this skill when the user wants to create..." clause answers both what and when, reinforced by "Triggers on phrases like...", matching the score-3 anchor for clearly answering both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural user phrasings — "create a theme", "make a theme called X", "extract a theme from <slide>", "build a theme from these images" — giving good coverage of terms a user would naturally say, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to "this open-slide repo" and `themes/` bundle authoring with an explicit negative boundary ("Do NOT use for editing real slides — only for authoring the theme bundle"), giving a clear niche unlikely to conflict, matching the score-3 anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
1weiho/open-slide
Reviewed

Table of Contents

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.