rp-source-wordpress

Capture WordPress and WooCommerce REST schemas and define read contracts for migration codegen.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill rp-source-wordpress-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rp-source-wordpress
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/replatform/resources/rp-source-wordpress
Command: npx skills add https://github.com/divinaarmuela/Content --skill rp-source-wordpress-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Migrating data out of WordPress or WooCommerce requires platform-specific knowledge — REST namespaces, authentication models, pagination headers, and route quirks — that generic migration workflows cannot safely hardcode. This Skill centralizes that knowledge so discovery and code generation stages produce accurate source profiles and readers. ## Core Features & Use Cases - Automated REST Discovery: Runs a deterministic capture script that walks the WordPress REST index, samples each entity with OPTIONS and GET requests, and writes per-entity markdown with schemas, record counts, and relationships. - Route Classification: Classifies advertised routes into backend data, metadata, public commerce, and excluded categories (frontend, editor, runtime session, admin), writing a skipped-routes audit trail. - Read Contract for Codegen: Documents auth models (Application Passwords vs WooCommerce consumer keys), X-WP-Total pagination, _embed/_links relation resolution, and known traps like HTML entities in plain-text fields and URL-encoded variation slugs. - Use Case: When migrating a WooCommerce store to Wix, use this Skill during discovery to capture the source schema with proper credentials, then let the codegen stage generate a bulk-extract reader that reuses the shared wp-http transport module. ## Quick Start Ask the AI to run WordPress discovery against your site by providing the base URL and choosing whether to capture public content only or also private authenticated data.

Frequently Asked Questions about rp-source-wordpress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture a WordPress site's schema for migration?

Run the wp-discovery.js script with --base-url and --out-dir pointing at your migration project. It walks the REST index, samples each entity with OPTIONS and GET requests, and writes per-entity markdown files with schemas, record counts, and relationships.

What credentials are needed for WordPress REST API migration?

A complete capture requires WP_USERNAME and WP_APPLICATION_PASSWORD for wp/v2 routes. WooCommerce wc/v3 routes may also need WC_CONSUMER_KEY and WC_CONSUMER_SECRET if the Application Password returns 401/403. Public-only captures work without credentials but miss drafts, orders, and user roles.

Does WordPress REST discovery work on localhost sites?

Yes, discovery and source reads work against localhost or private hosts from your machine. However, Wix media import fetches files from Wix servers, so localhost media URLs are unreachable during live import — expose the source through an ngrok tunnel or defer media import.

Why do WooCommerce variation attributes cause import errors?

WooCommerce returns variation attribute values as URL-encoded slugs, not display names, and 'Any' variations have null values. Generated readers must map slugs to display names from the parent product's options array and treat all-null variations as cartesian entries, or Wix rejects them with MISSING_VARIANT_OPTION_CHOICE.

Can I migrate WordPress authors and user roles to Wix?

Only with authenticated capture using context=edit, since public /wp/v2/users exposes no roles or emails. Administrators map to the owner member, content roles to per-author members, and subscribers or customers become Wix contacts by default.