Skip to main content
Replo’s skills teach AI agents how Replo works: how pages load Shopify data, how publishing works, how branding is applied, and how to use each integration. They live in the Replo MCP server’s skills tool, so every client reads the current version, and they update whenever Replo does.

​
Before you begin

  • Connect Replo in Cursor, Claude Code, Codex, or another AI client. Skills come through that connection; reading them doesn’t need a Replo account, but working on your projects does.
  • In Claude, the Replo plugin already includes everything below.

​
Make your client use them

1

Install the Replo skill

In a coding client, install the one replo skill, which tells your agent to call skills before doing Replo work:
Follow the installer’s prompts to select your client and project scope.
2

Check that it reads them

Ask your client:
You should see the list of skills and a summary of building-replo-pages. If your client does not call the tool, check that Replo is connected and start a new chat in the same workspace.
3

Use them on a real task

Name your Replo project and site, then ask for an outcome. Use one of the examples below and replace the bracketed values.

​
Try a workflow

​
Bring in a Figma brand

The design must be accessible through a connected Figma account. The skills explain the workflow; they do not grant access to the file. Review the resulting brand kit and preview before applying more changes.

​
Build from your product catalog

Connect Shopify to the Replo project first. Check that the preview uses your actual products and that its links lead to the right pages.

​
Fix a mobile shopping flow

​
Keep skills current

Skills update with Replo, so there is nothing to update in your workspace. npx skills update only refreshes the replo skill itself.

​
How skills work with Replo

Two ways an external agent works on a Replo project, and every skill says which it uses:
  1. Edit the site’s code directly. Every Replo site is a Next.js repo. Read the local-development skill to connect git: it reuses working credentials, otherwise creates a user API key with create_api_key, stores its secret, and clones the site’s clone_url from list_sites (see the Git docs). Edit locally, push, and inspect the site in Site Builder. Publish with publish_site only when asked.
  2. Use a dedicated Replo operation. create_site_page and edit_site_page delegate a selected page to the internal agent. update_brand saves branding, from ops or a website; apply_brand_kit_to_site applies it to a selected site. Continue within the original scope with the same dedicated tool with its sessionId and the returned sessionId. Generic project edits and report creation are not exposed.
Calling skills with no arguments lists every skill with its description; skills({ name: "publish" }) returns its full SKILL.md, following the Agent Skills spec. They are written for an agent to read, not a person. Besides the skills below, the list has one skill per integration (Klaviyo, Shopify, Google Analytics and the rest) and replo, a map of which tool does what.

​
Next steps

Edit your site locally

Ask your coding client to clone a site, start its preview, and make an edit.

Connect your coding client

Authorize access to your Replo projects.