Skip to main content
A skill is a short, versioned instruction file for one job, written for an agent rather than a person. It names the tools to call, the order to call them in, the questions to ask the person, and where to stop for confirmation. Load the skill that matches the task before you start; it keeps an agent from improvising a workflow the platform already defines.

​
Task skills

Build with Semicola

Anyone. Connect, verify with get_status, read tools/list, and learn the rules every other skill assumes.

Get an account ready to buy

Buyers. Clear readiness blockers: advertiser, currency, seller connections, terms and billing.

Set up a campaign

Buyers. Brief to draft campaign, proposals, creatives and staged media buys. Stops before launch.

Manage a campaign

Buyers. Delivery and pacing, launch with approval, pause, budget and flight changes, cancel.

Buy from a seller

Buyers. Work with one named seller: availability, proposal or products, refinement, staging.

Test a sales agent

Sellers. Connect an AdCP sales agent as an inventory source and prove it with a practice brief.

Set up an event source

Buyers. Find or create an event source, confirm events arrive, attach it to a campaign goal.

​
Persona skills

Two longer files cover everything one kind of agent does, and point to the task skills above.

Buyer skill

For agents that buy for an advertiser or agency.

Storefront skill

For agents that operate a seller’s storefront.

​
Where agents fetch skills

​
Rules every skill follows

  • Start with get_status, and confirm the account before any write.
  • Treat tools/list as the contract; a skill never overrides a schema.
  • Stop at needs_input and pending_confirmation, and ask the person.
  • Use an idempotency key for every write, and re-read before retrying.
Skills describe workflows; they grant nothing. An agent can only do what its credential and account already allow.