Elementor apis and deprecations

Skill randhoy/agent-skills-pack/.agent/skills/wp/elementor-apis-and-deprecations

Install

npx -y skills add randhoy/agent-skills-pack --skill elementor-apis-and-deprecations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Modernize Elementor integrations safely across versions. Use for deprecated hook/method replacement, phased API migrations, and behavior-stable upgrades in any project.

SKILL.md

1.9 KB, 367 tokens by cl100k_base, as published. Nobody here has run it

Elementor APIs And Deprecations

Core (Universal)

Trigger Scope

Use this skill when migration is the primary goal:

deprecated hooks/methods warnings
post-upgrade breakage
mixed legacy/current Elementor APIs
phased modernization with minimal regressions

Workflow

Inventory legacy surface.

registration hooks
manager calls
legacy method patterns

Prioritize by impact.

boot-breaking first
editor-breaking second
frontend-only third

Migrate in thin slices.

one subsystem per patch
preserve storage/output semantics

Validate after each slice.

widget discoverability
control persistence
render parity

Record migration notes.

replaced APIs
verification outcome

Legacy To Modern Map

Legacy pattern	Modern pattern
old widget registration hooks	`elementor/widgets/register`
deprecated widget registration calls	manager `register()`
legacy underscored control registration methods	`register_controls()`
mixed old/new registration in same subsystem	one modern style per subsystem

Guardrails

Do not mix old and new registration styles in the same flow.
Do not bundle migration with unrelated refactors.
Do not change visible behavior unless explicitly requested.
Always keep compatibility gate before Elementor symbol usage.

Migration Checks

After each slice, check:
widget appears in editor
controls save and persist
frontend output parity with previous stable state

Minimal Example

// modern
add_action( 'elementor/widgets/register', [ $this, 'register_widgets' ] );

public function register_widgets( $manager ): void {
    $manager->register( new \Vendor\Widget\Hero_Widget() );
}

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.