Research
Web search, citations, structured briefs
Versioned skills
Skills that live with each agent
Give every agent its own skill folder in your workspace—instructions, allowed tools, and guardrails you can review in git. Digio loads up to seven active skills per run, so research, sales, and support stay scoped without sharing one giant prompt.
Per-agent folder
Up to 7 active
Team review
Content agent · skills folder
- agents / content-agent
- config.yaml
- skills / research On
- skills / crm-readonly On
- skills / drafts-archive
Enabled skills merge into the prompt at run time—disabled folders stay in the repo but out of context.
Structure
How skills live in your workspace
Skills sit next to each agent’s configuration—versioned, reviewable, and reusable across staging and production. Clone from the skill catalog or author your own playbooks for the tools you trust.
Workspace tree
- team-marketing/
- └ content-agent/
- └ research-agent/
- team-sales/
- └ pipeline-agent/
CRM read-only
Scoped HTTP tools for pipeline lookup
Draft archive
Saved locally · not in this run
Workflow
From catalogue to production run
Skills are code-adjacent configuration your team owns—not a black-box prompt hidden in the UI.
-
Pick or clone a skill
Start from the catalog or copy an existing folder from another agent. Customize instructions for your stack and compliance rules.
-
Enable up to seven
Toggle which skills load for each agent. The cap keeps prompts focused—disable experiments without deleting files.
Why teams use it
Scoped capabilities per agent
Different roles get different tools—writers do not inherit sales CRM access unless you explicitly enable it.
Reviewable playbooks
Skill instructions live in files your team can diff in pull requests—policy changes ship with the same process as application code.
Tool allow-lists
Each skill declares which integrations an agent may call—read-only CRM, one Slack channel, or a single repo branch.
Seven-skill focus
Only active skills enter the prompt—prevents context bloat when you experiment with new connectors.
Shared by the team
Editors with access can update skills together—roles from team collaboration apply to the repo.
MCP & custom tools
Wire MCP servers and HTTP actions your organisation approves—skills describe when and how agents may invoke them.
Same skills in API runs
Automations through Agent API respect the same cap and guardrails—no shadow configuration.
Examples
Skills teams ship first
Typical folders you might enable on one agent—not every skill on every teammate.
Research
Search, triangulate sources, and return citation-ready briefs—only on your research agent, not the writer.
CRM read-only
Pipeline lookups for sales agents; support agents stay on helpdesk tools without CRM write access.
Engineering
Repo read, test runs, and PR drafts scoped to branches your DevOps skill allows.
Publishing
Social and CMS workflows with approval gates—pair with content workflows on the board.
Tips
Skill hygiene that scales
Keep agents predictable as you add connectors and teammates.
-
One concern per skill — split research and CRM into separate folders instead of one mega-instruction.
-
Promote via review — merge skill changes on a branch before enabling them in production agents.
-
Turn off experiments — disable a skill folder instead of deleting when you pause a connector.
-
Match the catalog — clone catalog skills first, then narrow tools to what each agent truly needs.
Connected
Skills in the full workspace
Repo skills power runs everywhere else your team works—not a separate skill system.
Explore
Related pages
Connect versioned skills to catalogue, automation, and team access.
Give every agent the right skills
Create a workspace, clone a catalogue skill into an agent folder, and run your first task from the board or API.