Agent Profiles

An Agent Profile is different from the other five resource types: it doesn't have its own long-form content or version history. Instead, it's a named bundle — a package of references to existing Contexts, Instructions, Skills, Prompt Templates, and Checklists that together define a role, like "Backend Developer," "QA," or "Marketing."

What an Agent Profile is for

Instead of pointing an AI tool at five separate resources every time, you assemble them once into a profile that matches how your team actually thinks about roles: "everything a Backend Developer needs," "everything a new hire on the Marketing team needs," "everything the on-call engineer needs during an incident."

Building a profile

1. Open a project and go to its Agent Profiles tab.
2. Click Create, and give it a title and description (e.g. "Backend Developer" / "Owns API and database work for this project").
3. Open the resource picker. It's organized into sections — Contexts, Instructions, Skills, Prompt Templates, Checklists — each listing that project's existing resources with a checkbox. Use Select all within a section if the whole category applies, or hand-pick individual items across sections.
4. A preview panel shows exactly what's currently selected before you save, so you can double-check the bundle reads correctly as a whole.
5. Save. Unlike the other five types, there's no draft content to publish — the profile itself doesn't have a status; what matters is that the resources inside it are published (see below).

Editing a profile's resource list

Reopen the resource picker at any time to add or remove resources — it replaces the profile's full list in one save, rather than adding/removing one at a time.

Why bundle resources instead of writing one big document

Individual resources stay reusable and independently versioned — a Skill used by the Backend Developer profile can also be reused, unchanged, in a Frontend Developer profile. The Agent Profile is just the assembled reading list for a given role; the underlying Contexts/Instructions/Skills/etc. are still edited and versioned exactly as described in their own articles.

Publishing still matters per-resource

An Agent Profile bundles references. If a bundled Context or Instruction is still in draft, it won't be included when an AI tool fetches the profile through MCP — only resources that are both referenced by the profile and individually published are actually served. Publish each piece you want included, not just the profile.

What happens if a bundled resource is deleted

If something referenced by a profile is later deleted, the profile shows a placeholder noting that resource is gone, instead of breaking. Re-saving the profile's resource picker will drop it from the bundle for good.

Who can write

Creating, editing, and deleting an Agent Profile requires org-admin-level project access (owner/moderator). Everyone with project access can view a profile and preview what's bundled into it.

Serving Agent Profiles to AI tools

Agent Profiles are one of the things an MCP connection can expose — an AI client can fetch a whole profile in one call and get every published resource bundled into it, instead of fetching each resource individually.