site-creator
Create a WordPress site from a rough idea using Studio and shared WordPress skills.
48
49%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/site-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.
The description is too vague and lacks both concrete capability details and explicit trigger guidance. It names the domain (WordPress) but fails to enumerate specific actions the skill performs and provides no 'Use when...' clause. The phrase 'using Studio and shared WordPress skills' is internal jargon that doesn't help Claude or users understand when to select this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to create a new WordPress website, set up a blog, or build a site from scratch.'
List specific concrete actions the skill performs, such as 'Scaffolds WordPress site structure, selects themes, configures plugins, creates initial pages and content layout.'
Include natural keyword variations users might say, such as 'website', 'blog', 'WP site', 'web page', 'new site setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Create a WordPress site from a rough idea' which is a single vague action. It doesn't list concrete capabilities like theme selection, plugin configuration, content creation, page layout, etc. 'Using Studio and shared WordPress skills' is abstract and doesn't describe what the skill actually does. | 1 / 3 |
Completeness | The 'what' is weak ('create a WordPress site from a rough idea') and there is no explicit 'when' clause or trigger guidance. The description lacks a 'Use when...' statement, which per the rubric should cap completeness at 2, but since the 'what' is also vague, this scores a 1. | 1 / 3 |
Trigger Term Quality | It includes 'WordPress' and 'site' which are natural terms users might say. However, it misses common variations like 'website', 'blog', 'WP', 'web page', 'hosting', or specific WordPress concepts. 'Studio' is a somewhat niche term that may or may not match user language. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'WordPress' and 'Studio' provides some specificity that distinguishes it from generic web development skills. However, it could overlap with other WordPress-related skills (e.g., WordPress editing, WordPress plugin management) since it doesn't clearly define its niche beyond 'create a site from a rough idea'. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured orchestrator skill that clearly defines its role, delegates appropriately, and provides a clean workflow with good decision branching and validation checkpoints. Its main weakness is that actionability depends entirely on the referenced sub-skills—the skill itself contains no executable code or concrete commands, which is somewhat expected for an orchestrator but limits standalone usefulness. The brief template and exact user-facing wording are strong concrete elements.
Suggestions
Add concrete examples of the `record_workflow_event` calls (e.g., exact function signature or MCP tool invocation) so the tracking steps are copy-paste ready rather than abstract references.
Consider adding brief inline summaries of what each delegated skill does (one line each) so the orchestrator is useful even if a referenced skill is unavailable or unclear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and well-structured. It avoids explaining what WordPress, themes, or briefs are. It explicitly states 'Do not duplicate specialist guidance here when another skill already owns it' and follows through on that principle. Every section serves a clear purpose. | 3 / 3 |
Actionability | The workflow provides clear steps and exact wording for user prompts, but relies heavily on delegating to other skills (studio, theme-creator, design-previews-creator, auditing) without concrete commands or code. The brief template is specific and actionable, but the actual implementation steps are abstract references to other skills rather than executable guidance. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps, explicit decision branches (user wants design options vs. proceed with build vs. changes), validation checkpoints (step 6 with mandatory validation loop for serialized block content), and feedback loops (brief revision cycle). The workflow_event tracking adds clear start/end markers. | 3 / 3 |
Progressive Disclosure | The skill references multiple other skills (studio, design-previews-creator, theme-creator, auditing) as delegation targets, which is good progressive disclosure in principle. However, no bundle files are provided, so we cannot verify these references resolve correctly. The skill itself is well-organized with clear sections, but the references to other skills are not formatted as navigable links. | 2 / 3 |
Total | 10 / 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.