design-previews-creator
Generate three parallel design preview options for a Studio-backed site and collect the user's preferred direction before theme implementation.
54
60%
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 ./plugins/codex/plugins/wordpress-studio/skills/design-previews-creator/SKILL.mdQuality
Discovery
57%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 communicates a specific and distinctive workflow for generating design previews for Studio-backed sites, which helps it stand out from other skills. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say. The specificity of actions could also be improved by detailing what the previews contain or how they're presented.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to choose a design direction, pick a theme, or preview website styles for a Studio-backed site.'
Include more natural trigger terms users might say, such as 'website design', 'theme options', 'design mockups', 'pick a look', or 'site styling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain (Studio-backed site design previews) and describes a workflow (generate three options, collect preference, then implement), but the concrete actions are somewhat abstract — 'generate design preview options' and 'collect preferred direction' lack detail about what those previews entail or how they're generated. | 2 / 3 |
Completeness | The 'what' is reasonably clear (generate three design previews, collect user preference, then implement theme), but there is no explicit 'Use when...' clause or trigger guidance. The 'when' is only implied by the nature of the task, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'design preview', 'Studio-backed site', and 'theme implementation', but misses common natural user phrases like 'website design', 'pick a theme', 'design options', 'mockup', or 'look and feel'. A user might not naturally say 'Studio-backed site' or 'preferred direction'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is quite distinctive — the combination of 'three parallel design preview options', 'Studio-backed site', and the specific workflow of collecting preference before implementation creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 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 well-structured workflow skill with clear sequencing and good scope boundaries. Its main weaknesses are the lack of concrete executable examples (no sample HTML template, no subagent invocation syntax) and some mild verbosity in the ownership and constraint sections. The workflow logic is strong but actionability would benefit significantly from at least one concrete code example.
Suggestions
Add a concrete HTML/CSS snippet showing the expected structure of a design preview file (e.g., a minimal header+hero template with CSS custom properties) to improve actionability.
Include an example of the subagent invocation pattern or tool call syntax so the parallel generation step is copy-paste ready rather than descriptive.
Consider trimming the 'Ownership' section, as its bullets largely restate what the workflow steps already communicate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections could be tightened—e.g., the 'Ownership' section restates what the workflow already covers, and the bullet lists in step 2 and step 3 are somewhat verbose for what are relatively straightforward instructions. | 2 / 3 |
Actionability | The skill provides clear structural guidance (file paths, parallel subagent pattern, presentation format) but lacks executable code examples. There are no HTML/CSS snippets showing what a preview file should look like, no concrete subagent invocation syntax, and the instructions for generating previews remain at the descriptive level rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The five-step workflow is clearly sequenced with logical progression from workspace setup through generation, presentation, user selection, and handoff. The user choice step includes explicit branching (pick, modify, or regenerate), and the handoff step specifies exactly what values to pass forward, serving as a validation checkpoint before theme implementation. | 3 / 3 |
Progressive Disclosure | The skill references external concerns appropriately (delegating to 'theme-creator' and 'studio') and keeps its scope focused, but with no bundle files provided, the references to these external skills are unverifiable. The content is well-sectioned but everything is inline in a single file with no supporting reference documents for the more detailed aspects like subagent patterns or HTML template examples. | 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.