build-elementor-page

build-elementor-page is a skill for Claude Code from respira-press/agent-skills-wordpress. It costs 84 tokens per session (2,031 once invoked), scanned A, original, MIT.

A recipe for building pages in Elementor, a WordPress page builder, from a brief, screenshot, or mockup. It translates the design into Elementor's own settings rather than relying on a separate stylesheet.

In plain words
What is it for?
Use it to create an Elementor page when there is no finished HTML file and every style should remain editable in Elementor. It also covers templates, computed design values, responsive layouts, and checking the result.
Why use it?
It addresses the common mismatch between a design and an Elementor page when theme defaults or missing widget settings change the appearance. It provides a structured way to account for layout, styles, spacing, buttons, and mobile views.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the respira-wordpress-skills plugin — 56 skills shipped together

Good fit Use it to create an Elementor page when there is no finished HTML file and every style should remain editable in Elementor. It also covers templates, computed design values, responsive layouts, and checking the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/respira-press/agent-skills-wordpress/build-elementor-page
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add respira-press/agent-skills-wordpress --skill build-elementor-page
Clone the repo
git clone --depth 1 https://github.com/respira-press/agent-skills-wordpress

Made for: Claude Code.

Or install respira-wordpress-skills, the plugin that ships this one along with the rest of its 56 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for build-elementor-page

README.md
[![agentmods](https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/build-elementor-page/github.svg)](https://agentmods.dev/skills/respira-press/agent-skills-wordpress/build-elementor-page)
Your own site
<a href="https://agentmods.dev/skills/respira-press/agent-skills-wordpress/build-elementor-page"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/build-elementor-page/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for build-elementor-page

Your own site · 80×15
<a href="https://agentmods.dev/skills/respira-press/agent-skills-wordpress/build-elementor-page"><img src="https://agentmods.dev/badge/skills/respira-press/agent-skills-wordpress/build-elementor-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,031 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.02031
Opus 5.5 $0.00034 $0.00812
Sonnet 5.5 $0.00017 $0.00406
Haiku 4.5 $0.00008 $0.00203

Measured 2d ago against content hash 2f9cf4da94f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-elementor-page scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/build-elementor-page/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build an Elementor page

Version: 1.1.0 Updated: 2026-10-04 Category: workflow Status: stable Requires: Respira for WordPress plugin (9.1+) and an MCP connection, on a site running Elementor


Description

A recipe for building an Elementor page through respira_build_page that looks like the design the first time. Elementor writes every style into the widget that shows it. Nothing cascades from the page the way CSS does, so whatever a widget's settings leave out comes from the theme or the Elementor kit: the theme's body size, the kit's heading colour, a default line height. Most of the distance between a hand-built page and its design comes from those gaps, not from the layout.

Have the finished HTML? Use the html-to-page skill. One respira_convert_html_to_builder call writes the page as native Elementor widgets and carries the file's stylesheet, so it matches the file without restating anything. Build by hand when there is no file, or when the user wants every style in Elementor's own controls.


When to Use

  • A page from a brief, a screenshot or a mockup.
  • A design you can read but that has to land as Elementor settings, not a stylesheet.
  • A first build looked off: wrong font size, light blue headings, buttons on separate lines, the theme header and title above the page.

Trigger Phrases

  • "build this page in elementor"
  • "make an elementor landing page"
  • "recreate this design in elementor by hand"

Workflow

1. Read the site

respira_get_site_context, then respira_get_builder_info for the Elementor version and whether containers are on. You write the tree as section > column > widget; Respira writes it in the shape the site uses.

2. Pick the template

A landing page draws its own header and footer, so it should not sit inside the theme's. Pass template to respira_build_page:

  • "elementor_canvas": nothing but the page. No theme header, page title or footer.
  • "elementor_header_footer": the theme's header and footer, the page full width between them, no page title.
  • omitted: the theme's default template, with its title and content width.

Read the full file on GitHub · 123 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 123 lines · 84 tokens per session scan A 2f9cf4da94f5

Subscribe to this mod's changes

build-elementor-page is a skill published in the GitHub repository respira-press/agent-skills-wordpress (48 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 2,031 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.