Build an agent
Describe the job and what good looks like, point Kav at expertise worth copying, and test the agent on one run.
An agent is a worker with its own instructions, skills, connections and cloud computer. When no agent in your workspace fits a job, Kav has one built for it. This page covers what to tell Kav and how to give a new agent real expertise.
Problems this solves
| Problem | What Kavela does |
|---|---|
| The agent's work is almost right, but not quite | The builder studies how experts in the field do the job, and installs that method as the agent's skills |
| You explain the job from scratch every time | The agent keeps its instructions and skills, and remembers what you approved and sent back |
| Setting up an agent means configuring it field by field | You describe the job. The builder writes the instructions, installs the skills and wires the connections |
Describe the job
Tell Kav what the agent should do and what a good result looks like. The builder fills in the rest.
| Tell Kav | Example |
|---|---|
| What it should do | Answer billing questions in our help desk |
| What it is for | Fewer billing tickets reaching the team |
| What a good result looks like | Every reply cites our pricing page. No refund is promised without my approval |
| Sources you trust | Our pricing page, and our refund policy in docs/refunds.md |
Build me an agent that answers billing questions in our help desk, so fewer billing
tickets reach the team. A good reply cites our pricing page and never promises a refund
without my approval. Work from our pricing page and docs/refunds.md.Kav proposes a name, and once you agree, files a "Build" task you can watch on the calendar. When the agent should run, on a schedule or when something happens, is set on a workflow. See Write a workflow.
What the builder does
- Names the goal the agent works toward.
- Researches the field: the core craft, the expertise a strong practitioner also relies on, and the moves specific to your goal. It works from recognised sources and skips listicles and vendor marketing.
- Collects 8 to 10 real, proven examples when the output is judged on taste, such as a video, an ad, a design or a cold email.
- Installs the expertise as skills, keeping a practitioner's published skill package whole.
- Writes the agent's instructions.
- Asks you, once, whether to use an account you already have for each service the job needs, or one it registers for you.
- Tests the agent and hands it back on the board.
Point Kav at expertise worth copying
The fastest way to a strong agent is a method that a recognised practitioner already wrote down. Paste a link to a folder of skills on GitHub, and ask for an agent that follows it:
Build an engineering agent that follows Lauren Tan's pstack:
https://github.com/cursor/plugins/tree/main/pstackThe builder clones the repository, reads its skills and installs them on the agent. A skill folder with its own scripts or examples is kept whole.
| Part | Detail |
|---|---|
| Repositories | Public GitHub repositories |
| Skill files | SKILL.md, up to 5 MB each |
| Skill folders with scripts or templates | Kept whole and read-only, at /opt/kavela/skills/<name>/ in the agent's computer |
| Templates and fill-in formulas | Read for their method, without installing them as fixed templates |
Other good sources are the skills published by the makers of the tools an agent uses. For example, Cloudflare publishes skills for Workers and Wrangler at github.com/cloudflare/skills.
Start from a pack
A pack is a set of agents that come with their skills and the apps they use. The engineering pack has two agents:
| Agent | What it does |
|---|---|
| Ship | Builds and ships web apps end to end on GitHub, Cloudflare and Supabase, and hands back the live URL |
| Echo | Plans and designs posts for X, LinkedIn, Reddit and Instagram, and posts them only after you approve |
Add a pack in the Choose agent packs step when you set up a workspace, or from kavela.ai/marketplace. Adding one opens its setup under Agents and starts a chat with Kav to connect the apps it needs.
Test it on one run
Before an agent works on its own, ask for one run and read the result: "Do one run of this now and show me what you'd deliver." See Refine the output.
Find and edit an agent
Open Agents in the sidebar. Each agent's page has:
| Section | What it holds |
|---|---|
| Overview | What the agent does and what it runs on |
| Soul | Its instructions. Edit them here. |
| Playbooks | Its skills. Skill folders kept whole are read-only. |
| Workflows | The workflows set up for this agent |
| Apps | What it does in your tools |
| Abilities | Its built-in tools |
| Memory | The rules it follows |
| Activity | Its recent work |
To change an agent in plain words, tell Kav, for example: "Have Ship add a checklist step before every deploy." Kav files the change as a task for the builder.