Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

WordPress Theme to EmDash · emdash-cms | DecimalAI

Wordpress Theme To Emdash

SkillScore39Maintained

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.

Frontendby emdash-cms

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Frontend / UI pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/wordpress-theme-to-emdash/SKILL.md

decimalai skills pull wordpress-theme-to-emdash --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/wordpress-theme-to-emdash/SKILL.md https://app.decimal.ai/s/wordpress-theme-to-emdash/SKILL.md

Raw file: /s/wordpress-theme-to-emdash/SKILL.md ↗ · machine-readable summary at /s/wordpress-theme-to-emdash.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

23 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 56d ago

—-17% tokens0% turns39% of whole cases pass with skill (9/23)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-23	✗→✓	▲ Improved	—	—
case-22	✗→✓	▲ Improved	—	—
case-11	✗→✓	▲ Improved	—	—
case-13	✗→✓	▲ Improved	—	—
case-21	✗→✓	▲ Improved	—	—

Showing 5 of 23 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 7/30/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

emdash-cms / emdash

skills/wordpress-theme-to-emdash/SKILL.md

View on GitHub ↗

License MIT LicenseImported 8/1/2026Version v1Bundled 5 files

Skill contents

references/

SKILL.md

WordPress Theme to EmDash

Port WordPress themes to EmDash in six phases. Read the phase file before starting each phase.

Critical Rules

Copy scaffold first - Start every theme by copying scaffold/ from this skill
Take screenshots of demo - Identify the demo URL and capture all page types using agent-browser before starting work
No hard-coded content - Use getSiteSettings() for title/tagline, getMenu() for navigation
Server-rendered pages - Never use getStaticPaths() for EmDash content
Astro 6 - Use ClientRouter not ViewTransitions, Zod 4 syntax, Node 22+
Use emdash Image component - For all images, import Image from "emdash/ui"

Phases

| Phase | File | Summary | | ----- | ----------------------- | ----------------------------------------------- | | 1 | phases/1-discovery.md | Download theme, screenshot demo, capture images | | 2 | phases/2-design.md | Extract CSS variables, fonts, colors | | 3 | phases/3-templates.md | Convert PHP templates to Astro | | 4 | phases/4-dynamic.md | Site settings, menus, taxonomies, widgets | | 5 | phases/5-seed.md | Create seed file with demo content | | 6 | phases/6-verify.md | Screenshot, compare, iterate, build |

Checklist

Setup

] Copy scaffold/ to new theme directory. Unless otherwise specified by the user, make this a subdirectory of themes/ and name it after the WordPress theme (e.g., themes/twentytwentyfour/).
] Rename folder, update package.json
] Verify build: pnpm build

Phase 1: Discovery

] Theme source downloaded
] Demo site identified
] discovery/ folder created with screenshots/, images/, notes.md
] All page types screenshotted
] Sample images downloaded

Phase 2: Design

] CSS variables in global.css
] Fonts loading
] Colors match demo

Phase 3: Templates

] Homepage, single post, archive, category, tag, page, 404
] Components extracted (PostCard, etc.)

Phase 4: Dynamic

] Site settings (title, tagline, logo from CMS)
] Navigation menus (from CMS, not hard-coded)
] Taxonomies
] Widget areas (if applicable)

Phase 5: Seed

] Seed file created with demo images at .emdash/seed.json (or wired up via package.json#emdash.seed)

Phase 6: Verify

] Dev server applied seed cleanly on first request (no validation errors in logs)
] Output screenshots captured
] Visual comparison done
] Build succeeds: pnpm build
] LICENSE file downloaded (GPL-2.0 in most cases)
] README credits original theme

Reference Documents

references/astro-essentials.md - Astro 6 patterns
references/template-patterns.md - PHP → Astro conversion
references/concept-mapping.md - WP → EmDash concepts
references/emdash-api.md - Full API reference
references/design-extraction.md - CSS extraction techniques

Illustrative Want to see what wordpress-theme-to-emdash would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

7/27/2026, 20:39 UTC · 23 cases

Measured on 21 comparable cases — below the 22 needed to publish a lift, so this result is shown here but not on the registry card or leaderboard.

Lift

+39%

39% vs 0%

Agent turns

1.0 vs 1.0

Tokens

-17%

1,529.48 vs 1,847.9

fail → pass · 9fail → fail · 14

Per-case results (23)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-23 After finishing design extraction in Phase 2, what is the next sequential phase in the theme conversion process?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-22 What files and subdirectories must be created inside the discovery folder during Phase 1?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-01 I need to port the Twenty Twenty-Four WordPress theme over to EmDash. Please analyze the theme, set up the project structure, extract the design tokens, convert the PHP templates to Astro, and verify the final visual match against the original demo.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-11 We are building post and category templates for our CMS layout in Astro. Should we implement getStaticPaths for content routing?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-13 Where should the theme's initial demo seed data file be saved within the project repository?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-21 How should we verify that the seed content loaded cleanly into the local development environment on initial startup?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-16 What credit requirement must be satisfied in the theme's README file upon completing the migration?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-02 Can you convert the WordPress theme located in `./downloads/oceanwp.zip` into a fully functional EmDash theme? Make sure to set up dynamic CMS site settings, build out the template components, create a seed file with demo content, and run a final build check.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-07 We are configuring dynamic navigation transitions in our Astro layout file for a ported theme. Should we import ViewTransitions or ClientRouter from astro:transitions?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-09 In our theme header template, how should we dynamically obtain the site title and tagline from the backend CMS?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-15 What open-source license file should be added to the ported theme directory to ensure compliance with WordPress theme licensing?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-08 We are displaying post thumbnails in our blog grid component for our layout. Where should the Image component be imported from?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-19 In which project conversion phase should CSS variables, fonts, and colors be extracted into global.css?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-03 I'm migrating a custom WordPress theme called 'minimal-blog' to an EmDash layout. Please execute the conversion process from initial theme discovery and template translation through to dynamic menu and taxonomy wiring and seed data validation.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-04 I am writing a custom PHP WordPress plugin to create a REST API endpoint that exposes custom post type taxonomy terms. How should I register the endpoint using register_rest_route in WordPress PHP?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-05 I'm building a standard standalone Astro 6 e-commerce site (not using EmDash) with static SSG pre-rendering for product details pages. How do I define static routes using dynamic params in Astro?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-06 I want to port a WordPress theme to a React Next.js App Router application. How should I structure the page routes and fetch WordPress data via GraphQL?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-10 In our navigation bar template, how should we dynamically retrieve the main site menu structure from the CMS?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-12 We are starting to migrate a WordPress theme called 'generatepress'. Into which workspace folder path should the scaffold directory be copied?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-14 During initial theme discovery, what automated browser tool should be used to capture screenshots of all page types from the live demo site?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-17 Which major version of Zod syntax should be targeted when defining content validation schemas in Astro 6?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-18 What is the minimum Node.js runtime version required to build and execute the ported theme?	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-20 What package manager build command should be executed to verify layout compilation before and after template verification?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted, and 21 counted toward the lift figure. The other 2 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +39 percentage points is the difference between those two pass rates over the 21 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 0%
Pass rate with the skill: 39.1%
Cases attempted: 23
Cases counted toward lift: 21
Cases that regressed: 1
Skill version measured: v1
Run completed: 7/27/2026, 20:39 UTC

The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run39

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 56 days ago

Other measured skills in the registry, with their headline benchmark lift.