Creating Tasks with the Task Editor

The Task Editor is where tasks are authored and refined, in the Tasks tab of a copilot in the Copilots portal. Every task passes through it — whether you build it by hand or start from a task created with Claude and adjust it here.

This section walks through building a task the way you would in practice, one page per stage.

The Authoring Flow

Creating a Task — add the task in the Task List view and set who sees it.
Adding Steps — outline the work as a tree of steps, and use the step menu.
Choosing the Step Type — information, observation, solution, or subtask, and how observations collect data.
Adding Step Instructions — fill each step with text, images, resources, and links.
Dynamic Steps — author a step's body directly with Markdown or HTML.
Branching and Subtasks — split the flow on what the Technician observes, and reuse shared sequences.
Configuring Step Attributes — the behaviors and metadata that control a step.

Scripts

Tasks connect to the world beyond the session through scripts:

Any step can run one. Enable Trigger script on the step's Info tab, and the script runs when the step completes.
Every task has two automatic hooks. A script can run at the start of a task — to gather data from IoT, a historian, or another external system before the first step — and when the session finishes, to act on everything that was collected.
Typical script work: compare the collected readings to setpoints on the asset, store gathered values in asset variables so they persist on the machine, email a report of the results, or send the record to a CMMS or other external system.

Scripts are developed on the Copilot Settings page. See Scripts for the editor, and the scripting reference for the full API.

The Views of the Task Editor

The icons down the left edge of the Task Editor switch between its views. The flow above touches each view as it needs it, and each view has its own page with the full detail:

View	What it is for
Task List View	The Tasks tab: create, reorder, search, publish, and set visibility on a copilot's tasks.
Authoring View	The editing workspace: the step tree and the selected step's Content, Data, and Info tabs.
Task Details	A task's settings — user levels, published and visible states, dependencies, and whether InSkill GPT can find it.
Step Explorer	A table of every step in a task, with columns for content, feedback, dependencies, tags, and more.
Observations	The Observations viewer, where photo observation processors are built to read data from pictures.

The + icon opens the new task form, and the gear at the bottom opens Browser Settings, where you set the editor's font size.