{"id":"91da27ff-e26f-4a63-82dc-70fdfe47adb4","entityType":"agent","slug":"clawhub-benkalsky-siteagent-elementor-studio","name":"SiteAgent Elementor Studio","canonicalUrl":"https://www.xpersona.co/agent/clawhub-benkalsky-siteagent-elementor-studio","canonicalPath":"/agent/clawhub-benkalsky-siteagent-elementor-studio","generatedAt":"2026-10-11T14:14:10.044Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T11:08:17.193Z","emptyReason":null},"description":"Helps with WordPress + Elementor work via the elementor-mcp MCP server — building new pages, editing existing ones, inspecting site state, or exploring what's possible. Auto-detects Elementor Pro (native Form, Theme Builder, Loop Grid, Popups, Dynamic Tags, Sticky/Motion vs free-tier workarounds) AND the page engine (classic vs Elementor 4 atomic/V4 — atomic uses add-flexbox/add-atomic-* tools since classic writes don't persist on a V4 page). Detects ACF + Crocoblock/JetEngine for dynamic-data binding (Tier-0; bind ACF via Pro dynamic tags, place Jet widgets via add-widget with runtime-verified types). On atomic (V4) sites, authors the Elementor 4 design system — Global Classes, Variables (design tokens), and per-element Interactions — and recovers from the fork's schema-in-error and governance responses. Asks what the user wants before acting. Use when the user references the Elementor MCP, invokes `/siteagent-elementor-studio`, or runs `mcp__elementor__elementor-mcp-*` tools. Also covers initial install of the MCP Adapter + elementor-mcp plugins, app-password auth wiring, schema-loading discipline, and the widget-vs-HTML decision tree. SKIP for Bricks, Divi, Beaver Builder, or non-Elementor WordPress builds.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17b8qfjfq0g8kveh2g8v1179h83ejwb:siteagent-elementor-studio","sourceUrl":"https://clawhub.ai/benkalsky/siteagent-elementor-studio","homepage":"https://clawhub.ai/benkalsky/skills/siteagent-elementor-studio","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/benkalsky/siteagent-elementor-studio","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/benkalsky/skills/siteagent-elementor-studio","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"SiteAgent Elementor Studio technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T11:08:17.193Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T11:08:17.193Z","emptyReason":null},"stars":null,"forks":null,"downloads":1080,"packageName":null,"latestVersion":"1.7.1","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T11:08:17.124Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T11:08:17.193Z","lastCrawledAt":"2026-10-11T11:08:17.124Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T11:08:17.124Z","lastVerifiedAt":null,"highlights":[{"version":"1.7.1","createdAt":"2026-09-14T23:05:39.989Z","changelog":"siteagent-elementor-studio 1.7.1 - Updated installer to pin and describe the new Digitizers/elementor-mcp fork v1.34.1 (was v1.24.0). - Noted in documentation that the fork now includes a built-in update checker (since v1.28.0), surfacing new GitHub releases in the WordPress Updates screen. - Clarified not to use the fork together with the Premium plugin due to naming conflicts. - Removed redundant documentation file (skill-card.md). - Minor documentation and setup instruction improvements.","fileCount":21,"zipByteSize":88046},{"version":"1.7.0","createdAt":"2026-09-14T22:07:02.039Z","changelog":"siteagent-elementor-studio v1.7.0 - Updated permissions and environment handling for plugin release pinning and integrity verification; now defaults to a kit-pinned plugin version and requires digests for all downloads. - Improved setup script and documentation to clarify local vs remote path handling and override behavior for EMCP_PIN_VERSION. - Removed the obsolete skill-card.md file for simplification. - Minor clarification and restructuring of descriptions around allowed shell/network/filesystem/env actions.","fileCount":21,"zipByteSize":86177},{"version":"1.6.1","createdAt":"2026-09-14T21:14:36.629Z","changelog":"siteagent-elementor-studio 1.6.1 - Minor documentation and skill metadata updates in SKILL.md. - Removed redundant or outdated file: skill-card.md. - No functional or user-facing changes in the code or setup scripts.","fileCount":21,"zipByteSize":84644},{"version":"1.6.0","createdAt":"2026-09-13T16:20:52.331Z","changelog":"siteagent-elementor-studio v1.6.0 - Updated documentation in SKILL.md to reflect recent clarifications and protocol improvements. - Removed obsolete skill-card.md file. - Minor script or setup updates in setup-elementor-mcp.sh. - No changes to user-facing features or core functionality.","fileCount":21,"zipByteSize":84668},{"version":"1.5.0","createdAt":"2026-09-13T02:26:59.985Z","changelog":"**Security and setup improvements for siteagent-elementor-studio 1.5.0** - Verifies the downloaded plugin zip against a sha256 digest (from the GitHub release API or supplied via EMCP_EXPECTED_SHA256 env) before unpacking or installing. - Refuses plaintext HTTP connections to non-local hosts unless explicitly allowed via the new WP_ALLOW_HTTP environment variable. - Sets .mcp.json file permissions to mode 600 before writing WordPress credentials. - Updated documentation to describe new security parameters and environment variable usage. - Removed the obsolete skill-card.md file.","fileCount":21,"zipByteSize":81267},{"version":"1.4.0","createdAt":"2026-09-12T22:48:15.665Z","changelog":"**Improved setup detection, configuration, and documentation flow.** - Enhanced first-session setup: now detects and handles placeholder `.mcp.json` configs, with clear instructions for both environment-variable-based setup and interactive script-based setup. - Updated SKILL.md to clarify how to locate and run the setup script, supporting installations from the skill directory when possible, with fallback guidance if missing. - Expanded setup guidance on running in directory contexts with tracked placeholder configs versus per-site config, helping users avoid credential leakage and misconfiguration. - Improved documentation for edge-case setup states and failure modes. - Removed obsolete or redundant documentation files, including `skill-card.md`.","fileCount":21,"zipByteSize":74352},{"version":"1.3.2","createdAt":"2026-07-08T16:07:56.204Z","changelog":"**siteagent-elementor-studio v1.3.2** - Updated documentation to clarify that the built-in MCP engine is now v1.24.0 (up to 118 tools, Elementor 4.x-correct). - Clarified Pro vs Free server detection: using the tool presence check is now emphasized as the definitive signal; notes added on the reliability of detect-elementor-version. - Removed references to a prior MCP server schema bug (now fixed) and improved instructions accordingly. - Minor clarifications and updates to setup instructions and conventions for first-time sessions.","fileCount":21,"zipByteSize":71798},{"version":"1.3.0","createdAt":"2026-07-08T10:48:20.912Z","changelog":"**Expanded Elementor 4 (atomic/V4) support and error recovery.** - Adds authoring capabilities for the Elementor 4 design system: Global Classes, Variables (design tokens), and Interactions on atomic sites. - Introduces error recovery instructions for fork-specific schema and governance issues on atomic/V4. - Adds references for CRUD in the atomic design system, error recovery patterns, and guidance for migrating from v3 to v4. - Documentation updates: describes expanded atomic engine capabilities and clarifies action flows on atomic sites.","fileCount":21,"zipByteSize":70854}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17b8qfjfq0g8kveh2g8v1179h83ejwb:siteagent-elementor-studio","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17b8qfjfq0g8kveh2g8v1179h83ejwb:siteagent-elementor-studio` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/benkalsky/siteagent-elementor-studio before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T14:14:10.038Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-benkalsky-siteagent-elementor-studio/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T11:08:17.193Z","emptyReason":null},"readme":"Skill: SiteAgent Elementor Studio\n\nOwner: benkalsky\n\nSummary: Helps with WordPress + Elementor work via the elementor-mcp MCP server — building new pages, editing existing ones, inspecting site state, or exploring what's possible. Auto-detects Elementor Pro (native Form, Theme Builder, Loop Grid, Popups, Dynamic Tags, Sticky/Motion vs free-tier workarounds) AND the page engine (classic vs Elementor 4 atomic/V4 — atomic uses add-flexbox/add-atomic-* tools since classic writes don't persist on a V4 page). Detects ACF + Crocoblock/JetEngine for dynamic-data binding (Tier-0; bind ACF via Pro dynamic tags, place Jet widgets via add-widget with runtime-verified types). On atomic (V4) sites, authors the Elementor 4 design system — Global Classes, Variables (design tokens), and per-element Interactions — and recovers from the fork's schema-in-error and governance responses. Asks what the user wants before acting. Use when the user references the Elementor MCP, invokes `/siteagent-elementor-studio`, or runs `mcp__elementor__elementor-mcp-*` tools. Also covers initial install of the MCP Adapter + elementor-mcp plugins, app-password auth wiring, schema-loading discipline, and the widget-vs-HTML decision tree. SKIP for Bricks, Divi, Beaver Builder, or non-Elementor WordPress builds.\n\nTags: latest:1.7.1\n\nVersion history:\n\nv1.7.1 | 2026-09-14T23:05:39.989Z | auto\n\nsiteagent-elementor-studio 1.7.1\n\n- Updated installer to pin and describe the new Digitizers/elementor-mcp fork v1.34.1 (was v1.24.0).\n- Noted in documentation that the fork now includes a built-in update checker (since v1.28.0), surfacing new GitHub releases in the WordPress Updates screen.\n- Clarified not to use the fork together with the Premium plugin due to naming conflicts.\n- Removed redundant documentation file (skill-card.md).\n- Minor documentation and setup instruction improvements.\n\nv1.7.0 | 2026-09-14T22:07:02.039Z | auto\n\nsiteagent-elementor-studio v1.7.0\n\n- Updated permissions and environment handling for plugin release pinning and integrity verification; now defaults to a kit-pinned plugin version and requires digests for all downloads.\n- Improved setup script and documentation to clarify local vs remote path handling and override behavior for EMCP_PIN_VERSION.\n- Removed the obsolete skill-card.md file for simplification.\n- Minor clarification and restructuring of descriptions around allowed shell/network/filesystem/env actions.\n\nv1.6.1 | 2026-09-14T21:14:36.629Z | auto\n\nsiteagent-elementor-studio 1.6.1\n\n- Minor documentation and skill metadata updates in SKILL.md.\n- Removed redundant or outdated file: skill-card.md.\n- No functional or user-facing changes in the code or setup scripts.\n\nv1.6.0 | 2026-09-13T16:20:52.331Z | auto\n\nsiteagent-elementor-studio v1.6.0\n\n- Updated documentation in SKILL.md to reflect recent clarifications and protocol improvements.\n- Removed obsolete skill-card.md file.\n- Minor script or setup updates in setup-elementor-mcp.sh.\n- No changes to user-facing features or core functionality.\n\nv1.5.0 | 2026-09-13T02:26:59.985Z | auto\n\n**Security and setup improvements for siteagent-elementor-studio 1.5.0**\n\n- Verifies the downloaded plugin zip against a sha256 digest (from the GitHub release API or supplied via EMCP_EXPECTED_SHA256 env) before unpacking or installing.\n- Refuses plaintext HTTP connections to non-local hosts unless explicitly allowed via the new WP_ALLOW_HTTP environment variable.\n- Sets .mcp.json file permissions to mode 600 before writing WordPress credentials.\n- Updated documentation to describe new security parameters and environment variable usage.\n- Removed the obsolete skill-card.md file.\n\nv1.4.0 | 2026-09-12T22:48:15.665Z | auto\n\n**Improved setup detection, configuration, and documentation flow.**\n\n- Enhanced first-session setup: now detects and handles placeholder `.mcp.json` configs, with clear instructions for both environment-variable-based setup and interactive script-based setup.\n- Updated SKILL.md to clarify how to locate and run the setup script, supporting installations from the skill directory when possible, with fallback guidance if missing.\n- Expanded setup guidance on running in directory contexts with tracked placeholder configs versus per-site config, helping users avoid credential leakage and misconfiguration.\n- Improved documentation for edge-case setup states and failure modes.\n- Removed obsolete or redundant documentation files, including `skill-card.md`.\n\nv1.3.2 | 2026-07-08T16:07:56.204Z | auto\n\n**siteagent-elementor-studio v1.3.2**\n\n- Updated documentation to clarify that the built-in MCP engine is now v1.24.0 (up to 118 tools, Elementor 4.x-correct).\n- Clarified Pro vs Free server detection: using the tool presence check is now emphasized as the definitive signal; notes added on the reliability of detect-elementor-version.\n- Removed references to a prior MCP server schema bug (now fixed) and improved instructions accordingly.\n- Minor clarifications and updates to setup instructions and conventions for first-time sessions.\n\nv1.3.0 | 2026-07-08T10:48:20.912Z | auto\n\n**Expanded Elementor 4 (atomic/V4) support and error recovery.**\n\n- Adds authoring capabilities for the Elementor 4 design system: Global Classes, Variables (design tokens), and Interactions on atomic sites.\n- Introduces error recovery instructions for fork-specific schema and governance issues on atomic/V4.\n- Adds references for CRUD in the atomic design system, error recovery patterns, and guidance for migrating from v3 to v4.\n- Documentation updates: describes expanded atomic engine capabilities and clarifies action flows on atomic sites.\n\nv1.2.1 | 2026-07-07T22:40:48.509Z | auto\n\n**Minor update with documentation and naming improvements.**\n\n- Updated documentation in SKILL.md for clarity and detail.\n- Clarified the initial working protocol and user prompt behavior.\n- Improved references to skill naming to consistently use \"SiteAgent Elementor Studio.\"\n- No functional or code changes, just documentation and descriptive updates.\n\nv1.2.0 | 2026-07-07T21:44:52.356Z | auto\n\nsiteagent-elementor-studio v1.2.0\n\n- Renamed skill and all mentions from \"elementor-pro-studio\" to \"siteagent-elementor-studio\"\n- Updated SKILL.md and invocation instructions to use the new skill name (including CLI and menu prompts)\n- Removed outdated skill-card.md\n- No changes to core protocols, permissions, or setup flow\n\nv1.1.2 | 2026-07-03T23:11:05.776Z | auto\n\n**elementor-pro-studio 1.1.2**\n\n- Added explicit skill permissions to SKILL.md, clarifying shell, network, filesystem, and environment variable usage.\n- Updated setup instructions: the setup script (`setup-elementor-mcp.sh`) is now offered only after explicit user confirmation and is never run automatically.\n- Removed the redundant `skill-card.md` file.\n- Various minor documentation clarifications in SKILL.md regarding when and how script and shell actions are triggered.\n\nv1.1.1 | 2026-07-03T21:19:49.535Z | auto\n\nelementor-pro-studio v1.1.1\n\n- Documentation updated: project link for the `elementor-mcp` server now points to the `Digitizers/elementor-mcp` fork, reflecting correct upstream and version compatibility.\n- Minor clarifications in setup instructions and references for improved accuracy.\n\nv1.1.0 | 2026-07-03T20:38:29.564Z | auto\n\n**Major update with improved detection, user flow, and setup guidance**\n\n- Added auto-detection for Elementor Pro, engine type (classic vs atomic/V4), and third-party integrations (ACF, Crocoblock/JetEngine).\n- Introduced a strict \"ask before doing\" protocol; skill now presents a menu and waits for user input before any write or destructive action.\n- Outlined safe read-only actions (list pages, get global settings) permitted prior to user selection.\n- Documented first-session setup instructions, including plugin installation script, for both local and live WordPress hosts.\n- Included clear branching based on detected Pro/free and engine type; skill adapts responses and tool usage accordingly.\n- Expanded documentation to cover best practices, integration checks, and troubleshooting common setup issues.\n\nArchive index:\n\nArchive v1.7.1: 21 files, 88046 bytes\n\nFiles: references/atomic-v4.md (9593b), references/brand-kit.md (3625b), references/design-system-crud.md (9059b), references/dynamic-data.md (3406b), references/engine-and-premium.md (7497b), references/error-recovery.md (7340b), references/forms.md (8624b), references/header-footer.md (3947b), references/lifecycle.md (1805b), references/pro-widgets.md (3128b), references/recipes.md (11027b), references/v3-to-v4-conversion.md (7250b), references/verticals/car-wash.md (2617b), references/verticals/dental.md (2832b), references/verticals/local-business.md (2647b), references/verticals/portfolio.md (2701b), references/verticals/salon.md (2527b), setup-elementor-mcp.sh (72430b), skill-card.md (3082b), SKILL.md (41569b), _meta.json (145b)\n\nFile v1.7.1:SKILL.md\n\n---\nname: siteagent-elementor-studio\nversion: 1.7.1\nlicense: MIT\ndescription: Helps with WordPress + Elementor work via the elementor-mcp MCP server — building new pages, editing existing ones, inspecting site state, or exploring what's possible. Auto-detects Elementor Pro (native Form, Theme Builder, Loop Grid, Popups, Dynamic Tags, Sticky/Motion vs free-tier workarounds) AND the page engine (classic vs Elementor 4 atomic/V4 — atomic uses add-flexbox/add-atomic-* tools since classic writes don't persist on a V4 page). Detects ACF + Crocoblock/JetEngine for dynamic-data binding (Tier-0; bind ACF via Pro dynamic tags, place Jet widgets via add-widget with runtime-verified types). On atomic (V4) sites, authors the Elementor 4 design system — Global Classes, Variables (design tokens), and per-element Interactions — and recovers from the fork's schema-in-error and governance responses. Asks what the user wants before acting. Use when the user references the Elementor MCP, invokes `/siteagent-elementor-studio`, or runs `mcp__elementor__elementor-mcp-*` tools. Also covers initial install of the MCP Adapter + elementor-mcp plugins, app-password auth wiring, schema-loading discipline, and the widget-vs-HTML decision tree. SKIP for Bricks, Divi, Beaver Builder, or non-Elementor WordPress builds.\npermissions:\n shell: \"Runs the bundled setup script (files/setup-elementor-mcp.sh) — only on explicit user confirmation. It shells out to curl/unzip/zip/python3 and, for Local sites, drives Local by Flywheel's bundled WP-CLI (plugin install/activate) against the running site's PHP + MySQL socket.\"\n network:\n - \"GitHub release download over HTTPS from the trusted Digitizers/elementor-mcp repo (api.github.com + release asset host) — the elementor-mcp plugin zip. By default the release this kit pins (EMCP_DEFAULT_VERSION in the setup script), checked before it is unpacked or installed against the sha256 recorded beside the pin — out of band from the download. EMCP_PIN_VERSION= or =latest selects another release, checked against the digest that release publishes (integrity, not provenance) or EMCP_EXPECTED_SHA256. Nothing is installed unverified\"\n - \"The target WordPress site's REST API (/wp-json/ — auth check, plugin list/install, MCP route verification). Plaintext http:// is refused for a non-local host unless that exact host is named in WP_ALLOW_HTTP, because the run sends a reusable application password on every request\"\n filesystem:\n - \"Writes .mcp.json in the current working directory, created mode 600 before the credential is written (it embeds a reusable Basic-Auth WordPress credential), and appends .mcp.json to .gitignore there\"\n - \"Reads Local by Flywheel site paths + bundled WP-CLI/PHP binaries; creates a temp working dir for the plugin zip\"\n env:\n - \"WP_URL / WP_USERNAME / WP_APP_PASSWORD (when used to supply the target site + Application Password auth)\"\n - \"EMCP_PIN_VERSION (optional — a release tag, or latest, instead of the release this kit pins; the kit's pin never downgrades an installed newer plugin — the run stops and names this override)\"\n - \"EMCP_EXPECTED_SHA256 (optional — verify the plugin zip against a digest obtained out of band; required for a release that publishes no digest)\"\n - \"WP_ALLOW_HTTP (comma-separated host list — permits plaintext http for exactly those hosts; a blanket value is not a hostname and permits nothing)\"\n---\n\n# SiteAgent Elementor Studio Skill\n\nYou are operating against a WordPress site with the **elementor-mcp** server (`https://github.com/Digitizers/elementor-mcp` — our fork, Elementor 4.x-correct) connected via the WordPress MCP Adapter. This skill captures everything I learned the hard way the first time through, so subsequent sessions start at expertise level.\n\n## 🛑 First Action Protocol — ASK BEFORE DOING\n\n**When this skill is invoked, do not start running tools. Ask the user what they want first.**\n\n> **Shell / setup actions run only on explicit user confirmation.** The bundled `setup-elementor-mcp.sh` (which shells out, runs Local's WP-CLI, downloads the plugin, and writes a credentialed `.mcp.json`) is never run automatically — offer it and wait for the user to say yes.\n\nIf the user's invocation message *already* contains a clear task — *\"build me a hero section from `index.html`\"*, *\"show me my current global colors\"*, *\"change the burgundy to navy\"* — proceed with that task directly.\n\nOtherwise *(invocations like `/siteagent-elementor-studio` alone, or \"use the Elementor MCP\" with no follow-up)*, **respond with this menu and wait for the user to pick:**\n\n```\nWhat would you like to do with your Elementor site?\n\n 1. Build — create new pages or sections from a design\n 2. Edit — change something on an existing page\n 3. Reference — inspect current state (pages, colors, fonts, content)\n 4. Explore — show me what's possible / what can the MCP do here\n```\n\nDo **not** silently default to \"build\" — that's the most destructive action and forces a path the user may not want. Wait for the user to choose 1/2/3/4 *(or describe their task in their own words)* before invoking any MCP tool other than the harmless read-only ones at the bottom of this section.\n\n### Read-only \"smoke test\" calls that are always safe to run\n\nWhen the user picks any option, you can run these **before** asking follow-up questions, since they help frame the next response:\n\n- `mcp__elementor__elementor-mcp-list-pages` — confirms auth + lists what's there\n- `mcp__elementor__elementor-mcp-get-global-settings` — current colors/fonts kit\n\nThat's it for unprompted tool calls. **Anything that creates, modifies, or deletes data requires the user to have explicitly asked for it.**\n\n## When this skill applies\n\n- The user mentions Elementor MCP, types `/siteagent-elementor-studio`, or says \"use the Elementor MCP\"\n- A `.mcp.json` in the project registers an MCP server pointing at `wp-json/mcp/elementor-mcp-server`\n- The user asks to build, edit, inspect, or troubleshoot an Elementor page\n- Tools beginning with `mcp__elementor__elementor-mcp-*` are available\n\n## First-session setup (when MCP not yet connected)\n\n> **Engine:** this skill drives our fork `Digitizers/elementor-mcp` (v1.34.1, the release this kit's installer pins; Elementor 4.x-correct), a single self-contained plugin — no Freemius, no phone-home. Since fork v1.28.0 it carries its own update checker, which **offers** later GitHub Releases on the site's normal Updates screens (release-only, a user agent naming only the plugin); installing one is WordPress's ordinary update flow, and the fork does not switch on WordPress's per-plugin auto-update. **Never run it alongside the paid \"MCP Tools for Elementor (Premium)\" — same class names → fatal.** Details + switch commands → `references/engine-and-premium.md`.\n\nIf the user has a WordPress site but no **working** `elementor` MCP connection — either no `.mcp.json` at all, or only this kit's committed placeholder config (values like `\"WP_URL\": \"${WP_URL:-}\"` with those env vars unset) and no `mcp__elementor__elementor-mcp-*` tools loaded:\n\n> In the placeholder case there are two fixes, not one: **export `WP_URL` / `WP_USERNAME` / `WP_APP_PASSWORD`** (the committed config reads them — fastest in this repo's checkout or a cloud session), or run the wizard below from a **separate per-site project directory** (it refuses to write credentials into the tracked placeholder file).\n\n1. **Check whether they're using Local-by-Flywheel or a live host.** Setup paths differ.\n2. **Run the bundled setup script** from the loaded skill's directory — it handles plugin install, auth wiring, and `.mcp.json` generation interactively for both flavors. The skill's base directory is announced when this skill loads (look for the filesystem path in the skill load message). Replace `` with that announced path:\n ```bash\n bash \"/setup-elementor-mcp.sh\"\n ```\n Keep the quotes — plugin-cache paths can contain spaces (e.g. a Windows\n profile named `First Last`), and an unquoted substitution splits the path.\n **If `/setup-elementor-mcp.sh` is not found** (e.g., from a manual `INSTALL.sh` run instead of plugin-marketplace), use the fallback path for manual installations:\n ```bash\n bash ~/.claude/scripts/setup-elementor-mcp.sh\n ```\n3. After the script completes, instruct the user to **quit and reopen Claude Code in the project directory** so the new `.mcp.json` is picked up.\n4. On reopen, the deferred MCP tools will be exposed via ToolSearch — load the ones you need with `select:` queries.\n\nIf something fails, see \"Setup gotchas\" below.\n\n## Working session conventions\n\n### Always do this first\n\n```\nmcp__elementor__elementor-mcp-list-pages # confirms auth + lists existing pages\nmcp__elementor__elementor-mcp-get-global-settings # see existing colors/fonts kit\nmcp__elementor__elementor-mcp-get-container-schema # ground truth on flex_* key names\n```\n\n### 🎯 Detect Pro vs Free FIRST — it changes which path you take\n\nBefore building anything, determine whether **Elementor Pro** is active. The\nwhole skill branches on this: with Pro you use native widgets (Form, Theme\nBuilder, Loop Grid, Popups, Dynamic Tags, Sticky/Motion); without it you use the\nfree-tier workarounds documented further down (Fluent Forms, UAE/HFE, HTML for\nmotion).\n\n**How to detect — by tool availability (the definitive Pro signal):**\n\nThe elementor-mcp server exposes Pro tools **conditionally**. When Pro is active\nthe tool list grows from ~74 to ~100+ tools and Pro-only tools appear. Check\nwhether these exist in your available `mcp__elementor__elementor-mcp-*` tools:\n\n- `add-form` — present ⇒ **Pro active**\n- `create-theme-template` — present ⇒ **Pro active**\n- `add-loop-grid` / `add-loop-carousel` — present ⇒ **Pro active**\n- `create-popup`, `set-dynamic-tag` — present ⇒ **Pro active**\n\nIf none of those Pro tools are exposed, treat the site as **Free** and use the\nworkarounds. The **tool-presence check above is the definitive Pro-vs-Free\nsignal** — prefer it. (`detect-elementor-version` is reliable on current builds —\nthe old v1.5.0 schema bug is fixed — but it reports **atomic/version** support,\nnot a Pro flag, so it doesn't settle Pro-vs-Free on its own.)\n\n> **Record the verdict once** (\"Pro detected\" / \"Free only\") and state it to the\n> user up front, then follow the matching branch in every section below. Each\n> \"Forms\", \"Header/Footer\", and motion section is written as **If Pro → … /\n> If Free → …**. Don't mix paths.\n\n### 🧬 Also detect the ENGINE — classic vs atomic (Elementor 4 / V4)\n\nThere's a **second** axis that changes everything: the page engine. Elementor 4\nintroduced the **atomic / V4** engine (`e-flexbox`, `e-div-block`, atomic\nwidgets, a typed-prop `$$type` data model). Classic widget writes **do not\npersist on an atomic page** — they silently appear to do nothing. So before\nbuilding, decide classic vs atomic.\n\n**How to detect — by atomic tool availability (preferred):**\n\nThe atomic tools register only when the site is on the atomic engine. Check your\navailable tools:\n\n- `add-flexbox`, `add-div-block`, `add-atomic-heading` / `add-atomic-button` / …,\n `add-atomic-widget` / `update-atomic-widget` present ⇒ **atomic (V4) engine**\n- Only classic `add-container` / `add-heading` / … present ⇒ **classic engine**\n\nYou may also call `detect-elementor-version` (reliable on current releases — it\nreturns whether atomic is supported). The old v1.5.0 schema bug is fixed; still,\ntool-presence is the most direct signal.\n\n> **Which elementor-mcp PLUGIN version am I on?** Some behaviour below branches on\n> it, and `detect-elementor-version` answers about *Elementor*, not the plugin.\n> Call **`server-info`**: it returns `plugin_version` (plus registered-vs-exposed\n> tool counts and what is withholding the rest). It is always registered and\n> cannot be disabled, so **its absence is itself the answer** — no `server-info`\n> means the site is on **1.28.0 or older**. Use it for the one branch that needs it —\n> whether `update-atomic-widget` can restyle in place (1.28.1+). Nothing else should\n> depend on the version: for the universal atomic tools, pass raw `$$type` values, which\n> are correct on every build.\n\n> ⚠️ **Antigravity / tight tool caps.** Antigravity caps MCP tools at ~100. The\n> full Pro+atomic set is ~113, so atomic tools can get truncated and never reach\n> the client — making a V4 site look like \"writes don't persist\". Fix: enable the\n> MCP plugin's **Low-tools mode** (WP Admin → MCP Tools screen). Its curated\n> essentials set **includes the 5 atomic essentials** (`detect-elementor-version`,\n> `add-atomic-widget`, `update-atomic-widget`, `add-flexbox`, `add-div-block`) and\n> stays under the cap.\n\n> 🐞 **Known root cause (older MCP builds).** Elementor often runs atomic as an\n> opt-in *experiment* while `ELEMENTOR_VERSION` still reads `3.x`. MCP builds that\n> gate atomic on `version_compare(ELEMENTOR_VERSION,'4.0.0','>=')` therefore never\n> register the atomic tools on those sites. Fixed upstream by detecting via the\n> experiment/module. If atomic tools are missing on a clearly-V4 site, update the\n> elementor-mcp plugin (or confirm the V4 experiment is on under Elementor →\n> Settings → Features).\n\nRecord **both** axes: e.g. \"Pro + atomic\", \"Pro + classic\", \"Free + classic\".\nThe Pro/Free axis picks Form vs Fluent Forms etc.; the engine axis picks classic\nvs atomic widget tools (next section).\n\nThe container schema is large (~50KB). Read it once, then write down the keys you'll use in your reply text so you don't need to re-fetch it. Critical keys:\n\n- `flex_direction`, `flex_justify_content`, `flex_align_items`, `flex_gap`, `flex_wrap` — note the **`flex_` prefix** on justify/align (issue #32 was about these being written under wrong keys in older versions)\n- `content_width: \"boxed\"|\"full\"` + `boxed_width: {unit, size, sizes}`\n- `min_height: {unit, size, sizes}` — use unit `vh` for full-screen heroes\n- `padding`/`margin: {unit, top, right, bottom, left, isLinked}` — `isLinked: false` when sides differ\n- `background_background: \"classic\"|\"gradient\"|\"video\"` — must be set first or other background_* keys are ignored\n- `background_overlay_*` — separate parallel set for overlays. `background_overlay_opacity: {unit:\"px\", size: 0.5}` (yes, the unit is `px` even for opacity — quirk of the schema)\n\n### Widget call convention — flat params, NOT nested in `settings`\n\nThis bit me hard the first time. The `add-*` shortcut tools take their settings as **top-level parameters**, not inside a `settings: {}` object:\n\n```js\n// ✓ CORRECT\nmcp__elementor__elementor-mcp-add-heading({\n post_id: 11,\n parent_id: \"abc123\",\n title: \"where estates are entrusted\",\n header_size: \"h1\",\n title_color: \"#FFFFFF\",\n typography_typography: \"custom\", // ← required to enable typography\n typography_font_family: \"Cormorant Garamond\",\n typography_font_size: {size: 110, unit: \"px\"},\n typography_font_weight: \"300\",\n typography_line_height: {size: 0.98, unit: \"em\"},\n})\n\n// ✗ WRONG — silently fails or returns \"title is required\"\nmcp__elementor__elementor-mcp-add-heading({\n post_id: 11,\n parent_id: \"abc123\",\n settings: {title: \"...\", typography_font_family: \"...\"}\n})\n```\n\n`add-container` is the **exception** — it takes a `settings: {}` object. Don't generalize from one to the other.\n\n### Always set `typography_typography: \"custom\"`\n\nWithout this, the other typography_* keys are ignored. Same applies to `css_filters_css_filter: \"custom\"` for image filters, etc. — these \"enable\" flags are how Elementor knows you want to override defaults.\n\n### Italic emphasis pattern\n\nDisplay headings often need a single italic-emphasized word. Don't use a separate widget — just inline `` in the title:\n\n```js\ntitle: \"A quiet practice for an uncommon clientele.\"\n```\n\nCormorant Garamond and most luxury serifs have italic variants that auto-load when `` appears. Confirm via the rendered page; if italics fail, the global typography needs the italic variant explicitly enabled.\n\n### Responsive values — suffix keys (classic) vs. variants (atomic)\n\nElementor stores a responsive control's per-breakpoint values under **suffixed keys**.\nThe base (desktop) value has **no suffix**; each breakpoint appends its own suffix to the\n**same base control key**, with the **same value shape** as desktop:\n\n```js\n// classic widget — tablet/mobile overrides of the same control:\nmcp__elementor__elementor-mcp-add-heading({\n post_id, parent_id,\n title: \"...\",\n typography_font_size: {size: 110, unit: \"px\"}, // desktop (base, no suffix)\n typography_font_size_tablet: {size: 72, unit: \"px\"}, // tablet\n typography_font_size_mobile: {size: 44, unit: \"px\"}, // mobile\n align: \"left\", align_tablet: \"center\", // alignment per breakpoint\n})\n```\n\n**The suffix set is breakpoint-dependent — do NOT hardcode an incomplete list.** It\nderives from Elementor's **active breakpoints** (`add_responsive_control()`), so beyond\n`_tablet` / `_mobile` a site may expose `_widescreen`, `_laptop`, `_tablet_extra`,\n`_mobile_extra`, or custom ones. Read the site's breakpoints rather than assuming; the\nfork passes any `_` key through as long as `` is a real control.\n\n> **Atomic (V4) is different — no suffix keys.** On a V4 page responsive lives in a style\n> definition's **`variants` array**, keyed by a `breakpoint` meta (`desktop` = base, then\n> `tablet`/`mobile`/custom) — Global Classes take a `variants` param, local styles add\n> variant entries. Never put `_tablet`/`_mobile` suffix keys on atomic elements. See\n> `references/atomic-v4.md` and `references/design-system-crud.md`.\n\n## The widget-vs-HTML decision — DEFAULT TO NATIVE WIDGETS\n\n> 🚨 **CRITICAL ANTI-PATTERN — read this first.**\n>\n> **Do NOT paste an entire HTML page into one HTML widget.** Do NOT build a homepage that is \"1 container with 3 HTML widgets inside.\" That is not building with Elementor — that is using Elementor as a wrapper around a static webpage. The user **cannot edit it** in the Elementor visual editor, **cannot reuse the design tokens**, and **cannot iterate** on it without going back to source code.\n>\n> If you find yourself thinking *\"I'll just dump this section as HTML, it's faster,\"* **STOP.** Break it into native widgets.\n\n### Always default to native widgets\n\nFor every section the user wants, build it from native Elementor widgets:\n\n- **Headings** → `add-heading` widget *(supports inline `` for italic emphasis)*\n- **Body copy** → `add-text-editor` widget\n- **Images** → `add-image` widget *(NOT an `` tag inside an HTML widget)*\n- **Buttons / CTAs** → `add-button` widget *(NOT an `` styled as a button)*\n- **Layout / spacing** → `add-container` with proper `flex_*` settings *(NOT `
`s with CSS flex)*\n- **Lists** → `add-icon-list` widget\n- **Tabs** → `add-tabs` widget\n- **Accordions / FAQs** → `add-accordion` widget\n- **Forms** → Fluent Forms shortcode via `add-shortcode` widget\n- **Nav menu in headers** → UAE Nav Menu widget *(`uael-nav-menu`)*\n\n### When HTML widget IS allowed *(narrow list — exceptions only)*\n\nOnly reach for an HTML widget in these specific cases. **Anything not on this list goes through native widgets.**\n\n1. **Tab/accordion content with rich layout.** `add-tabs` only accepts `tab_content` as a string of HTML, so a multi-card grid inside a tab MUST be HTML. *(But the wrapping Tabs widget itself is still native.)*\n2. **Decorative-only flourishes** with no native equivalent — a thin gold rule with a CSS-pseudo-element flourish, an animated underline that grows on hover, a gradient overlay on a child element. **Even then, prefer to pair it with a native widget rather than replacing one.**\n3. **Form HTML as a flagged placeholder** when no real form plugin is wired up yet — and you must explicitly tell the user \"form is visual only, doesn't capture submissions.\"\n4. **Site-wide CSS overrides** scoped to a specific Elementor element ID *(e.g., styling the tab strip of an `add-tabs` widget that the widget controls don't expose)*. These should be small style blocks, not whole sections of markup.\n\n### What about card grids of 4+ items?\n\nEarlier versions of this skill said \"use one HTML widget for card grids — it's faster than 50 widget calls.\" That advice was wrong because it led to non-editable pages.\n\n**The correct path for card grids:**\n\n- Build the first card with native widgets *(Container → Image → Heading → Text Editor → Button)*\n- Use `duplicate-element` to copy it 3+ more times\n- Use `update-element` to change the copy/image on each duplicate\n- Wrap them in a parent Container with `flex_direction: row` and `flex_wrap: wrap`\n\nThis is more widget calls, yes, but the result is a **real Elementor card grid** the user can edit, restyle globally, or reuse as a template.\n\n> **If Pro is active and the cards are driven by posts/CPT/products** (a blog feed, portfolio, listings), prefer the native **Loop Grid** (`add-loop-grid`) instead — see the Loop Grid section below. The duplicate-element pattern is still the right answer for a fixed set of bespoke, non-dynamic cards on either tier.\n\n### Cross-widget styling — `\n```\n\nThe `f8d1545` is the `element_id` returned when you created the tabs widget. Always grab and remember these IDs — they're the only stable selector across page reloads.\n\n> ⚠️ **An HTML widget used for cross-widget styling MUST contain only `\n```\n\nThe `f8d1545` is the `element_id` returned when you created the tabs widget. Always grab and remember these IDs — they're the only stable selector across page reloads.\n\n> ⚠️ **An HTML widget used for cross-widget styling MUST contain only `