A conversation, a chain of skills, a team of agents, a gate for human judgment, a schedule to run it all unattended — the primitives every other pillar builds on.
Instead of learning where twenty different tools live, start a conversation and let the Assistant route the request to the right skill, Pipeline, or Crew — the way a new hire asks a colleague instead of hunting through a wiki.
A Pipeline chains skills together — the output of one step becomes the input to the next — versioned, re-runnable, and inspectable at every step. Change one step without rewriting the whole workflow.
Some problems need more than one perspective. A Crew assigns a goal to multiple agents with different roles — researcher, drafter, reviewer — who collaborate toward one outcome, the way a real team splits the work.
Not every step needs a person watching. An approval gate sits exactly where the cost of a mistake outweighs the cost of a pause — a specific step, a specific condition, a specific approver — and the workflow waits, not guesses.
A Pipeline or Crew that works once should be able to run itself — daily, weekly, or on an event trigger — without someone remembering to kick it off by hand.
A human in the loop wherever the risk of getting it wrong outweighs the cost of a pause.See how this rolls up in Govern & Prove Value →
Chain two skills into a Pipeline and run it — no setup, no sales call required.