rp-execute-import

Runs generated extract/import pipelines and records migration execution results for Wix replatforming.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a large content migration to Wix by hand is error-prone and non-repeatable. This Skill runs the previously generated extract/import pipeline as a deterministic artifact, enforcing approval gates, dry-run validation, idempotent re-runs, and auditable completion reporting so nothing is written to the user's Wix site without explicit acceptance. ## Core Features & Use Cases - Gated execution plan approval: Presents a human-readable import plan (entities, counts, lossy items, notification muting, analytics exclusion) and blocks all writes until the user accepts. - Artifact-driven import: Runs the generated run-extract.js and run-import.js entrypoints with config/env credentials, never hand-issuing per-record Wix MCP writes. - Dry-run and safe-mode support: Validates with DRY_RUN=true captures, safe-mode blocked-record ledgers, and demo-catalog cleanup before live writes. - Targeted recovery: Supports --missing-only, --failed-only, and --deferred-only resume runs with a durable recovery-log.json and crosswalk-based idempotency. - Use Case: After setup and codegen for a WordPress-to-Wix migration are complete, use this Skill to dry-run the pipeline, present the execution plan, then run the live import of 1088 posts and 86 podcast episodes and produce a completion report with the dashboard URL. ## Quick Start Run the approved migration pipeline for my project and give me the completion report with imported counts and the Wix dashboard URL.

Frequently Asked Questions about rp-execute-import

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

FAQPage Schema
How do I run a Wix migration import after code generation?

Run the generated import entrypoint (for example node src/import/run-import.js) with credentials loaded from the project config env files, after extraction completes. The import must go through the generated artifact, not per-record agent or MCP writes.

How do I dry-run a Wix import before writing live data?

Invoke the same generated setup/import entrypoints with DRY_RUN=true or --dry-run. The runtime skips Wix calls, writes request captures to state/attempts/wix-request-captures.ndjson, and keeps placeholder IDs out of the crosswalk.

Can the agent perform Wix import writes directly via MCP?

No. Import writes must run through the generated artifact for reproducibility, idempotency, and verified request shapes. MCP is used only for grounding and verification at codegen time, not as the import transport.

How do I re-run only failed or missing records in a migration?

Use the generated import entrypoint's selective resume flags: --missing-only, --failed-only, or --deferred-only, optionally with --entity or --source-type. Each recovery run appends an entry to execution/recovery-log.json without overwriting earlier entries.

Why does the import halt when Wix credentials are missing?

The generated artifact needs real Wix write credentials such as WIX_AUTH_TOKEN to execute. Missing credentials are a blocker surfaced to the user; the flow must not substitute the agent's MCP account auth to complete writes.

Does the migration import historical analytics data?

No. Historical traffic and visitor statistics are explicitly out of scope and are not imported. This exclusion must appear in the execution plan's not-migrating list before the user accepts the plan.