More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Cornerstone Pages for Themeco X and Pro, No Hand-Save

    1

    Stop hand-saving the blank X and Pro pages your agent writes. Get a draft built from your own sections that renders right away.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Cornerstone Pages for Themeco X and Pro, No Hand-Save

    Cornerstone Pages for Themeco X and Pro, No Hand-Save

    Example session with this skill installed

    I run a WordPress site on the Themeco Pro theme with the Cornerstone builder. The site facts, an export of my Services page's Cornerstone data, and the copy for a new page are in ./site/. Build me a new "Water Heaters" page in the same style as Services: hero, short intro, the "what we install" list with the image, my Request Service Gravity Form, and a call to action. It has to look right on phones, and I need to keep editing it in Cornerstone afterward. I have SSH and WP-CLI on the server. Put the page data and whatever I need to run on the server in ./out/, and tell me exactly what to run.

    • Read your context and instructions
    • Compiled the cornerstone pages

    I've built the Water Heaters page and written the run steps, but nothing has run on your server yet. The page data passes the checker against your Services export (0 errors, 0 warnings). The files are in ./out/:

    • water-heaters.json: the page data.
    • cs-build.php: the build script.
    • cs-recon.php and cs-export.php: read-only helpers.
    • RUN.md: the full command list.

    What I built

    The page has five sections, cloned from your Services page's own styles, colors and fonts, with your copy word for word:

    1. Hero: the headline, subhead and "Get a Same-Day Quote" button linking to #request-service.
    2. Intro: "Cold Shower This Morning?" and its text.
    3. What we install: the "WHAT WE INSTALL" heading, the four-item list and image 431.
    4. Request Service: your Gravity Form 3, with an anchor above it for the hero button.
    5. Call to action: "Book a Plumber Today" and a "Call (555) 014-2290" button linking to tel:5550142290.

    Phones

    Phone sizes. smaller font sizes, padding and background-image sizes are set for phones and tablets as per-breakpoint overrides on the same elements. I didn't make separate phone copies, so the form appears once.
    Stacking. the list and image stack on phones, as they do on Services.
    Big heading. Services uses a 9.6em "SERVICES" heading, which would overflow a phone. I scaled "WHAT WE INSTALL" down to 3em on small phones and 4.5em on larger ones. Your Services page probably has that overflow problem now.

    What to run

    Replace HOST with your SSH login and run these from the WordPress root, ~/public_html. Don't use --skip-themes, because on Pro that unloads Cornerstone.

    ssh HOST 'mkdir -p ~/cs-build'
    scp out/water-heaters.json out/cs-build.php out/cs-recon.php HOST:~/cs-build/
    ssh HOST 'cd ~/public_html && wp eval-file ~/cs-build/cs-recon.php'
    ssh HOST 'cd ~/public_html && wp eval-file ~/cs-build/cs-build.php elements=$HOME/cs-build/water-heaters.json title="Water Heaters" slug=water-heaters like=57 protect=57 dry-run=1'
    ssh HOST 'cd ~/public_html && wp eval-file ~/cs-build/cs-build.php elements=$HOME/cs-build/water-heaters.json title="Water Heaters" slug=water-heaters like=57 protect=57'
    ssh HOST 'cd ~/public_html && wp cs clear_style_cache'
    

    Then purge your host cache and Cloudflare. RUN.md also has checks that form 3 and the images exist.

    Safety. the build creates a draft, backs up what it touches and checks that page 57 is unchanged. Every check line should say PASS.
    Saving through Cornerstone. the script saves the way the builder does, so the page renders straight away and opens in the builder.
    Storage mode. it should be shortcode storage, since the site was built in 2021 and updated since. Expect post_content to start with [cs_content. The recon step confirms it; I haven't seen your server.
    Rolling back. trash the draft. Services is untouched.

    What I couldn't confirm

    Form element. your Services export has no form element, so I couldn't copy the form's property names. I put the Gravity Forms shortcode [gravityform id="3"] in a text element, which uses only elements your site already has. It should render and stay editable. If you'd rather have a native Form Integration element, swap it in the builder afterward.
    Images. I don't know which images are 412, 414 and 431 beyond your note that 431 is the technician. The hero and call-to-action background images (412 and 414) are reused from your Services page. Swap them if you want something different.
    Dark section on Services. the "What we install" section copies Services' pale text, which only reads if the page background behind it is dark. Check it in the preview. I gave the form section its own Paper background so it reads regardless.
    Phone check. I couldn't view the page, so the phone sizes are untested. Look at the draft on a real phone or in device emulation, especially that the hero background image doesn't cover the text and that the form loads and submits.

    After the build, open the page in Cornerstone and click Save once. That's your proof it's editable. Publish only after that.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem. You ask your AI agent for a new page on an X or Pro site. It writes the builder data straight into the database, the page comes out blank or stale, and you end up opening it in Cornerstone and clicking Save yourself. Sometimes it also copies the flag that marks a page as "edited outside the builder", so Cornerstone stops treating it as a builder page. Themeco does not document the data format or a save API, so every agent guesses. This skill makes the agent save the page the way Cornerstone does, so you get a draft in your site's own style that renders right away.

    What it does. You say something like "Build a Water Heaters page in the same style as our Services page, with our Request Service form, and make it work on phones." The agent surveys the site read-only, copies the closest existing page's sections, colors and fonts, checks the new page against your pages, and gives you the exact commands (or runs them itself if it has SSH and WP-CLI). The build saves a draft, backs up anything it changes, prints PASS or FAIL for each check, and you open the preview.

    • Saved through Cornerstone's own save method, so the page renders without a manual Save. On Cornerstone 7.8.12 the page content it saves is byte for byte what the editor's own save produces, in both storage modes.
    • Built from your site's own elements, colors and fonts, so the new page matches the ones you already have.
    • Checks how your site stores pages first (sites built before Pro 6.7 often still use shortcode storage), so the format is read from your site, not guessed.
    • Phone sizes set as breakpoint overrides on the same elements, so there is no duplicate phone section and your form appears once.
    • Drafts, backups and protected pages, so nothing outside the page you named gets written.
    • Clears Cornerstone's style cache, so the new page does not show stale styles.

    Why this beats prompting it yourself.

    Ask a capable agent the same thing without this skill and it tends to:

    • Write the builder data straight to the database and leave the page content empty.
    • Tell you to open the page in Cornerstone and click Save to make it appear.
    • Set or copy the "edited outside the builder" flag, and skip the style cache.

    With the skill, the agent:

    • Saves through Cornerstone's own save method, so the page content is filled in.
    • Leaves you one Save in the builder as a final check, not as the fix.
    • Clears that flag, checks the storage mode and clears the style cache.

    Known limitations. Builds pages and posts, not headers, footers or layouts. It clones what your site already has; if no page uses an element (a form element, for example), the agent says so and uses the closest one it can verify. The scripts confirm the saved content and that the builder can load the page; they do not check the look or the in-browser editor, so check the preview and open the page in Cornerstone and save it once before publishing. Cornerstone's format is not documented and changes between versions: the script checks the save method on your install and stops if it is missing. Building needs SSH and WP-CLI; without them you run the printed commands. Use a staging copy first if you have one.

    What's inside. SKILL.md (the method, five rules and the hand-over format), references on how Cornerstone stores pages and the traps that break them, three WP-CLI scripts (cs-recon.php and cs-export.php only read; cs-build.php creates or updates a page with backup, protected pages, dry run and PASS/FAIL checks), an offline checker and outline tool, and a full worked example on a made-up site.

    $9. Pays for itself the first time a new X or Pro page renders without you opening Cornerstone to hand-save it into existence.

    • Builds pages and posts. Headers, footers and layouts are documented in the references but not built by the script.
    • Clones what your site already has. If no existing page uses an element (for example a form element), the agent says so and uses the closest element it can verify.
    • Cornerstone's data format is not publicly documented and changes between versions. The scripts check the save method on your install and stop if it is missing, but a future Themeco update could change it.
    • The final proof of editability is opening the page in Cornerstone and saving it once; the skill tells you to do this before publishing.
    • Styling and the in-browser editor are not checked by the scripts. They confirm the saved content and that the builder can load the page; you check the look in the preview and open it in Cornerstone once.
    • Use a staging copy first if you have one.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    ./**

    no credentials, no environment variables, no network calls from the scripts, nothing installed. `cs-recon.php` and `cs-export.php` only read. New pages are drafts.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The knowledge and the checker work in any agent that reads skills. Surveying and building need an agent that can run shell commands over SSH; without that you run the printed commands yourself.

    Both. On X, Cornerstone is a plugin and only the page builder exists, so the skill builds pages and posts there. Pro adds headers, footers and layouts, which the survey lists.

    New pages are created as drafts. Updating an existing page takes an explicit page id, writes a JSON backup first, and any page you list as protected is checked before and after and never written.

    Yes, and the skill checks for it. Older sites often still use shortcode storage even on current versions, and old pages get rewritten on their first save, so it backs them up before touching them.

    No. It uses your existing SSH and WP-CLI access. No credentials are stored or read by the scripts.

    New in Frontend & Web Apps