Let a coding agent add Configure

A skill provides instructions for an agent. Give its URL to a coding agent to load those instructions. Configure provides one skill for integration and one for profile use.

Add Configure to your project

In the project you want to add Configure to, send this message to Claude Code, Cursor, or Codex:

Read https://configure.dev/skill.md and add Configure to this project.

The agent reads the skill and builds the seven Quickstart steps in your code. In order:

1. It reads your code and decides two things without asking: where to place the connection button (onboarding, an empty chat, or settings), and whether your app has its own users. If it does, profiles are keyed by your user ID. Only an app with no accounts at all gets Sign in with Configure.
2. It installs the SDK. If your credentials are not in the environment yet, it asks you to run npx configure setup --users, because that step opens a browser and needs you.
3. It adds a connection button linked to a route on your server. The route creates the link with profile.connect({ returnUrl }) and redirects to the Configure hosted flow.
4. It adds the callback route: it refreshes the user's stored context and sends them to the chat. A user who did not finish goes back home.
5. It adds the daily refresh, the first-turn injection, a commit at the end of every turn, and the configure_* tools on your model call (Anthropic, OpenAI, or Vercel).
6. It writes a test against the sandbox, runs it, and shows you the result.

Complete setup when requested, review the changes, and run the app.

The skill forbids it to build a Configure link by hand, keep its own connected flag, expose your secret key to a browser, or leave the refresh and the commit to the model.

TIP

No account yet? The skill starts from the sandbox, so the agent can build and test everything before you sign up.

Add profile-use instructions

A model may not use profile tools consistently without instructions. This skill specifies when to search, save, and exclude profile information:

• Search the profile before saying you do not know something about the user.
• Save a durable fact the moment the user states it, without asking permission.
• Keep project conventions and code style out of the user's profile.

https://docs.configure.dev/skill/agents-block.md

Append it to your agent's system prompt or rules file. For Claude Code, this installs it along with a hook that loads a short digest of the user at the start of every session:

curl -fsSL https://docs.configure.dev/skill/install.mjs | node -

Per-client steps for Codex, Cursor, Windsurf, and Gemini CLI are on the coding agents page.

For platforms that host agents

If you run a platform that hosts other people's agents, your platform provisions the keys and every agent on it gets Configure. Maritime has a skill for this today.

https://configure.dev/configure-maritime-skill.md

How the skills are tested

Every skill on this page is tested two ways before it ships:

• Question-based evaluation. A small model gets only the skill and must answer a developer's questions correctly: where the connection button goes, what its route and the callback route call, how to tell whether a user is connected, when to refresh, what to commit, how to wire each model provider, and what never to do.
• Integration test. A fresh agent gets only the skill and a real app, and what it builds must run against the sandbox.

If you write a skill for your own platform, run the same two tests. Specify the full API host, api.configure.dev. Show how to pass mcp_servers to the model. Creating an MCP session alone does not expose its tools to the model.