Agent Skills

federation

★ 572

by automattic

ActivityPub protocol specification and federation concepts. Use when working with ActivityPub activities, understanding federation mechanics, implementing protocol features, or debugging federation issues.

🧰 Not standalone — use together with automattic/wordpress-activitypub

need-for-speed

★ 470

by automattic

Run a frontend performance audit on a WordPress site and get actionable optimization recommendations.

🧰 Not standalone — use together with automattic/studio

qa

★ 470

by automattic

Compare extracted WXR content against the original source site page by page. Find missing text, headings, images, and links. Fix by patching the WXR or re-extracting individual pages. Produces a health score and structured report. Use when asked to "qa", "check extraction", "compare content", or "verify extraction quality".

🧰 Not standalone — use together with automattic/studio

site-spec

★ 470

by automattic

Gather the site name and layout preference before building a WordPress site. Run this before creating any new site.

🧰 Not standalone — use together with automattic/studio

studio-cli

★ 470

by automattic

Use the Studio CLI to manage local WordPress sites, authentication, and preview sites. Invoke this skill when you need to run Studio CLI commands, manage sites, or troubleshoot site issues.

🧰 Not standalone — use together with automattic/studio

adapt

★ 470

by automattic

Build a new platform adapter to extract content from an unsupported platform (Blogger, Ghost, Tumblr, etc.)

🧰 Not standalone — use together with automattic/studio

annotate

★ 470

by automattic

Open a browser with visual annotation tools. The user clicks elements on their site and leaves feedback — the agent reads annotations and makes changes. Use this when the user wants to point at specific elements to fix, tweak, or redesign.

🧰 Not standalone — use together with automattic/studio

block-content

★ 470

by automattic

Write editable WordPress block markup for local Studio sites, including core/html limits, block-theme layout rules, full-width sections, validation, and skeleton-first page/CSS recipes.

🧰 Not standalone — use together with automattic/studio

compose-page-blocks

★ 470

by automattic

Compose a single liberated page's WordPress block-editor markup from its rendered HTML and screenshot. Inputs are a sanitized HTML file, a desktop screenshot, the design-foundation tokens, the URL's archetype (page/post/product/etc.), and the source URL. Output is a string of valid block markup that round-trips through parse_blocks, uses theme tokens (no inlined hex colors), and contains only text drawn from the source HTML. Call per-page during the streaming watch loop after extraction has prod

🧰 Not standalone — use together with automattic/studio

creating-blocks

★ 470

by automattic

Templates and guidelines for creating new WordPress blocks from scratch — load this before generating block files

🧰 Not standalone — use together with automattic/studio

creating-themes

★ 470

by automattic

Guidelines for creating new WordPress block themes from scratch — load this before generating theme files

🧰 Not standalone — use together with automattic/studio

design-foundations

★ 470

by automattic

Build a coherent design-foundation JSON from a liberated site — semantic color/typography/spacing roles with evidence trails. Consumes the partial scaffold produced by liberate_design_foundation_scaffold plus aggregate HTML/CSS analysis and representative rendered HTML; produces a complete design-foundation matching the schema. Call after liberation, before theme generation.

🧰 Not standalone — use together with automattic/studio

design-qa

★ 470

by automattic

