Skills, memory & teams
Skills are reusable bundles of tools and best-practice instructions the orchestrator consults while planning. Account memory persists your targets, protected campaigns and rules so every run respects how you operate. Organizations isolate accounts, billing, skills and memory, with per-member roles.
Skills library
A Skill bundles tools with a proven method so the agent plans your way instead of from scratch. Built-in skills seed when you create an organization; you can add your own, and the agent can save a new skill during a run.
- Per-organization — each org has its own library.
- Pin skills in the Workspace to force the agent to consider them; otherwise enabled skills load automatically.
- Great for codifying SOPs (e.g. your audit checklist or launch process).
Account memory
Each connected account carries durable memory the agent reads on every run and updates as it works. Set it once and your guardrails and targets apply everywhere.
| What it stores | Example |
|---|---|
| Targets | ROAS 2.5, CPA $30, CTR goals |
| Protected campaigns | Never pause anything matching “brand*” |
| Excluded geos | Regions to never bid in |
| Rules & pacing | Pause if ROAS < 1.5; daily budget smoothing |
| Notes & history | Timestamped log of decisions and changes |
Organizations & roles
Each organization is an isolated workspace — its own accounts, integrations, skills, memory, audit log and billing. Switch orgs from the nav; create as many as you need (great for agencies).
| Role | Can do |
|---|---|
| Admin | Everything: members, integrations, approvals, billing. |
| Editor | Authorize integrations, create tasks, approve mutations (no members/billing). |
| Member | Create tasks and view results (no integration auth or approvals). |
Frequently asked questions
- How is a Skill different from a Schedule?
- A Skill is reusable know-how the agent applies while planning; a Schedule runs a goal automatically on a cron. They compose — schedule a goal and pin the skills it should follow.
- Does memory carry between organizations?
- No. Memory, skills, accounts and billing are isolated per organization.
- Can I stop the agent from touching certain campaigns?
- Yes — list them as protected campaigns in account memory (e.g. patterns like “brand*”) and every run will respect that guardrail.