wp-site-health-auditor
Turns a WordPress Site Health report into a risk-tiered, backup-first fix plan with exact WP-CLI/PHP snippets. Use for site health, recommended improvements, or critical issue reports.
Profile →npx skills add sickn33/agentic-awesome-skills --skill wp-site-health-auditor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Turns a WordPress Site Health report (Critical issues / Recommended improvements / Passed tests) into a prioritized, risk-tiered fix plan — then executes the safe fixes and hands off the rest with exact commands or code.
How it works
- It parses input from the WordPress Site Health report or debug info and identifies three buckets: Critical issues, Recommended improvements, and Passed tests.
- It performs risk-tiered triage, classifying non-passed items into Tier 1 (safe/reversible), Tier 2 (requires host/server changes), or Tier 3 (informational only).
- It matches each item title to a predefined fix recipe and applies Tier 1 fixes directly, with backups as required by safety rules.
- For Tier 2 fixes, it provides exact code snippets, specifies where to insert them, and includes backup, lint, and rollback steps, noting that a host restart or support may be needed.
- For Tier 3 items, it reports informational details without attempting a fix.
- It ends with a recommendation to re-run Site Health after Tier 1/2 changes to confirm resolution of yellow items.
When to use it
- When a user pastes a WordPress Site Health report or debug info and asks what’s wrong
- When the user wants to clean up, harden, or speed up a WP install based on that report
- When the user wants a risk-tiered, backup-first remediation plan with exact commands
What it can touch
- wp-config.php (edits with caution)
- .htaccess (edits with caution)
- php.ini-equivalent settings (Tier 2 changes)
- Plugins/themes (activation/deletion as part of Tier 1 fixes)
Caveats
- Safety steps require backups before edits and lint checks after PHP changes
- Tier 2 fixes may require host-level access or restarts
- It will not invent fixes for items not covered by its recipes
# WP Site Health Auditor ## When to Use This Skill - The user pastes a WordPress Site Health report (`Tools > Site Health`), as text or screenshot - The user pastes raw Site Health debug info (`Tools > Site Health > Info`) and asks what's wrong - The user mentions "site health", "recommended improvements," or "critical issues" for a WordPress site - The user asks to clean up, harden, or speed up a WP install based on that screen Turns a WordPress Site Health report (Critical issues / Recommended improvements / Passed tests) into a prioritized, risk-tiered fix plan — then executes the safe fixes and hands off the rest with exact commands or code. ## ⚠️ Safety — read before touching any file This skill edits `wp-config.php`, `.htaccess`, and `php.ini`-equivalent settings, and deletes plugins and themes. All three are one bad edit away from a white-screen-of-death or a broken upload path. **Never skip this section, even for a one-line change, even if the user is in a hurry.** **Before any edit or deletion, in this order:** 1. **Back up the specific file(s) you're about to touch outside the web root**, not just "have a backup somewhere": ``` umask 077 backup_dir="../wp-site-health-back
- When to Use This Skill
- ⚠️ Safety — read before touching any file
- Overview
- Phase 1 — Parse the report
- Phase 2 — Risk-tiered triage
- Phase 3 — Fix recipes by item
- You should remove inactive plugins / themes — Tier 1
- postmaxsize smaller than uploadmaxfilesize — Tier 2
- You should use a persistent object cache — Tier 2
- Page cache is not detected — Tier 2
- REST API / loopback requests / background updates failing — Tier 2
- HTTPS not fully active — Tier 2
- Phase 4 — What NOT to invent
- Phase 5 — Output format
What does the wp-site-health-auditor skill do?
Turns a WordPress Site Health report into a risk-tiered, backup-first fix plan with exact WP-CLI/PHP snippets. Use for site health, recommended improvements, or critical issue reports.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill wp-site-health-auditor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.