Skip to main content
Skills are instructions Daoco loads when a task matches them. They can define a writing method, a design process, a research checklist, or rules for working with a specific tool. Most skills guide work that is already running. A workflow is a skill that also starts work: typing its slash command in chat runs its steps in order. Click the brand at the bottom of the sidebar, choose Settings, and open Skills under Workspace. The page has Daoco’s built-in Library and Your skills for workspace-owned skills. The first time you open Skills, a five-step walkthrough explains the library, workspace skills, triggers, agent access, brand scope, and publishing controls. It switches between the two tabs for you but does not change any skill.

Use the built-in library

Search the library by name, category, or purpose, or filter it to Workflows or Skills. Open a skill to read its instructions and see which agents can use it. A workflow also shows its command and every step, with the specialist that runs 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. For a workflow, choose Copy and edit: the copy opens in the editor with its steps. 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. Keep Skill selected, 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 skill

Add direct instructions in Markdown. Put examples, source material, or longer reference notes in the skill’s extra files instead of crowding the main skill.
4

Turn it on

New skills start off. Review the saved copy, then turn it on when agents should begin using it.
Published skills can only be changed by workspace admins. Other members can draft skills for an admin to review.

Start a workflow with a slash command

A workflow is a skill with one or more slash commands, such as /launch, and a fixed list of steps, each handled by one specialist with its own instructions. Typing the command in brand chat runs exactly those steps, in that order, with the rest of your message as the brief. A workflow can answer to more than one command, and its rules can skip steps by command: /check-pages runs the weekly SEO review without preparing fixes, /suggest-pages runs only the first step of /page-plan, /email-copy runs the email workflow for copy only, and /page-pr runs the page workflow for a page you already saved. Shipped workflows read each source in its own step (the CRM, then call notes; Reddit, then the other networks) and finish with a step that brings them together, so a source you have not connected is skipped without holding up the rest. To write one, choose New skill under Your skills and select Workflow. Name it, say what it does, and check the slash command, which starts as the name. The steps page lists the steps on the left, with the rules and extra files under them. Pick one to see it on the right, one at a time. Text shows formatted; click it to edit, with the same Markdown editor brand documents use. For each step:
  • Pick a specialist for each step. A specialist can appear more than once, for example writing a draft, then checking its claims, then writing again to revise. A specialist’s steps always run in order.
  • Write what that specialist should do in this step. Daoco adds your message and what earlier steps produced.
  • Optionally choose Works in to pin the step to one connection your brand has, such as Google Search Console or Shopify. The specialist works in that connection and never uses another source. If the brand has not connected it when the workflow runs, Daoco skips the step, shows “not connected” on the plan, and moves on to the next step. Shipped workflows can name several connections for one step, such as any analytics tool; the step runs when any one of them is connected. Then write what to do there, in order.
  • Steps run top to bottom, each after the one above it; use the arrows on a step in the list to move it. Each step says in a sentence when it runs. Turn on Run at the same time as the step above when two steps for different specialists do not need each other’s output.
To turn an existing skill into a workflow, edit it and choose Workflow. Daoco never adds, removes, or reorders steps. When a step does not fit a request, for example no visuals were asked for, it is skipped and the plan shows why. Approvals work as usual: publishing and scheduling still stop for your review. Rules for the whole run is optional guidance for every step: when a step should be skipped, what the run must never do, and what the final report covers. Each step’s instructions go to that step’s specialist. A workflow with no command starts from the skill’s name, such as /launch-plan. A name works as the first word of a message; a command you declared works anywhere in it. Typing / in brand chat lists your workflows. Skills are not commands: Daoco loads one when a request matches its When to use. Your message shows the workflow it started as a label with its name and command, such as AI visibility check /ai-check, followed by the rest of what you typed. Buttons that run a built-in process, such as Write it on a suggested page or Fix with Daoco on a finding, the first-win picks at the end of onboarding, and the assistant’s follow-up offers, start that workflow the same way: the thread opens with its command and a short subject, such as /write-page acme vs globex for small teams. The finding, page, keyword, or conversation the button belongs to goes to the run as data, so it is not repeated in your message. These buttons need that skill turned on. If you want the process to work differently, copy the skill and edit your copy instead of turning it off. Daoco also runs a few workflows of its own, such as the website, email, store, and customer reviews right after onboarding. They have no command and are not listed after / or in the library; their thread shows the workflow’s name and what it reads. A command works once the skill is on, in the brands the skill applies to. Commands are unique in a workspace. The built-in commands, such as /post and /campaigns, are library skills too. To change what one does, copy it with Copy and edit; your copy keeps the command. Your assistant can also run a workflow on a schedule.

Ask Daoco to write, change, or fix a workflow

You do not have to use the editor. In any brand thread, ask in your own words:
  • “Turn this into a workflow”, after work you liked. Daoco reads what that run recorded, keeps the steps that completed, and leaves out the ones that failed, were skipped, or had to be redone.
  • “In my launch workflow, add a step that saves the announcement as a LinkedIn draft.”
  • “Change step 2 of /site-audit so it only looks at the pricing and product pages.”
  • “/seo-review keeps skipping its last step. Fix it.” Daoco reads how the workflow’s recent runs went, step by step, before proposing anything.
Mentioning a command in a request to change its workflow does not need to run that workflow. The Skills specialist handles the proposed change. It never changes a skill itself. It opens a Workflow panel beside the thread showing the whole skill as it would read, with each new or changed step marked, what a changed step says now, and why the change is proposed. Each step shows what it waits for, with the previous waits shown when the execution order changes. Removed steps keep their previous instructions visible, even when the proposal removes every step. You can edit the proposal right there before taking it: click a step to change its title, specialist, or instructions (Markdown works), click the rules to rewrite them, or add and remove steps. Choose Apply to take it or Discard to drop it. Ask for another tweak in chat and the panel updates; Daoco starts from the proposal as you edited it. When a thread has proposals for more than one skill, the panel lists the others so you can switch between them. After you apply, the panel shows the skill itself and stays editable, so further edits there save straight to the skill. Applying a change to a skill that is on needs a workspace admin, the same as editing it. A new skill is saved off, under Your skills. A change to a built-in skill saves your own copy, including its reference files. It takes effect immediately when an admin applies it; otherwise it stays off until an admin enables it. Stale proposals cannot overwrite newer edits; ask Daoco for an updated proposal. The version you replace is kept: Undo in the panel puts it back, until the skill is edited again. Undoing a change that created a skill archives that skill.

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 skill. 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 skill 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 workflow 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 skill to the agents that can act on it. A video editing checklist does not need to load during billing questions.
Skills load only when they match the current task. They do not appear as transcript steps. The work they guide remains visible in the normal chat execution view.