Visual-QA loop run after replica theme install and content import. Captures replica screenshots, applies a hard responsiveness gate at 390px AND a hard per-section visual-parity gate (measured SectionParity records, verdict computed by buildRunReport), runs qualitative vision review of source/replica pairs, checks accessibility, and drives a per-section escalation ladder of fixes via editing-themes/editing-blocks/rebuild-section (R1 CSS → R2 spec-rebuild → R3 re-extract → R4a AI canonical-block

🧰 Not standalone — use together with automattic/studio

editing-blocks

★ 470

by automattic

Guidelines for modifying existing WordPress blocks — load this before editing block files

🧰 Not standalone — use together with automattic/studio

editing-themes

★ 470

by automattic

Guidelines for modifying existing WordPress block themes — load this before editing theme files

🧰 Not standalone — use together with automattic/studio

generating-patterns

★ 470

by automattic

Guidelines and examples for generating WordPress block patterns — load this when creating patterns for themes

🧰 Not standalone — use together with automattic/studio

hosting-plans-helper

★ 470

by automattic

Answer WordPress.com plan, pricing, upgrade, and feature-tier questions (plan names, what each tier unlocks — plugins, themes, custom code, SSH, hosting — and current prices) from authoritative live data. Load before answering ANY plan, pricing, or feature-gating question; never answer these from memory.

🧰 Not standalone — use together with automattic/studio

liberate

★ 470

by automattic

Front door for the whole migration. FIRST routes on input type — a local directory of owned HTML/CSS/JS takes the local carry-to-block-theme path (dispatches liberate-local inline; no platform detection, no network extraction, no path checkpoint), while a URL takes the remote path: detect → discover, then ALWAYS stop and ask the operator (AskUserQuestion) which reconstruct path to take (blocks+products, or theme replication) BEFORE running extraction/capture, then dispatch the matching sub-skill

🧰 Not standalone — use together with automattic/studio

liberate-local

★ 470

by automattic

The OWNED LOCAL static-site path of /liberate — dispatched inline by `/liberate` when its input is a local directory (not a URL). Point it at a directory of hand-authored / Claude-generated HTML+CSS+JS and it stands up a fresh WordPress Studio site and converts the source into a native block theme + live editable pages, carrying the source's own CSS/JS for identical parity. The local-source analog of the URL path: no extraction (the source is already on disk), no platform detection — it provisio

🧰 Not standalone — use together with automattic/studio

match-page

★ 470

by automattic

Orchestrate whole-PAGE visual parity, with a replayable parity log so the work survives a reconstruct. PHASE 0 — if <outputDir>/parity-log.json exists, REPLAY its logged intents onto the current build first (apply + verify each by looking), so prior parity work is re-applied to whatever the latest reconstruction produced. PHASE 1 — one batch pass measuring EVERY band's built design vs the SOURCE screenshot across all axes, emitting a per-band verdict. PHASE 2 — iterate match-section on the diver

🧰 Not standalone — use together with automattic/studio

match-section

★ 470

by automattic

Reach VISUAL parity for ONE section by guiding AI to apply the captured design data (colors, padding, margins, full-bleed, font sizes, line-heights, families, alignment) to that section's WordPress block markup, then VERIFYING by looking at the source section and the built section side-by-side and iterating until they are visually identical. Non-deterministic on purpose — deterministic emission gets the structure right but misses visual parity; this skill closes the gap with an AI eyes-on loop.

🧰 Not standalone — use together with automattic/studio

migrate

★ 470

by automattic

Alias for `/liberate`. Migrate a website or an owned local directory into WordPress — point it at a URL (a live site you don't control) or at a local folder of HTML/CSS/JS you own, and it runs the full liberate pipeline (route on input → detect/discover/extract/capture + reconstruct for URLs; provision Studio + carry-to-block-theme for local dirs). Use `/migrate <url-or-dir>` exactly like `/liberate <url-or-dir>`.

🧰 Not standalone — use together with automattic/studio

model-local-data

★ 470

by automattic

Analyze an OWNED local static site's JavaScript data grids or repeated static-HTML content cards and emit a data-model.json that turns that data into real WordPress posts/taxonomy + native query loops while keeping the styling/animation/modal JS. Produces the model that liberate-local's convert step consumes. Use before liberate_convert_local_site when the source renders its content from JS data (catalogs, listings, galleries) or repeated post-preview cards in static HTML.

🧰 Not standalone — use together with automattic/studio

plugin-recommendations

★ 470

by automattic

Choose recommended plugins and plugin-provided blocks for features core WordPress blocks do not cover - ecommerce (WooCommerce), forms and newsletters (Jetpack), online courses and quizzes (Sensei LMS), polls, surveys and ratings (Crowdsignal), spam protection (Akismet) - while keeping generated content editable and avoiding raw HTML fallbacks. Any request to sell products or build a shop, store, or storefront requires WooCommerce with products.

🧰 Not standalone — use together with automattic/studio

rank-me-up

★ 470

by automattic

Run an on-page SEO audit on a WordPress site and get actionable recommendations to improve search visibility.

🧰 Not standalone — use together with automattic/studio

rebuild-section

★ 470

by automattic

R4a of the design-qa escalation ladder — rebuild ONE divergent section into canonical, editable WordPress core blocks from its source HTML, screenshots, spec, and design tokens, when R1–R3 (CSS / spec-rebuild / re-extract) could not reach visual parity. Dispatched as a subagent by design-qa; not user-invocable. Output ships ONLY if it re-scores `match` and survives canonicalization with no content loss — otherwise the loop falls to the R4b styled-island floor.

🧰 Not standalone — use together with automattic/studio

replicate-theme

★ 470

by automattic

Parity-first carry-and-scope theme reconstruction — dispatched by `/liberate` after capture. Instead of projecting the source onto editable WordPress blocks (the `replicate-with-blocks` path), it CARRIES the source page near-verbatim and SCOPES the source's own CSS under a per-site wrapper, producing a high-fidelity but NON-block-editable theme. It owns only the reconstruct→theme stage (capture already happened in `/liberate`); writes `output-carry.wxr` + a `<site>-carry` theme and installs into

🧰 Not standalone — use together with automattic/studio

replicate-with-blocks

★ 470

by automattic

Spec-driven, whole-site block-theme reconstruction for a liberated site. Invokes design-foundations → creating-themes → clustering → spec extraction → generating-patterns (fan-out, per cluster) → assemble → validate → install → design-qa to produce a responsive, editable WordPress block theme that matches the source site's layout, content structure, and visual design. Call after `liberate` (extraction) and before content import, or re-run standalone to re-theme an already-extracted site. Use whe

🧰 Not standalone — use together with automattic/studio

taxonomist

★ 470

by automattic

Analyze and optimize a WordPress site's category taxonomy. Exports all posts, uses AI to suggest an improved category structure — merging duplicates, retiring dead categories, creating missing ones, writing descriptions, and re-categorizing posts. Run this when the user wants to clean up or improve their categories.

🧰 Not standalone — use together with automattic/studio

testing-js

★ 470

by automattic

Guidelines for checking JavaScript files for syntax errors

🧰 Not standalone — use together with automattic/studio