CtrlK
BlogDocsLog inGet started
Tessl Logo

site-creator

Create a WordPress site from a rough idea using Studio and shared WordPress skills.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/claude-code/skills/site-creator/SKILL.md

The canonical home for this skill is site-creator in Automattic/build-with-wordpress

SKILL.md
Quality
Evals
Security

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.

The body is a well-structured, concise orchestrator overview with an explicit sequenced workflow and mandatory validation checkpoints; its only gaps are a minor lack of exact invocation examples for workflow events and the absence of any progressive-disclosure bundle.

Suggestions

Show the exact record_workflow_event invocation (with arguments) for the started and completed stages so the workflow calls are copy-paste ready.

Consider extracting the brief template or design-options handoff details into a reference file to keep the overview closer to a pure pointer and improve progressive disclosure.

Make the validation gate in step 6 a named checklist so the 'mandatory before complete' requirement is an explicit, runnable verification step.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and deliberately delegates specialist detail to sibling skills ('Do not duplicate specialist guidance here'); every section earns its place with no padding about what WordPress or Studio is.

5 / 5

Actionability

It provides concrete, executable guidance — an exact brief template, verbatim user-facing wording, and specific record_workflow_event calls with parameters — but stops short of showing the exact invocation shape for the workflow events, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 6-step numbered sequence includes explicit checkpoints ('Wait for the user's answer before continuing'), a mandatory validation loop ('the studio validation loop is mandatory before considering the work complete'), and started/completed workflow events, matching the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

The content is well-organized into clear sections with one-level-deep, clearly signaled sibling-skill references and no nested references; it scores just below 5 because the ~108-line overview is self-contained with no bundle files to split despite being longer than the simple-skill threshold.

4 / 5

Total

18

/

20

Passed

Description

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

The description is concise and identifies a clear niche, but it lacks an explicit 'Use when...' trigger clause and only names a single concrete action, capping completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user wants a new WordPress site built from a prompt, brief, or rough idea.'

List a couple more concrete actions to raise specificity, e.g. 'Create a WordPress site from a rough idea, draft the site brief, and coordinate design and theme build-out.'

Include common user phrasings or file/signal terms (e.g. 'new WordPress site', 'build a site from a brief') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain (WordPress site creation) and one concrete action ('Create a WordPress site from a rough idea'), but does not enumerate several specific actions, fitting the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

It gives a clear 'what' (create a WordPress site from a rough idea) but has no explicit 'Use when...' or equivalent trigger guidance, so completeness is capped at 3 per the missing-trigger-clause rule.

3 / 5

Trigger Term Quality

It includes some relevant natural keywords ('WordPress site', 'rough idea', 'Studio') but misses common user variations and synonyms such as 'new site', 'build a site', or 'WordPress', matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Studio/WordPress niche is mostly distinct, but the phrase 'shared WordPress skills' creates minor overlap risk with closely related sibling skills like theme-creator and studio, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

13

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Automattic/build-with-wordpress
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.