CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wordpress-theme-development

Use when creating or converting WordPress themes: theme.json v3, template hierarchy, block patterns, template parts, navigation overlays, breadcrumbs, block styles, child themes, or WordPress 7.0/7.1 theme features. Do not use for plugin back-end logic or store setup; use wordpress-plugin-development or wordpress-woocommerce-development.

Quality

82%

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

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

A highly actionable, well-sequenced theme-development workflow whose strength is concrete, version-specific WordPress 7.0/7.1 guidance with executable code throughout. Its weaknesses are monolithic structure with no progressive disclosure into reference files, generic boilerplate padding, and end-of-workflow-only validation without feedback loops.

Suggestions

Move the large version-specific blocks (full theme.json example, pattern markup for tabs/hero, icon registration) into files under references/ and keep short summaries with clearly signaled links in SKILL.md, converting the monolithic body into an overview.

Trim content Claude already knows — the boilerplate theme-header CSS comment, the standard theme directory tree, and generic per-phase action lists ('Register navigation menus', 'Test across browsers') — to cut tokens without losing guidance.

Add inline validation checkpoints per phase (e.g., after theme.json changes, verify compiled breakpoints; after pattern registration, confirm the pattern appears in the inserter) with fix-and-retry guidance instead of deferring all verification to Phase 8.

DimensionReasoningScore

Conciseness

The version-specific 7.0/7.1 guidance is dense and largely non-redundant, but the body pads with material Claude already knows — a boilerplate theme-header CSS block, the standard theme directory tree, and generic action lists like 'Test across browsers' / 'Performance testing' — plus a dated release banner ('7.1.4 "Mary Lou" (August 19, 2026)') that is time-sensitive and not isolated in an old-patterns/deprecated section. It sits between 'noticeably verbose' (2) and 'efficient' (4): mostly useful tokens with several trimmable sections.

3 / 5

Actionability

Code is complete and copy-paste ready across the common cases: full theme.json v3 config with viewport breakpoints, register_post_type/register_post_meta PHP, pattern PHP files (tabs, hero), navigation-overlay template parts with exact 'area' and 'overlay' values, breadcrumb filters, and wp_register_icon_collection() examples. This matches the anchor for fully executable, copy-paste-ready guidance covering common cases; it is clearly above 'mostly executable with minor gaps' (4).

5 / 5

Workflow Clarity

Phases 1–8 are clearly sequenced and there is an explicit WordPress 7.1 testing checklist plus a final compatibility checklist and quality gates, but validation appears only at the end of the workflow — no inline validate-then-proceed checkpoints or fix-and-retry feedback loops within phases. This matches 'clear sequence with most checkpoints present; minor validation gaps' and falls short of the anchor 5 requirement of explicit validation steps with error-recovery loops.

4 / 5

Progressive Disclosure

Internal structure is good (phases, headed sections, checklists), but the skill is a ~580-line monolith with no bundle files: content that clearly belongs in separate reference files — the full theme.json example, the pattern markup library, per-version feature details — is inlined with no one-level-deep references. This fits 'some structure but content that should be separate is inline' (3) rather than 2, since sectioning and navigation within the file are solid.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description with an explicit 'Use when' trigger clause, concrete scoped topics, and excellent boundary guidance that redirects adjacent domains to sibling skills. The only gap is trigger-term breadth — 'Gutenberg'/'block editor' synonyms are missing — and topic enumeration standing in for explicit action verbs.

DimensionReasoningScore

Specificity

The description names the domain and enumerates many concrete topics ('theme.json v3, template hierarchy, block patterns, template parts, navigation overlays, breadcrumbs, block styles, child themes'), which matches 'lists several specific actions; minor gaps in coverage'. It falls short of 5 because the concrete items are topic nouns rather than multiple specific actions — only 'creating or converting' are action verbs — and well above 3's '1-2 concrete actions'.

4 / 5

Completeness

It explicitly answers both questions: the 'what' via 'creating or converting WordPress themes' with an enumerated scope, and the 'when' via an explicit 'Use when' clause with concrete trigger phrases ('theme.json v3, template hierarchy, block patterns... WordPress 7.0/7.1 theme features'). This directly matches the anchor-5 example structure; the 'when' is neither missing nor weakly implied.

5 / 5

Trigger Term Quality

Natural trigger terms are well covered ('WordPress themes', 'child themes', 'breadcrumbs', 'block patterns', 'template parts', 'theme.json', version numbers), matching 'good keyword coverage; a few natural terms missing'. Not 5 because common user synonyms like 'Gutenberg' or 'block editor' are absent; not 3 since far more than 'some relevant keywords' are present.

4 / 5

Distinctiveness Conflict Risk

A clear niche (theme development only) with explicit negative boundaries ('Do not use for plugin back-end logic or store setup') and positive redirects to the sibling skills ('use wordpress-plugin-development or wordpress-woocommerce-development'), giving minimal conflict risk — the anchor-5 pattern.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (581 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/wordpress-skills/wordpress-theme-development/SKILL.md

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.