wordpress-theme-to-emdash

Port WordPress themes to EmDash CMS. Use when asked to convert, migrate, or port a WordPress theme to EmDash, or when creating an EmDash site that should match an existing WordPress site's design. Handles design extraction, template conversion, and EmDash-specific features like menus, taxonomies, and widgets.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and well-sequenced with strong workflow clarity and verification checkpoints, but actionability is partly deferred to phase files that are absent from the bundle, and progressive disclosure is weakened because the referenced phases/ and scaffold/ directories do not exist.

Suggestions

Either include the referenced phases/*.md and scaffold/ bundle files or remove/adjust the references so navigation is not broken; the body currently points to paths that are not in the bundle.

Tighten checklist items that read as outcomes rather than actions (e.g., 'Colors match demo', 'Components extracted') into executable steps, since the real instructions are in phase files not present here.

Consider moving any remaining per-phase executable detail inline or confirming the phase files are bundled, so actionability does not depend on missing references.

Dimension	Reasoning	Score
Conciseness	The body is lean: a phase table, terse critical rules, and checkbox checklists with no over-explanation of concepts Claude already knows, so every token earns its place per the score-3 anchor rather than the padded anchor at 2.	3 / 3
Actionability	There is concrete guidance (commands like 'pnpm build', APIs like getSiteSettings()/getMenu(), paths like .emdash/seed.json), but many checklist items are non-executable ('Colors match demo', 'Components extracted') and the real per-phase instructions live in phase files that are not present in the bundle, leaving key details implicit as in the score-2 anchor.	2 / 3
Workflow Clarity	The six-phase table plus per-phase checklists and the final Verify phase ('Build succeeds', 'Visual comparison done') give a clear sequence with validation/verification checkpoints, matching the score-3 anchor with explicit feedback loops rather than the checkpoint-missing anchor at 2.	3 / 3
Progressive Disclosure	The five reference documents are present and well signaled one level deep, but the body also references a phases/ directory and a scaffold/ directory that do not exist in the bundle; scoring against the actual bundle structure, this missing structure and broken navigation pulls it down to the score-2 anchor rather than a clean one-level-deep layout at 3.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong across all dimensions: it names concrete capabilities, includes natural trigger terms, explicitly covers both what and when, and occupies a distinct niche with low conflict risk. It is a close match to the rubric's good-overall examples.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'design extraction, template conversion, and EmDash-specific features like menus, taxonomies, and widgets', matching the score-3 anchor for several specific concrete actions rather than the single-action anchor at 2.	3 / 3
Completeness	Explicitly answers both 'what' (porting themes, design extraction, template conversion, EmDash features) and 'when' via a clear 'Use when...' clause, satisfying the score-3 anchor for both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural user phrasings ('convert, migrate, or port a WordPress theme', 'match an existing WordPress site's design') that a user would actually say, giving good trigger coverage beyond the partial-anchor at 2.	3 / 3
Distinctiveness Conflict Risk	The narrow 'WordPress theme to EmDash' niche with distinct port/migrate triggers is unlikely to fire for unrelated skills, matching the clear-niche anchor at 3 rather than the overlap-prone anchor at 2.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: emdash-cms/emdash
Path: skills/wordpress-theme-to-emdash/SKILL.md
Commit: 53dbf22

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.