orbit-host-wpenginelisted

WP Engine compat audit — fetches WP Engine's CURRENT disallowed-plugins list + EverCache rules + filesystem restrictions AT RUNTIME. Auto-stays-current with WPE policy. Use when the user says "WP Engine", "WPE", "is my plugin WPE-compatible", "WPE banned plugins", or before a customer hosts on WP Engine.
adityaarsharma/orbit · ★ 1 · Testing & QA · score 55

Install: claude install-skill adityaarsharma/orbit

# 🪐 orbit-host-wpengine — Runtime-evergreen WP Engine compat > WPE's disallowed-plugins list and EverCache rules update regularly. This skill fetches what's true today. --- ## Runtime — fetch live before auditing (DO THIS FIRST) When this skill is invoked: 1. **Fetch in parallel**: - https://wpengine.com/support/disallowed-plugins/ → CURRENT disallowed list - https://wpengine.com/support/cache/ → EverCache rules + cookie patterns - https://wpengine.com/developers/ → environment specs (PHP versions, file paths) - https://wpengine.com/changelog/ → recent platform changes - https://wpengine.com/support/git/ → Git push deploy patterns 2. **Synthesize current state**: - "Is my plugin (or any dep) on WPE's disallowed list right now?" - "What cookie patterns bypass EverCache today?" - "What's the current PHP / WP version range supported on WPE?" - "Has WPE added any new restrictions / detection patterns?" 3. **Audit the plugin** against today's rules. --- ## What gets checked ### A. Disallowed-plugins match (the big one) WPE bans plugins that conflict with their stack. As of last fetch: - Caching: W3 Total Cache, WP Super Cache, WP Rocket (use EverCache) - Backup: BackupBuddy, BackUpWordPress (use native snapshots) - Hit counter: WP Postviews, etc. - Some security plugins that conflict with their built-in firewall The fetched list grows; the skill matches the user's plugin + its bundled deps. ### B. EverCache cookie rules **Whitepaper intent:*