wordpress-elementor

jezweb/claude-skills · updated Jun 4, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill wordpress-elementor
0 commentsdiscussion
summary

Edit Elementor pages and manage templates on WordPress sites via WP-CLI or browser automation.

  • Choose WP-CLI for safe text and URL replacements within widgets; use browser automation for structural changes, styling, and template application
  • Workflow: identify the page, back up Elementor data, execute edits, flush CSS cache, and verify the live result
  • Supports template duplication, template library management, and page cloning via WP-CLI meta operations
  • Always clear Elementor's CSS
skill.md

WordPress Elementor

Edit Elementor pages and manage templates on existing WordPress sites. Produces updated page content via browser automation (for visual/structural changes) or WP-CLI (for safe text replacements).

Prerequisites

  • Working WP-CLI connection or admin access (use wordpress-setup skill)
  • Elementor installed and active: wp @site plugin status elementor

Workflow

Step 1: Identify the Page

# List Elementor pages
wp @site post list --post_type=page --meta_key=_elementor_edit_mode --meta_value=builder \
  --fields=ID,post_title,post_name,post_status

# Editor URL format: https://example.com/wp-admin/post.php?post={ID}&action=elementor

Step 2: Choose Editing Method

Change Type Method Risk
Text content updates WP-CLI search-replace Low (with backup)
Image URL swaps WP-CLI meta update Low (with backup)
Widget styling Browser automation None
Add/remove sections Browser automation None
Layout changes Browser automation None
Template application Browser automation None

Rule of thumb: If you're only changing text or URLs within existing widgets, WP-CLI is faster. For anything structural, use the visual editor via browser.

Step 3a: Text Updates via WP-CLI

Always back up first:

wp @site post meta get {post_id} _elementor_data > /tmp/elementor-backup-{post_id}.json

Pre-flight checklist:

  1. Back up the postmeta (above)
  2. Dry run the replacement
  3. Verify the dry run matches expectations (correct number of replacements)
  4. Execute
  5. Flush CSS cache
  6. Verify visually

Simple text replacement:

# Dry run
wp @site search-replace "Old Heading Text" "New Heading Text" wp_postmeta \
  --include-columns=meta_value --dry-run --precise

# Execute (after confirming dry run looks correct)
wp @site search-replace "Old Heading Text" "New Heading Text" wp_postmeta \
  --include-columns=meta_value --precise

After updating, clear Elementor's CSS cache:

wp @site elementor flush-css

If the elementor WP-CLI command isn't available:

wp @site option delete _elementor_global_css
wp @site post meta delete-all _elementor_css

What's safe to replace:

Safe Risky
Headings text HTML structure
Paragraph text Widget IDs
Button text and URLs Section/column settings
Image URLs (same dimensions) Layout properties
Phone numbers, emails CSS classes
Addresses Element ordering

Step 3b: Visual Editing via Browser Automation

For structural changes, use browser automation to interact with Elementor's visual editor.

Login flow (skip if already logged in via Chrome MCP):

  1. Navigate to https://example.com/wp-admin/
  2. Enter username and password
  3. Click "Log In"
  4. Wait for dashboard to load

Open the editor:

  1. Navigate to https://example.com/wp-admin/post.php?post={ID}&action=elementor
  2. Wait for Elementor loading overlay to disappear (can take 5-10 seconds)
  3. Editor is ready when the left sidebar shows widget panels

Edit text content:

  1. Click on the text element in the page preview (right panel)
  2. The element becomes selected (blue border)
  3. The left sidebar shows the element's settings
  4. Under "Content" tab, edit the text in the editor field
  5. Changes appear live in the preview
  6. Click "Update" (green button, bottom left) or Ctrl+S

Edit heading:

  1. Click the heading in the preview
  2. Left sidebar > Content tab > "Title" field
  3. Edit the text
  4. Optionally adjust: HTML tag (H1-H6), alignment, link
  5. Save

Change image:

  1. Click the image widget in the preview
  2. Left sidebar > Content tab > click the image thumbnail
  3. Media Library opens
  4. Select new image or upload
  5. Click "Insert Media"
  6. Save

Edit button:

  1. Click the button in the preview
  2. Left sidebar > Content tab: Text (label), Link (URL), Icon (optional)
  3. Style tab: colours, typography, border, padding
  4. Save

Using playwright-cli:

playwright-cli -s=wp-editor open "https://example.com/wp-admin/"
# Login first, then navigate to Elementor editor
playwright-cli -s=wp-editor navigate "https://example.com/wp-admin/post.php?post={ID}&action=elementor"

Or Chrome MCP if using the user's logged-in session.

Step 4: Manage Templates

List saved templates:

wp @site post list --post_type=elementor_library --fields=ID,post_title,post_status

