orbit-elementor-compatlisted

Across-Elementor-versions compatibility audit — fetches Elementor's current changelog + deprecation list at RUNTIME, then audits the plugin against today's reality. Auto-handles V3, V4 Atomic, V5+ as they ship — no manual rule update needed. Use when the user says "Elementor compat", "across versions", "after Elementor major release", "V4 atomic check", "deprecated Elementor APIs".
adityaarsharma/orbit · ★ 1 · Testing & QA · score 55

Install: claude install-skill adityaarsharma/orbit

# 🪐 orbit-elementor-compat — Runtime-evergreen Elementor compatibility > The skill that auto-stays-current with Elementor's release cadence. No "V4 atomic" hardcoding — it fetches what's current at runtime. --- ## Runtime — fetch live before auditing (DO THIS FIRST) When this skill is invoked: 1. **Fetch in parallel**: - https://elementor.com/pro/changelog/ → latest version + last 5 releases' changes - https://developers.elementor.com/docs/deprecations/ → current deprecation list - https://github.com/elementor/elementor/releases → latest tag + release notes - https://github.com/elementor/elementor/blob/main/CHANGELOG.md → free-version changelog - https://developers.elementor.com/elementor-editor-4-0-developers-update/ → V3→V4 migration (still relevant during coexistence) 2. **Synthesize current state**: - "What is the current major Elementor version as of today?" - "What APIs were deprecated in the last 2 minors? Last 6 months?" - "What new APIs / patterns has Elementor introduced that the plugin should adopt?" - "Has V4 become default for new sites yet (it did April 2026 per their announcement)?" - "Which V3 widgets / V4 Atomic Elements are the latest equivalents?" 3. **Audit the plugin** against the synthesized current rules. --- ## What gets checked (today's rule set, derived from today's fetch) ### A. Use of currently-deprecated APIs Whatever the fetched deprecation list says. Examples (as of last fetch — may differ today): - `_reg