Give AI one job and limits you can review.

The assistant's job, the things it may do, and the guides it may read all sit beside the fixed steps and records around it. Your house voice lives in a written guide it opens when it needs one.

Join private betaSee how it works

Use agents for judgment. Use workflows for rules.

Give the assistant the context for one job and nothing more. Keep predictable steps explicit in the process. Put long-standing know-how in a written guide instead of a swelling prompt.

The file says what the assistant may touch.

It states the job, the processes the assistant may run, the guides it may open, and the moment a person has to look at the result. Swirls holds it to exactly that.

Example: An editorial agent can open the house voice guide, run the publish process, and still leave the decision to publish with an editor.

Swirls owns the production work behind it.

Running the assistant, holding the supported access limits, handing it the tools you allowed, pausing for review, and keeping the record.

Write the guides

Keep house style and know-how in documents the assistant opens.

Hand over the tools

Give it only the processes and actions the job needs.

Stop for review

Send anything sensitive or uncertain to a person first.

editorial/desk
editorial-desk.swirls
skill editorial_voice {
  name: "editorial-voice"
}

agent editor_assistant {
  label: "Editor assistant"
  secrets: editorial_ops
  provider: openrouter
  model: "openai/gpt-4o-mini"
  maxSteps: 8
  skills: [editorial_voice]
  tools: [publish_article]
  system: @ts {
    return [
      "You help the editorial desk move drafts through review.",
      "Open the editorial-voice skill before judging tone, attribution, or house style.",
      "Never publish a draft an editor has not approved.",
    ].join("\n")
  }
}

channel editorial_room {
  label: "Editorial room"
  platform: swirls
  agent: editor_assistant
  mode: mention
}
Skill · editorial-voice

The assistant opens this while it reads a draft. House tone and attribution rules stay in writing, where anyone can edit them.

.agents/skills/editorial-voice/SKILL.md

Prefer concrete claims. Flag missing attribution. Never invent quotes.

Tool call

publish_article

Covers

  1. Business context
  2. Written guides
  3. Allowed tools
  4. Conversation
  5. Human review
  6. A record of what it did
Read the technical docs

You own

The assistant's job, its context, the actions it may take, what counts as a good result, and every point where a person must look.

Give the assistant a job you can describe.

Name the context, what it may do, what it should read, the result you expect, and the point where a person decides.

Join private betaSee how it works