Claude Code skills that unbreak WordPress when caches lie, Local crashes, and Hostinger pretends nothing's wrong.
You spend 4 hours debugging a WordPress site only to discover the answer was one button click in the Hostinger panel. WP Rescue Kit teaches Claude (via Claude Code skills) the operational truths that take humans years to learn the hard way — so the next time you (or Claude on your behalf) hits one of these walls, the answer is already loaded.
Three skills, one mission: stop wasting hours on problems with 30-second fixes.
The single most valuable thing in this kit. Hostinger has THREE cache layers. Most "my site shows the wrong content" problems are because someone purged ONE and assumed it was done.
Triggers when: working on a Hostinger-hosted WP site, anonymous users see different content than logged-in users, content updates aren't appearing, "Hello world!" appears in incognito, LiteSpeed isn't updating.
When Local won't start with mysqladmin: connect to server at '::1' failed. Usually a port conflict in sites.json. This skill knows the file path, the failure modes, and the 30-second fix.
Triggers when: Local by Flywheel won't boot, MySQL connection errors, lightning-services crashes.
How to ship WordPress changes when you have only wp-admin — no SSH, no FTP, no local install. Theme File Editor + Plugin Upload + Code Snippets + a CodeMirror automation trick most people never figure out.
Triggers when: Local is broken but you need to deploy, you only have wp-admin browser access, you need to inject scripts/code/content without SSH.
# macOS / Linux / Git Bash on Windows
git clone https://github.com/OmarEltak/wp-rescue-kit.git /tmp/wp-rescue-kit \
&& mkdir -p ~/.claude/skills \
&& cp -r /tmp/wp-rescue-kit/hostinger-ops ~/.claude/skills/ \
&& cp -r /tmp/wp-rescue-kit/local-by-flywheel-fix ~/.claude/skills/ \
&& cp -r /tmp/wp-rescue-kit/wp-deploy-without-local ~/.claude/skills/ \
&& rm -rf /tmp/wp-rescue-kit \
&& echo "✅ Installed. Restart Claude Code to pick up the skills."git clone https://github.com/OmarEltak/wp-rescue-kit.git
cd wp-rescue-kit
cp -r hostinger-ops local-by-flywheel-fix wp-deploy-without-local ~/.claude/skills/Skills load automatically when their description matches what you're asking Claude to do. No registration, no config.
ls ~/.claude/skills/
# Should show: hostinger-ops, local-by-flywheel-fix, wp-deploy-without-local (among others you have)In Claude Code, the next time you mention Hostinger, Local, or wp-admin deployment in a conversation, Claude should automatically reference the relevant skill.
A WordPress site for an air conditioning company in Riyadh launched on May 3, 2026. The owner spent 3 days configuring a custom theme, writing 13 blog posts, setting up Search Console, GA4, the works.
His own browser showed everything perfect. Customers reported seeing the default "Welcome to WordPress" page with the Twenty Twenty-Five theme.
He cleared the WordPress LiteSpeed cache. Nothing changed. He cleared his browser cache. Nothing changed. He suspected DNS hijacking, malware, hackers, duplicate WP installs.
The actual cause: Hostinger's CDN edge cache had captured the empty install at the moment Hostinger auto-created the site, and was serving that empty version to anonymous visitors forever — even after the site was fully built. WP-level cache purging never touched the CDN edge.
The fix was one click in the Hostinger panel: Dashboard → "Clear cache" button (which flushes all 3 layers at once).
If Claude had known this from the start, the entire 3-day debug session would have been resolved in 30 seconds. So we built the skill.
The other two skills (local-by-flywheel-fix and wp-deploy-without-local) come from the same engagement — they were the workarounds we needed after Local crashed mid-session and we had to deploy directly to live without staging.
- Operational, not theoretical. Every section ends with a fix you can copy-paste.
- Real failure modes. Not "best practices" — the actual breakages that happen in production.
- Diagnostic flows. Run command A → if X output, do B; if Y output, do C. No hand-waving.
- Battle-tested. Each skill was extracted from a 6+ hour debug session that ate someone's weekend.
- Claude Code (CLI) — primary target
- Claude Desktop — works if you use skill loading
- Anthropic Claude API — copy the SKILL.md content as a system prompt addendum
- Any LLM that supports Markdown context — these are just well-organized docs
Found a Hostinger trap or Local breakage we missed? PR it. Things we want:
- More hosting providers (
siteground-ops,wpengine-ops,kinsta-ops) - WordPress recovery skills (
wp-white-screen-recovery,wp-malware-cleanup) - Performance skills (
core-web-vitals-fix,cls-debug)
Format: each skill is a folder containing one SKILL.md with proper frontmatter. Keep skills under ~500 lines so they load fast and stay focused.
MIT — fork it, extend it, ship it. Just keep the attribution.
Built by @OmarEltak with Claude Code, after one too many cache rabbit holes.
If this saves you a debug session, star the repo so the next person can find it.