theme-creator
Create a modern WordPress block theme.
59
42%
Does it follow best practices?
Impact
81%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/codex/plugins/wordpress-studio/skills/theme-creator/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too terse and lacks the detail needed for effective skill selection. It names the domain (WordPress block themes) but fails to enumerate specific capabilities and entirely omits trigger guidance ('Use when...'). A user searching for help with full site editing, theme.json configuration, or block template creation might not reliably match to this skill.
Suggestions
Add a 'Use when...' clause with explicit trigger terms like 'WordPress theme', 'block theme', 'full site editing', 'FSE', 'theme.json', 'block templates', 'block patterns'.
List specific concrete actions such as 'Generates theme.json configuration, creates block templates and template parts, registers block patterns, sets up global styles and typography'.
Include common file type references and variations users might mention, such as '.json', '.html templates', 'WordPress FSE', 'Gutenberg theme development'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('WordPress block theme') but only mentions a single vague action ('Create'). It does not list any concrete sub-actions like generating theme.json, creating block templates, registering block patterns, or configuring styles. | 1 / 3 |
Completeness | The description weakly answers 'what' (create a block theme) but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also too thin to merit a 2. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords ('WordPress', 'block theme') that a user might naturally say, but misses common variations like 'FSE', 'full site editing', 'theme.json', 'block templates', 'WordPress theme development', or '.php/.json' file types. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'WordPress block theme' provides some specificity that distinguishes it from generic web development skills, but it could still overlap with general WordPress development skills, theme customization skills, or web design skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid skill with a well-structured verification workflow and clear delegation to other skills. Its main weaknesses are the lack of executable code examples (especially for block markup patterns and functions.php setup) and the verbose layout rules section that could benefit from concrete examples or being split into a reference file. The skill would be significantly more actionable with copy-paste-ready block markup snippets.
Suggestions
Add executable code examples for key artifacts: a complete functions.php snippet with style enqueuing, and serialized block markup examples showing the correct full-width section pattern (outer group → inner group → columns).
Extract the detailed layout rules into a separate reference file (e.g., LAYOUT_PATTERNS.md) and reference it from the main skill, keeping only the key principles inline.
Add a concrete theme.json example showing recommended contentSize, wideSize, and other layout settings to make the guidance copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elaboration. The layout rules section is quite detailed and could be tightened—some bullet points repeat similar concepts (e.g., multiple bullets about full-width alignment). The ownership and principles sections add moderate value but border on telling Claude things it could infer. | 2 / 3 |
Actionability | The skill provides concrete file structure and specific rules (e.g., enqueue style.css in functions.php, block markup patterns), but lacks executable code examples. The wp_enqueue_style line is mentioned inline but not shown in a complete functions.php snippet. Block markup examples (e.g., what a correct core/group with align:full looks like in serialized HTML) are entirely absent, which is a significant gap for a theme-building skill. | 2 / 3 |
Workflow Clarity | The verification flow is clearly sequenced with explicit validation checkpoints: validate block markup → repair if invalid → re-validate → activate → review. The feedback loop (repair and re-run until clean) is explicitly stated. The workflow also includes start/end event recording and clear handoff points to other skills (studio, auditing). | 3 / 3 |
Progressive Disclosure | The skill references other skills (studio, auditing) for delegation, which is good. However, there are no bundle files provided and no references to supplementary documentation for the detailed layout rules or block markup examples that would benefit from being in separate files. The layout rules section is quite long and inline, and could be better organized with references to examples or a separate patterns file. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Automattic/build-with-wordpress
- Commit
1c076c2
- 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.