Skills
Ad-ops playbooks your connected AI agents can run via the AdCrunch MCP server. Manage them in the console.
A Skill is an ad-ops playbook — a set of instructions that teaches an MCP-connected agent how to run a workflow using AdCrunch’s own tools (for example: “pull the last 14 days of Meta campaigns, then flag anything over target CPA”). You write a Skill once; every teammate’s connected agent can run it consistently, with no copy-paste.
Skills are private to your organization. New organizations start with an empty Skills store.
Manage Skills in the console
Open Skills in the console sidebar.
- Create a Skill with New skill. It opens the Adgent beside the list, and sends it “I want to create a new Skill.” The Adgent asks you what the playbook does, and when an agent must use it. It then writes the Skill at once, and the page of the new Skill opens on the left of the screen.
- Create a Skill with the form: Cmd-click New skill (Ctrl-click on Windows and Linux). The form asks for a
name, adescription(what an agent reads to decide when to use it), and thebody(the markdown instructions). Optionally set a custom slug. - Edit a Skill on its own page — change the name, description, or body, copy its handle, rename its slug, or delete it.
The slug is the agent handle
Every Skill has a slug — its stable, per-organization handle. Agents fetch a Skill by slug (skill_get with skill_name: "weekly-meta-audit"). The slug is derived from the name when you create the Skill and shown with a copy button in the editor.
Agents can edit Skills too
Anything you can do in the console, a connected agent can do over MCP with the skill:write scope — including creating and updating Skills mid-session. To keep a human edit and an agent edit from clobbering each other, every save is guarded by a revision: if the Skill changed since you opened it, the console shows a “reloaded the latest” notice instead of overwriting.