Wp Static Clone

Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx). Use when the user wants to "scrape", "freeze", "archive", "static-ify", or "move to [host]" a WordPress site, or asks to turn a sitemap into deployable static HTML. Pulls every URL from sitemap_index.xml, fetches all assets, rewrites paths to be root-relative, strips WP runtime markup, and outputs a flat directory ready to deploy with no build command.

110 stars 10 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jdevalk/skills --skill wp-static-clone
Manual install
git clone --depth 1 https://github.com/jdevalk/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/wp-static-clone ~/.claude/skills/wp-static-clone

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# wp-static-clone

Turn a live WordPress site into a static HTML clone deployable on any static host. Driven by the site's XML sitemap. Handles the WordPress-specific gotchas — Cloudflare bot protection, mid-scrape link rewriting, proxied analytics, R2-offloaded uploads, comment-form runtime, Yoast attribution, Gravatar privacy — that a naïve `wget` run misses.

**Recipes live in `AGENTS.md`; reusable scripts in `scripts/`.** This file is the workflow, gotchas, and output structure.

## When to use

Trigger on requests like:

- "Scrape this WordPress site for [host]"
- "Freeze [domain] as static HTML"
- "Pull all the pages from this sitemap and turn them into static files"
- "Move this WP site to [host] with no build step"

The broad shape (sitemap → wget → root-relative paths → static host) generalises to any CMS that emits a standard XML sitemap. The runtime cleanup (comment forms, Plausible proxy, Gravatar, Yoast) is WordPress-specific.

## Workflow

### Phase 0 — Confirm intent

Before scraping, confirm:

- **Source URL** (the live site).
- **Target host** — Cloudflare Pages, Netlify, Vercel, generic static. Drives Phase 9.
- **Same or different domain** at the destination. Drives whether `og:url`, `<link rel="canonical">`, and JSON-LD `@id` stay absolute (same domain — correct SEO behaviour) or get rewritten (different domain).
Read the full skill on GitHub

Details

Skill name
wp-static-clone
Repository
jdevalk/skills
Path
wp-static-clone/SKILL.md
License
MIT
Repo updated
5 July 2026

FAQ

What does the Wp Static Clone skill do?

Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx). Use when the user wants to "scrape", "freeze", "archive", "static-ify", or "move to [host]" a WordPress site, or asks to turn a sitemap into deployable static HTML. Pulls every URL from sitemap_index.xml, fetches all assets, rewrites paths to be root-relative, strips WP runtime markup, and outputs a flat directory ready to deploy with no build command.

How do I install the Wp Static Clone skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jdevalk/skills --skill wp-static-clone. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Wp Static Clone popular?

It lives in jdevalk/skills, which has 110 GitHub stars and 10 forks.

Related skills

Emdash Github Actions

110

jdevalk/skills

Sets up GitHub Actions CI/CD workflows for EmDash plugins — TypeScript type-checking, ESLint linting, Vitest testing, npm publishing, and automated releases. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an EmDash plugin — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an EmDash plugin repo; set up testing in CI for a plugin; auto-publish a plugin to npm from GitHub; add security scanning or dependency auditing to

Git & Code Review10

Astro Github Actions

110

jdevalk/skills

Sets up GitHub Actions CI/CD workflows for Astro sites — `astro check` (TypeScript + content schema), ESLint, Prettier, build verification, Vitest testing, Lighthouse CI, link checking, npm audit, and automated deployment to GitHub Pages, Cloudflare Pages, Netlify, or Vercel. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an Astro site — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an Astro repo; set up `astro ch

Git & Code Review10

Astro SEO

110

jdevalk/skills

Audits and improves SEO for Astro sites. Use when the user asks to audit, set up, or improve SEO on an Astro site, or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema endpoints, NLWeb, hreflang, or search engine indexing in an Astro project. Produces drop-in code routed through `@jdevalk/astro-seo-graph` and chains into `metadata-check` for generated SEO strings.

Marketing, Sales & Business10

Authority Signoff Call

116

CALLE-AI/awesome-phone-call-agents

Places one real CALL-E phone call to the specific named authority a decision was already auto-authorized under (a duty magistrate, an on-call commissioner, a disaster-management chair) — for autonomous agent systems that resolve things on their own and need a real, attributable post-hoc confirm/override channel, not a pre-action approval gate. Demonstrated end to end, including a real placed CALL-E call, inside GovOS — an experimental incident-response simulation built for a separate hackathon, not a deployed government system.

DevOps & Cloud512

Vllm Studio

223

NeverSight/learn-skills.dev

Use when setting up, deploying, or operating vLLM Studio (env keys, controller/frontend startup, Docker services, branch workflow, and release checklists).

DevOps & Cloud42

Deployment Approval Call

116

CALLE-AI/awesome-phone-call-agents

Place one CALL-E phone call to get a spoken, code-verified human approval before an agent or a pipeline does something irreversible, such as a production deploy, a database restore, a bulk refund or a migration. Use when the approver is away from a keyboard and the action cannot be undone.

DevOps & Cloud512

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.