Uniform agent skills
Uniform maintains a public, open-source set of agent skills that teach AI coding assistants how to build correctly on Uniform. They are task-scoped instructions — how to wire up a Next.js integration, how to model a content type, how to build a mega menu — verified against the shipped Uniform SDK packages.
The skills live in uniformdev/agent-skills and ship as a plugin for Claude Code, Codex, Cursor, and GitHub Copilot, and as plain skills for any other agent that reads SKILL.md.
Agent skills vs Scout skills
These are two different things:
- Agent skills (this page) teach your coding assistant — Claude Code, Codex, Cursor, Copilot — how to build with Uniform, in your code editor or terminal.
- Scout skills teach Scout, inside Uniform, your team's repeatable content procedures.
If you want Cursor to write a correct Uniform integration, you want agent skills. If you want Scout to follow your editorial process, you want Scout skills.
Why skills help#
Out of the box, an assistant's knowledge of Uniform is limited to whatever it indexed from the public internet before its training cutoff — so it invents APIs, reaches for deprecated packages, and models content in ways that make life hard for editors later.
Skills close that gap, and they are cheap to keep installed. Only each skill's name and description sit in the assistant's context at startup; the body loads on demand, when the assistant decides the task calls for it. All the skills together cost roughly 1,500 tokens of always-on context.
Install#
Claude Code#
The skills work immediately, with nothing to configure. The plugin also bundles the Uniform MCP server, which is optional — run /plugin configure and supply your project ID and API key to enable it. Claude stores the key in your system keychain. Until you do, the server is listed but will not connect.
Because the plugin declares no version, Claude Code tracks the repository's latest commit, so /plugin update uniformdev@uniformdev picks up new skills as they land.
Codex#
Uniform is published in the Codex plugin directory, so no marketplace setup is needed:
You can also find and install it through the Codex marketplace.
The CLI command requires Codex 0.153.0 or newer. On older versions the plugin is not visible in the directory listing — run codex update first.
GitHub Copilot#
The repository root is a portable Agent Plugins manifest, so Copilot installs it directly from the repository:
To load a local checkout instead, use copilot --plugin-dir /path/to/agent-skills. Either way you get the skills only — the portable manifest deliberately ships no MCP configuration, because the specification forbids putting a credential in one. Set up the Uniform MCP server separately if you want it.
Cursor#
Open Customize in the sidebar, choose Add marketplace, and enter:
Then install Uniform from that marketplace. Set UNIFORM_PROJECT_ID and UNIFORM_API_KEY in your environment if you also want the bundled MCP server.
Any other agent#
Many assistants read SKILL.md natively. Install the skills on their own with:
This installs into each agent's native skills directory, and npx skills update refreshes them. It installs skills only, not MCP.
Using the skills#
You do not invoke a skill by name. Describe the task the way you normally would, and the assistant picks the relevant skill from its description:
- "Add Uniform to this Next.js app so we can manage the homepage."
- "Our editors need a header with dropdown panels they can author and reorder."
- "Add a newsletter signup form to the homepage."
- "Review our content model — editors say the entry list is unusable and filtering doesn't work."
- "Build a custom Mesh data connector so editors can pick products from our PIM."
If a skill does not seem to be firing, name the area explicitly ("using the Uniform Mesh skill, ...") and check that the plugin is enabled.