Export a template (browser):

  1. Navigate to: https://example.com/wp-admin/edit.php?post_type=elementor_library
  2. Hover over the template > "Export Template"
  3. Downloads as .json file

Import a template (browser):

  1. Navigate to: https://example.com/wp-admin/edit.php?post_type=elementor_library
  2. Click "Import Templates" at the top
  3. Choose file > upload .json
  4. Template appears in the library

Apply a template to a new page:

  1. Create the page: wp @site post create --post_type=page --post_title="New Page" --post_status=draft
  2. Open in Elementor via browser
  3. Click the folder icon (Add Template)
  4. Select from "My Templates" tab
  5. Click "Insert"
  6. Customise and save

Duplicate an existing page via WP-CLI:

# Get source page's Elementor data
SOURCE_DATA=$(wp @site post meta get {source_id} _elementor_data)
SOURCE_CSS=$(wp @site post meta get {source_id} _elementor_page_settings)

# Create new page
NEW_ID=$(wp @site post create --post_type=page --post_title="Duplicated Page" --post_status=draft --porcelain)

# Copy Elementor data
wp @site post meta update $NEW_ID _elementor_data "$SOURCE_DATA"
wp @site post meta update $NEW_ID _elementor_edit_mode "builder"
wp @site post meta update $NEW_ID _elementor_page_settings "$SOURCE_CSS"

# Regenerate CSS
wp @site elementor flush-css

Apply template between pages via WP-CLI:

# Get source data
SOURCE=$(wp @site post meta get {source_id} _elementor_data)
SETTINGS=$(wp @site post meta get {source_id} _elementor_page_settings)

# Apply to target
wp @site post meta update {target_id} _elementor_data "$SOURCE"
wp @site post meta update {target_id} _elementor_edit_mode "builder"
wp @site post meta update {target_id} _elementor_page_settings "$SETTINGS"

# Clear cache
wp @site elementor flush-css

Step 5: Verify

# Check the page status
wp @site post get {post_id} --fields=ID,post_title,post_status,guid

# Get live URL
wp @site post get {post_id} --field=guid

Take a screenshot to confirm visual changes:

playwright-cli -s=verify open "https://example.com/{page-slug}/"
playwright-cli -s=verify screenshot --filename=page-verify.png
playwright-cli -s=verify close

Critical Patterns

Elementor Data Format

Elementor stores page content as JSON in _elementor_data postmeta. The structure is:

Section > Column > Widget

Each element has an id, elType, widgetType, and settings object. Direct manipulation of this JSON is possible but fragile -- always back up first and prefer search-replace over manual JSON editing.

CSS Cache

After any WP-CLI change to Elementor data, you must flush the CSS cache. Elementor pre-generates CSS from widget settings. Stale cache = visual changes don't appear.

wp @site elementor flush-css
# OR if elementor CLI not available:
wp @site option delete _elementor_global_css
wp @site post meta delete-all _elementor_css

Global Widgets

Global widgets are shared across pages. Editing one updates all instances.

# List global widgets
wp @site post list --post_type=elementor_library --meta_key=_elementor_template_type \
  --meta_value=widget --fields=ID,post_title

Caution: Replacing text in a global widget's data affects every page that uses it.

Elementor Pro vs Free

Feature Free Pro
Basic widgets Yes Yes
Theme Builder No Yes
Custom fonts No Yes
Form widget No Yes
WooCommerce widgets No Yes
Dynamic content No Yes

Theme Builder templates (header, footer, archive) are stored as elementor_library post type with specific meta indicating their display conditions.

Common Elementor WP-CLI Commands

If the Elementor CLI extension is available:

wp @site elementor flush-css          # Clear CSS cache
wp @site elementor library sync       # Sync with template library
wp @site elementor update db          # Update database after version change
how to use wordpress-elementor

How to use wordpress-elementor on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add wordpress-elementor
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill wordpress-elementor

The skills CLI fetches wordpress-elementor from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/wordpress-elementor

Reload or restart Cursor to activate wordpress-elementor. Access the skill through slash commands (e.g., /wordpress-elementor) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.551 reviews
  • Shikha Mishra· Dec 28, 2024

    wordpress-elementor reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yusuf Thomas· Dec 24, 2024

    Useful defaults in wordpress-elementor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aanya Diallo· Dec 16, 2024

    I recommend wordpress-elementor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ama Reddy· Nov 27, 2024

    wordpress-elementor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Nov 19, 2024

    I recommend wordpress-elementor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Aanya Choi· Nov 15, 2024

    Registry listing for wordpress-elementor matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sofia Shah· Nov 7, 2024

    wordpress-elementor reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sofia Thompson· Oct 26, 2024

    Registry listing for wordpress-elementor matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kwame Harris· Oct 18, 2024

    Keeps context tight: wordpress-elementor is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Pratham Ware· Oct 10, 2024

    Useful defaults in wordpress-elementor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 51

1 / 6