Use the built-in library
Search the library by name, category, or purpose. Open a skill to read its instructions and see which agents can use it. Workspace admins can turn a built-in skill on or off. Turning it off keeps it in the library but prevents agents from loading it. Choose Edit to create a workspace copy when the shipped instructions are close but not quite right. Once that copy is on, agents use it instead of daoco’s version.Create a skill
1
Add the basics
Under Your skills, choose New skill. Give it a clear name and
describe the tasks that should trigger it.
2
Choose where it applies
Select the agents that may load it. You can make the skill available to
every brand in the workspace or limit it to selected brands.
3
Write the playbook
Add direct instructions in Markdown. Put examples, source material, or
longer reference notes in the skill’s extra files instead of crowding the
main playbook.
4
Turn it on
New skills start off. Review the saved copy, then turn it on when agents
should begin using it.
Import and export
Use Import to add a compatible skill package. Export a workspace skill when you want a backup or need to move it to another workspace. Imported skills still start off, so nothing changes agent behavior until someone enables them.Write a useful trigger
The When to use field decides whether daoco considers the skill for a task. Name the situation and the expected work. Avoid broad triggers such as “use for marketing” because they make unrelated requests compete for the same playbook. Good trigger:Use when writing a customer case study from an interview transcript. Pull only claims supported by the transcript and keep direct quotes attached to the named speaker.Keep the playbook concrete. Tell the agent what inputs to check, what decisions to make, what output to return, and what it must not invent.
Skills and your assistant
Your assistant can use the same skills. Ask it “what skills do we have?” and it lists your workspace skills and the library skills you have not turned off. When it hands work to a brand thread and a skill covers that work, the thread and every specialist it delegates to are told to load that skill. You can also teach it a way of working. Describe a procedure in the channel, for example “remember how we write launch threads: open with the outcome, one post per feature, end with the link”, and the assistant saves it as a draft skill under Your skills. It replies with a link to the draft. A fact or preference, such as “our launch day is Tuesday”, goes to the assistant’s memory instead. Drafts from the assistant stay off, like any new skill. A workspace admin reviews the draft, edits it if needed, and turns it on, or archives it if nobody needs it. Only members who have linked their chat account can ask the assistant to save a skill.Manage a skill
- Turn a custom skill off to stop agents loading it without deleting the draft.
- Archive a custom skill when the workspace no longer needs it. If it replaced a built-in skill, archiving restores daoco’s version.
- Edit the workspace copy rather than the built-in original. Library updates remain separate from your copy.
- Limit a specialist playbook to the agents that can act on it. A video editing checklist does not need to load during billing questions.