Skip to content
Back to search

astro-conversion-kit

MarketplaceWorks with Claude CodeGitHub

Agent Skills that convert a WordPress site (or any live site) into a static Astro site with URL, SEO, content and pixel parity, then take it through launch. Works in Claude Code, Codex and any agent that reads SKILL.md.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ethanplusai--astro-conversion-kit/badge.svg)](/listings/ethanplusai--astro-conversion-kit)

HTML

<a href="/listings/ethanplusai--astro-conversion-kit"><img src="/api/listings/ethanplusai--astro-conversion-kit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 23 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "astro-conversion-kit",
  3. "owner": {
  4. "name": "Ethan Rogers"
  5. },
  6. "plugins": [
  7. {
  8. "name": "astro-conversion",
  9. "source": "./",
  10. "description": "Convert a WordPress site (or any live site) into a static Astro site with URL, content, SEO and visual parity gates, then launch it safely.",
  11. "skills": [
  12. "./skills/convert-site",
  13. "./skills/capture-site",
  14. "./skills/parity-gates",
  15. "./skills/visual-review",
  16. "./skills/suggest-improvements",
  17. "./skills/pre-launch",
  18. "./skills/launch-audit",
  19. "./skills/post-launch"
  20. ]
  21. }
  22. ]
  23. }
