Opidocs
GuidesAssistant guides

Build a workflow around the right skills

Combine several skills into a repeatable flow the assistant runs for you.

Intermediate · ~10 min · Prerequisites: familiar with skills

What you'll do

Map your repeatable task to the skills that handle each step, ask the assistant to chain them in one message, and save the whole flow as a scheduled task so it runs without you.

Pick the skills

Start by naming what you need the assistant to do — then match each step to a skill. For example, a weekly competitor digest might use a web-research skill, a summarize skill, and a format-as-markdown skill.

Open Browse all… (type /Browse all…) and check which skills cover your steps. If a step has no skill, the assistant can still handle it with a plain instruction — you don't need a skill for every part. See Browsing skills for the full catalog.

Chain them in one ask

You don't need to send three separate messages. Describe the full flow in one prompt:

"Use the web-research skill to find the top 3 competitor launches this week, summarize each in two sentences, then format the result as a Markdown table with columns for Company, Launch, and Impact."

The assistant invokes each skill in sequence and hands off the output from one step to the next. Review the result and refine with a follow-up if any step needs adjustment.

Save it as a scheduled task

Once the flow produces what you want, ask the assistant to run it on a schedule:

"Run this every Monday at 8am and send the result to my inbox."

The assistant saves it as a recurring task. See Set up a recurring summary for details on scheduling, changing the time, and pausing.

Scope

Skills have a scope that controls who can use them:

  • Common — available to all users by default
  • Org — installed by an admin for everyone in your organization
  • Agent — attached to a specific custom agent and not visible in the general library

If a skill you want is missing, ask your org admin to install it, or build one yourself — see Create a custom skill.

Try this next

On this page