Skip to main content

Creating an Agent

Creating an agent takes minutes: give it a soul, then give it tools. This page is the from-scratch path — installing a ready-made agent from the community catalog is one click on the Agents page, and everything below still applies when you want to customize one afterwards.

Step 1 — write the persona (agent.md)​

Every agent starts with one file: config/agent.md. It answers one question: what is this agent's job? Think of it as the role description you'd write for a new hire — its responsibilities, its working style, its judgment — not a list of features.

What belongs in it:

  • The role. "You are the company's support agent; you own the inbox and the FAQ."
  • Working style. Tone, brevity, language habits, when to ask vs. act.
  • Judgment rules. "Never quote prices without checking the price list." "Always confirm before sending anything external."

What does not belong in it:

  • Capability lists. Tools bring their own instructions when you attach them — a persona that says "you can send email and browse the web" goes stale the moment the tool set changes, and misleads the agent when it does. Capabilities live in Step 2.
  • Day-to-day facts. Preferences, contacts, the current project — the agent records those in its own memory as it works, and you can drop reference material into its context files. The persona is the part that stays true for months.

Two ways to write it:

  • Let the agent draft it. Create the agent, open a chat as its manager, and throw your material at it — a job description, notes, an old prompt from another tool — and ask it to write its own agent.md. Manager chats can edit the config folder, so it saves the result directly. Review, iterate, done.
  • Write it yourself. config/agent.md is plain markdown — edit it from the agent's file view.

Step 2 — add tools (MCPs)​

Tools are what the agent can actually do — files, documents, email, browsing, integrations. Attach them from the agent's MCPs settings; each tool ships its own usage instructions that load automatically into the agent's sessions, which is exactly why the persona never needs to describe them.

→ Using Tools (MCPs) for install and authorization details.

Step 3 — add skills​

Skills are focused how-to guides — playbooks the agent loads when a matching job comes up. Some arrive bundled with tools; standalone skill packs install from the community catalog and are enabled per agent in its settings.

Round it out​

  • Knowledge — drop reference documents in knowledge/; the agent consults them on demand without paying their cost in every conversation.
  • Always-on context — markdown files in config/context/ load into every session: operational rules, business vocabulary, standing instructions.
  • Onboarding — an agent can carry setup guides: setup.md (agent-wide, a manager completes it once) and user-setup.md (personal, each user completes their own copy in their first chat). Community agents use these to configure themselves; yours can too.
  • Engine & mode — pick the AI engine and the personal/shared mode in the agent's settings.
Share it

If your agent would be useful to others, the community catalog accepts contributions — see the community repository for the template format.