What it does
Establishes what's already in front of the site (a host-provided CDN, Cloudflare, or nothing) and then recommends caching rules, cache-purge triggers, and origin settings specific to the detected host and CMS setup, rather than generic CDN advice that ignores host-specific quirks like a managed host's own edge caching layer.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/cdn-setup-advisor/ (or ~/.claude/skills/cdn-setup-advisor/ for all projects)
GitHub Copilot (VS Code)
.github/skills/cdn-setup-advisor/
OpenAI Codex
.codex/skills/cdn-setup-advisor/
Cursor
.cursor/skills/cdn-setup-advisor/ (or ~/.cursor/skills/cdn-setup-advisor/ globally)
Compatibility
Any WordPress site; benefits from knowing the current host and whether a CDN or reverse proxy is already active in front of it.
The complete SKILL.md for this skill:
---
name: cdn-setup-advisor
description: Use when a user wants help setting up or tuning a CDN for their WordPress site, or asks why cached content isn't updating after a CDN was added.
---
# CDN Setup Advisor
## When to use
The user wants to add a CDN to a WordPress site, or already has one configured but is seeing stale content, caching conflicts with a host's own edge layer, or unclear purge behavior.
## Procedure
1. Determine what's already in front of the site: a managed host's built-in CDN/edge caching, a separate service like Cloudflare, or nothing at all.
2. If the host already provides edge caching, check whether adding a second CDN layer on top would conflict (double caching, purge mismatches) before recommending one.
3. Recommend caching rules appropriate to the content type: aggressive caching for static assets (images, CSS, JS), shorter or bypassed caching for dynamic content (cart, account pages, admin).
4. Recommend how cache purging should be triggered (on content publish/update, via a plugin integration, or manually) so stale content doesn't linger after edits.
5. Note any WordPress-specific considerations: excluding wp-admin and logged-in sessions from the CDN cache, and handling cookies used for personalization correctly.
6. Present the recommendation as a step-by-step setup checklist specific to the detected host and CDN combination, not a generic "how CDNs work" explainer.
## Guardrails
- Never assume a one-size-fits-all caching rule is safe for dynamic pages (cart, checkout, account); flag those for exclusion explicitly rather than caching everything by default.
- Do not make the actual DNS or CDN configuration changes without the user's confirmation, since a misconfigured CDN can take the site offline or serve stale/broken pages to visitors.