Skip to content
Docs
Docs

Skills and workflows

Skills, procedures the Assistant follows when you name them, and workflows, steps that run in order on Otherspace, such as Script to Storyboard.

Markdown

Skills and workflows live in a Space’s Intelligence, like its other references (see Intelligence).

Skills and workflows are documents too, with front matter that says what they do. Otherspace checks each one: its page says Valid or lists its problems. Nothing in a document that isn’t valid ever runs, and Markdown is never run as code. Only the steps and tools Otherspace knows can be used.

Skills

A skill is a procedure for the Assistant, such as how your studio describes a shot. Its front matter has:

  • type: skill, an id and a purpose;
  • tools: what it may use, for example [read_reference, generate_shot];
  • approval: always, to ask before changing your work, or paid (the default), to ask only before anything that costs money.

Its text is the procedure. Mention it in the Composer as @skill- then its id (@skill-shot-artist describe @shot-03) and the Assistant follows it, using only the tools it names. A skill never lets the Assistant do more than it could anyway, and paid work is still priced and confirmed as usual. Ask the Assistant to “save this as a skill” and it drafts one for you to save.

Workflows

A workflow runs several steps in order on Otherspace, so nothing needs to stay open. A Space can have as many as it needs, listed under Workflows in its Intelligence tab. To make one, choose New workflow in the Intelligence tab: Blank workflow, or a template such as Script to Storyboard. It opens as a document to read and change. Press Run to run it. Script to Storyboard:

  1. Name the script to use (@factory-safety-script).
  2. It extracts the script, then waits for you to check the proposed shots.
  3. Approve, and it lays the script out as a storyboard on a new Canvas. Open the storyboard takes you there.

If a step fails, it says why, and Resume tries it again. Cancel run stops it. You can close the dialog while it waits and come back to it later. Each run keeps the workflow as it was when the run started, and what every step did.

A workflow’s steps can be extract-script, lay-out-storyboard and approval. A blank workflow starts with one approval step to replace.

A prompt template is run the same way: each time it’s made is a run, keeping its answers and the version it used. A template with steps is a run of several, each made when you choose it.