README.md · README · 167 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # astro-conversion-kit
  2. Convert a WordPress site to static Astro with your coding agent, and get back the same site: the
  3. same URLs, the same content, the same titles, descriptions, canonicals and structured data, the
  4. same media at the same paths, every redirect the old site performs, and a design checked pixel by
  5. pixel at 390, 768 and 1440 px. No PHP, no plugins, no database, no server to patch.
  6. It is a set of Agent Skills, so it runs in Claude Code, Codex or any agent that reads `SKILL.md`.
  7. Plain Node scripts do everything that has to be exact, and gates prove each part before the work
  8. moves on. A run ends with a pull request, a noindexed staging deploy and a launch runbook.
  9. WordPress is the first-class case. Anything served over HTTP works, because the capture reads the
  10. rendered HTML; see [docs/platforms.md](docs/platforms.md).
  11. ## Start
  12. Paste this into your coding agent, with your site in place of example.com:
  13. ```
  14. Convert https://example.com to Astro with https://github.com/ethanplusai/astro-conversion-kit
  15. ```
  16. That is the whole job. The agent installs the skills, asks you one message of questions (each
  17. with a stated default: where the repo goes, which host, how forms are handled), and runs to a pull
  18. request without stopping again. Answer "defaults" and it picks every default.
  19. To install the skills first, into any agent that reads Agent Skills:
  20. ```
  21. npx skills add ethanplusai/astro-conversion-kit
  22. ```
  23. In Claude Code, from its plugin marketplace:
  24. ```
  25. /plugin marketplace add ethanplusai/astro-conversion-kit
  26. /plugin install astro-conversion@astro-conversion-kit
  27. ```
  28. Or from a clone, which also lets you run any script by hand:
  29. ```
  30. git clone https://github.com/ethanplusai/astro-conversion-kit
  31. cd astro-conversion-kit
  32. npm install
  33. npx playwright install chromium
  34. node skills/convert-site/scripts/preflight.mjs
  35. ```
  36. `preflight.mjs` says which tools the run needs (Node, git, gh, the hosting CLI, the Playwright
  37. browser) and whether each is installed and logged in. Every script prints `--help`.
  38. ## Results
  39. ![45 WordPress sites converted to static Astro: average run time 83 minutes, design parity passed on 45 of 45, Google PageSpeed performance 74 to 98 on mobile and 87 to 99 on desktop](docs/examples/results.png)
  40. Averages over 45 WordPress conversions run with the kit, intake to pull request. Every run passed
  41. the pixel-parity review at all three widths.
  42. ### Demos
  43. Public WordPress sites converted by a coding agent following the skills as published. Each link
  44. is the Astro build on Vercel; each image is the live WordPress page beside the Astro build.
  45. Counts and timings are in [docs/examples](docs/examples/README.md).
  46. **sxsw.com** (WordPress VIP, block theme, 71 pages): https://sxsw-com-astro-v2.vercel.app
  47. ![sxsw.com home page hero, before on WordPress and after on Astro, with the hero video playing on both](docs/examples/sxsw-home.gif)
  48. **harvard.edu** (WordPress multisite, 457 pages): https://harvard-edu-astro.vercel.app
  49. ![harvard.edu /ai/ page, before on WordPress and after on Astro](docs/examples/harvard-ai-1440.png)
  50. **angrybirds.com** (WordPress on WP Engine, 388 pages, media in Vercel Blob): https://angrybirds-com.vercel.app
  51. ![angrybirds.com home page, before on WordPress and after on Astro](docs/examples/angrybirds-home-1440.png)
  52. ## What happens
  53. 1. **Intake.** At most four requests fingerprint the platform; one message asks you where the
  54. repo and hosting go, how forms are handled, and what the agent cannot detect.
  55. 2. **Capture.** A paced, read-only crawl (sitemaps, the WordPress REST API, links) saves every
  56. page's HTML, head tags, redirects, media list, fonts, feeds and screenshots into `capture/`.
  57. 3. **Plan.** `docs/plan.md`: templates, counts, the media decision, and a row for every oddity.
  58. 4. **Scaffold and baseline.** A new Astro repo on an `astro-rebuild` branch, with the capture
  59. frozen into `baseline/` so the gates never need the old site again.
  60. 5. **Build.** Layouts first, then pages from the captured markup, the captured CSS pruned by
  61. coverage, media at the original paths, forms and third-party scripts carried over by list.
  62. 6. **Gates.** Routes, redirects, SEO tags, visible text, links, media, sitemap, feeds, forms and
  63. scripts, checked against the baseline on every commit.
  64. 7. **Visual review.** Live and new screenshots per template at three widths, pixel-diffed, plus a
  65. computed-style check, until every pair passes; then every page at 390 and 1440.
  66. 8. **Launch checks.** `pre-launch` on the repo, a staging deploy, `launch-audit` against staging,
  67. a suggestions report, and the PR. You merge and launch; `post-launch` watches the first 30 days.
  68. [docs/process.md](docs/process.md) says what each phase produces and what proves it done.
  69. ## What you get
  70. - A pull request from `astro-rebuild` to `main` in a repo you own, with the gate output, counts,
  71. every exception and proposal, and the launch skills' "Not covered" sections quoted in full.
  72. - A noindexed staging deploy on Vercel or Cloudflare Pages (or a local preview and a first
  73. runbook step to deploy, if you have no hosting account yet).
  74. - Contact sheets: live, new and diff screenshots side by side for every template and width.
  75. - `docs/suggestions.md`: broken links, missing alt text, duplicate titles, slow images and other
  76. improvements the agent found but did not make, each with evidence, effort and risk.
  77. - `docs/LAUNCH.md`: the runbook, in order, with the exact commands for your host.
  78. - `npm run verify` in the new repo, so the gates keep working after the old site is gone.
  79. The default build reproduces the live site, faults included. Fixes are proposals you approve.
  80. ## WordPress, specifically
  81. The capture needs no admin login, plugin or database export; it reads what the site serves.
  82. - **Every public page and post**, from the sitemaps, the REST API (`wp/v2/pages`, `posts`,
  83. `media`, `categories`, `tags`) and the links between pages, so nothing the sitemap forgot is
  84. missed. Drafts and private content never appear; the API only returns what is public.
  85. - **Every image size.** The resized copies WordPress writes (`photo-300x200.jpg`, ...) and lists
  86. in `srcset` all stay at their paths, because other sites and old emails may link to any of them.
  87. - **Media that fits the repo stays in it**; larger libraries go to Vercel Blob or Cloudflare R2
  88. at the same URLs, with the decision made per site and written into the plan.
  89. - **`?p=` shortlinks, category-base collisions, shortcodes left in content, lazy-load
  90. attributes**, and the other WordPress habits, handled as listed in
  91. [docs/platforms.md](docs/platforms.md).
  92. - **Classic themes, page builders and block themes.** The build keeps the theme's CSS, pruned to
  93. the rules the pages use, and the per-page inline styles block themes emit.
  94. - **Forms** post to a third-party endpoint you name at intake. Analytics, tag managers, consent
  95. banners and chat widgets are carried over by list, so nothing is silently dropped.
  96. - **Redirects** the old site performs (including `www` and trailing-slash rules) become host
  97. rules, and the launch skills check that every old URL still lands somewhere.
  98. What a static site cannot do (site search, comments, carts, logins, user-generated content) is
  99. found at intake and reported as out of scope with the options: a third-party embed, keeping that
  100. part on the old platform under a subdomain, or a separate project.
  101. ## What it refuses
  102. To run on end-of-life Node; to submit forms or log in on the live site; to touch DNS; to commit
  103. anything but the scaffold to `main` (all work goes on `astro-rebuild` and reaches `main` through
  104. a pull request you merge); to soften a gate. One site per run.
  105. ## Security
  106. The converted site is static HTML, CSS, images and the scripts you keep. There is no PHP and no
  107. Node running on your server, so a runtime vulnerability has nothing to attack there. The build
  108. tooling runs Node on your machine and in CI and has to stay patched; third-party scripts you keep
  109. are their vendor's responsibility; TLS and security headers are handled at your host's edge, with
  110. a baseline set shipped in `vercel.json` or `_headers`. More in [docs/security.md](docs/security.md).
  111. ## Requirements
  112. - Node 22.23.4 or newer on the 22 line, or 24.22.1 or newer. Node 20 is end of life and refused.
  113. - git, and a GitHub account with `gh` logged in if you want the repo and PR created for you.
  114. - A Vercel or Cloudflare account for staging and production. Optional for the conversion itself.
  115. - Playwright's Chromium (`npx playwright install chromium`), for screenshots and visual review.
  116. - macOS or Linux. Windows is not supported in this version.
  117. - A coding agent that can run shell commands. If your agent has its own browser or can run
  118. subagents, the skills use them; without them every step still runs.
  119. Further reading: [hosting](docs/hosting.md), [platforms](docs/platforms.md),
  120. [dependencies](docs/dependencies.md), [FAQ](docs/faq.md). [AGENTS.md](AGENTS.md) tells an agent
  121. which skill to use when.
  122. ## Licence
  123. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.