Share skills, AGENTS.md and MCP servers with your team
Your team wants every agent, on every harness, on every laptop, to know the same things: how you test, how you name
things, which MCP servers to use. wisp keeps that in your repo, so it’s reviewed like code and everyone gets it with
git pull. There are three parts: rules (AGENTS.md and instructions), skills, and MCP servers.
Rules: AGENTS.md
Claude Code, Codex, Cursor, opencode and the others read AGENTS.md at the root of the repo. Keep your house rules
there and commit it. Claude Code reads CLAUDE.md instead: make it one line, @AGENTS.md, so both read the same
file. A folder deeper in the repo can have its own AGENTS.md for the rules of that part.
wisp init adds one short section to AGENTS.md (and to CLAUDE.md when there is one): it tells agents how to read
the tasks behind the code (wisp tasks --touching <path>). It adds it once, and only beside .wisp/.
Rules that only some agents follow go on the agent profile, or on the project:
agents: reviewer: { harness: codex, mode: plan, instructions: "Review only. Never change files. Correctness first." }projects: api: { path: https://github.com/acme/api, instructions: "Every endpoint gets a test in tests/api." }A crew member has its own AGENTS.md in its kit, followed on every job. See
Crew and check-ins.
Skills
A skill is a how-to an agent picks up when it needs it: “how we write migrations”, “how to release”. Write it as
a markdown file, or a folder with a SKILL.md, then declare it and give it to the agents that need it.
wisp: 1skills: migrations: { description: How we write and test database migrations, path: docs/skills/migrations.md } release: { description: How to cut a release, path: .wisp/skills/release }agents: builder: { harness: claude, skills: [migrations, release] } helper: { harness: codex, skills: [migrations] }A relative path is the repo’s. The description is what an agent reads to decide whether to use a skill, so say
what it’s for. A short skill can be inline, with body: instead of path:. Each task records which skills it had
and which it used. To see whether a skill helps, run the task with and without it:
Try it two ways.
MCP servers
Declare an MCP server once as a connector. Every agent that should have it gets it, on every harness.
wisp: 1connectors: linear: { url: "https://mcp.linear.app/sse", oauth: true } postgres: command: npx args: ["-y", "@modelcontextprotocol/server-postgres"] env: { DATABASE_URL: "${secret:DB_URL}" } agents: [builder] # only these agent profiles get it modes: [plan, edits] # and only in these modesSecrets never go in the file. ${secret:NAME} names one; each person sets the value on their own computer:
⌘K → Settings → Agents → Connectors. A connector that needs a key or a sign-in says so; Sign in
opens the server’s page for an oauth: true server. The token stays in your secrets file.
In the browser (wisp --browser, or your cloud wisp) it’s the same window, menus and keys.
Tap the person button at the top of Tasks → Settings → Agents → Connectors. A connector that needs a sign-in says so; Sign in opens the server’s page. A key is easier to paste from the Desktop app tab.
Secrets are typed hidden, so set them from a terminal (CLI tab). Then check the server:
/connectors listwisp secret set DB_URL # typed, not shownprintf %s "$DB_URL" | wisp secret set DB_URLwisp validate # says which secrets aren't set here yetAlready have MCP servers?
The MCP servers in Claude Code’s or Codex’s own config can come in as connectors, so every harness gets them.
⌘K → Settings → Agents → Connectors → Found in your harnesses → Review, tick them, and Add.
Person button → Settings → Agents → Connectors → Found in your harnesses → Review, tick them, and Add.
/connectors import --names linear,sentrywisp connectors list # yours, and the ones found in your harnesseswisp connectors import --names linear,sentrywisp export connectors > .wisp/connectors.wisp.yml # as a formula to commitMany repos: modules
Put the shared setup in its own repo (acme/wisp-setup) and use it everywhere as a module:
# .wisp/team.wisp.yml in each repomodules: team: { source: "git::https://github.com/acme/wisp-setup//team?ref=v3" }wisp init fetches it and pins it in .wisp/lock.yml. Moving to ?ref=v4 is one pull request per repo, reviewed
like any other change. See Formulas.
Without git: share through wisp Cloud
wisp share skill.migrations # a link: the skill and what it referenceswisp share connector.linear --access people:ana,benwisp open <link> # the other side: see what it adds, then import itA shared setup never carries a secret: it names the ones it needs, and whoever imports it sets their own. In the app, Settings → Advanced → Setup → Share setup makes the same formula to copy.