agentsclimarketplace

Elementor ops and data

Skill randhoy/agent-skills-pack/skills/wp/elementor-ops-and-data

Run safe Elementor content operations in live or staging environments. Use for backup-first meta changes, scoped WP-CLI edits, template cloning, cache refresh, and verification loops.From its SKILL.md

Install
npx -y skills add randhoy/agent-skills-pack --skill elementor-ops-and-data

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.

SKILL.md

2.4 KB, 551 tokens by cl100k_base, as published. Nobody here has run it

Elementor Ops And Data

Core (Universal)

Trigger Scope

Use this skill when operating on persisted Elementor content:

  • bulk text/URL edits
  • _elementor_data and related meta operations
  • template clone/apply workflows
  • import/export integrity checks

Workflow

  1. Scope changes.
  • identify target post IDs and exact keys/tables
  1. Create rollback artifacts.
  • backup relevant meta before writes
  1. Run controlled mutation.
  • dry-run first
  • execute scoped updates
  1. Refresh generated state.
  • flush Elementor CSS/cache artifacts
  1. Verify outcome.
  • editor load
  • frontend render
  • metadata sanity

Verification Loop

Run this sequence for every non-trivial mutation:

  1. backup snapshot created
  2. dry-run reports expected blast radius
  3. write operation executed with scoped target
  4. cache/CSS regenerated
  5. editor and frontend parity verified

Guardrails

  • Never run broad replacements without explicit scope.
  • Never mutate Elementor meta without backup.
  • Do not treat _elementor_data as unstructured text.
  • Keep rollback artifacts until acceptance.
  • Keep data ops and structural widget refactors in separate passes.

Minimal Example

Bash / Linux / macOS:

wp post meta get <id> _elementor_data > backup-<id>.json
wp search-replace "Old" "New" wp_postmeta --include-columns=meta_value --dry-run --precise
wp search-replace "Old" "New" wp_postmeta --include-columns=meta_value --precise
wp elementor flush-css

PowerShell / Windows:

# Backup meta
$backupName = "backup-$(Get-Date -Format 'yyyyMMdd-HHmm')-$id.json"
wp post meta get $id _elementor_data | Out-File -FilePath $backupName -Encoding UTF8

# Dry-run (review what will change)
wp search-replace "Old" "New" wp_postmeta --include-columns=meta_value --dry-run --precise

# Execute (provide explicit yes flag)
wp search-replace "Old" "New" wp_postmeta --include-columns=meta_value --precise

# Refresh cache
wp elementor flush-css

Scope verification (before mutations):

# Count matching rows
$matchCount = wp db query "SELECT COUNT(*) as cnt FROM wp_postmeta WHERE meta_key='_elementor_data' AND meta_value LIKE '%Old%'" --skip-column-names
Write-Host "Will affect ~$matchCount rows. Review backup first."

What ships with it: 1 file

268 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most ship operate skills give in 551 tokens

Counted across 1,077 of the 1,713 authors here whose files we hold, read 2026-09-06

  • Create GitHub releasein 44 of 1077, across 43 files
  • Run the test suitein 30 of 1077, across 25 files
  • Create and push git tagin 27 of 1077, across 26 files
  • Push commits and tagsin 27 of 1077
  • Create annotated tagin 25 of 1077, across 22 files
  • Ensure working tree is cleanin 24 of 1077
  • Check for product marketing context firstin 23 of 1077, across 6 files
  • Commit version bump changesin 22 of 1077, across 21 files
  • Update CHANGELOG.mdin 21 of 1077, across 20 files
  • Structure launch marketing across three channel typesin 20 of 1077, across 5 files
  • Commit and tag the releasein 20 of 1077, across 18 files
  • Update the CHANGELOG for new releasesin 19 of 1077

Said here and by no other author read

  • Identify target post IDs and exact keys
  • Backup relevant meta before writes
  • Execute scoped updates
  • Flush Elementor CSS and cache artifacts
  • Verify editor load and frontend render

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.