---
name: Elementor Edit Content
description: Playbook for editing Elementor pages via SiteSkite MCP — read environment, fetch document JSON, replace widgets, clear CSS cache.
enable_prompt: true
enable_agentic: true
---

# Elementor content editing (SiteSkite MCP)

Use this skill when the site uses **Elementor** and the user wants page/layout changes handled through MCP.

## Workflow

1. `siteskite_site_context` — confirm Elementor is detected.
2. `siteskite_elementor_get_environment` — version + capabilities.
3. `siteskite_elementor_get_document` with the target post ID — read `_elementor_data` JSON.
4. Plan widget/section changes in valid Elementor document structure.
5. `siteskite_elementor_replace_document` — write the full document JSON (includes CSS cache clear when Elementor API is available).
6. `siteskite_get_post` or re-fetch document to verify.

## Rules

- Prefer typed Elementor abilities over raw `post_content` edits.
- Elementor stores layout in post meta, not in `post_content` alone.
- Replace the **entire** document JSON unless you have a precise partial patch strategy.
- Keep global styles, kits, and theme builder templates in mind — do not overwrite unrelated templates.
- Draft-first: create or update as draft; confirm before publish.
- If Elementor is inactive, stop and tell the user.

## Common pitfalls

- Invalid JSON or missing `elements` root breaks the page — validate structure before replace.
- Missing responsive settings on columns/sections can look wrong on mobile.
- After replace, ask the user to hard-refresh Elementor preview if styles look stale (CSS cache is cleared server-side when possible).
