Creating Tasks with Claude

The fastest way to build a task is to let Claude write it. With the InSkill Task Creator skill, Claude turns a service manual, a work instruction, or a plain description of the work into a complete task — every step written, diagrams from the source embedded, data capture built in — that you paste into InSkill in one action.

What You Will Need

• Claude, with the InSkill Task Creator skill enabled
• Your source material: a PDF manual, a work instruction, or a description of the work
• Author access to the copilot in the Copilots portal

How It Works

Give Claude the source and describe the task you want. Claude analyzes the document, chooses the task type — troubleshooting, procedure, or inspection — and maps each logical section of the work to a step: safety warnings first, then preparation, the work itself, and verification. Where the source contains figures or diagrams, Claude extracts them and embeds them directly in the steps. Where the Technician must record data — a reading, a part number, a confirmation — Claude builds the step to save that value with the session, so it appears in the step's data and in Task History.

The output is a single task template plus a summary table of the steps, so you can review the structure before anything touches InSkill.

📘

Note

Claude converts your source — it does not improve on it. Warnings, measurements, and instructions are carried over exactly as written, and nothing is added that is not in the document. Review the summary table against the source before you paste.

Asking Claude

Attach the source and describe the task. Example prompts:

Convert section 4.2 of this maintenance manual into an InSkill procedure.

Build an inspection task from this daily checklist. Pressure and temperature are numeric readings; everything else is a pass or fail condition check.

Create a troubleshooting task for the error codes in chapter 7 of this manual.

The more you tell Claude about how the task will be used — which readings matter, where the flow should branch, what must be photographed — the closer the first draft lands.

What Claude Can Build Into a Task

Conversion is the baseline. The skill can also build interactive behavior into individual steps — ask for these by name:

Presentation carries over from the source too: warnings and cautions become styled alert boxes with their exact original text, figures are embedded in the step where they belong, instructions render as numbered lists, and any parts or required skills named in the source are tagged on the step.

And the behavior around steps is available on request:

• Conditional steps and instructions — shown only when a dependency is met, such as model = 300 or pressure > 50.
• Step behaviors — end the task at a step (Stop Here), exit a subtask early, let a shared subtask run more than once in a session, trigger the copilot's session script, or hide a step from selected user levels.
• Session-aware content — a step can greet the Technician by name, show the asset's serial number, or adapt to the session's language.
• Return-safe steps — a Technician who revisits a step through History finds their earlier entries and photos restored, not a blank form.
• Data stored on the asset — gathered values can be written to asset variables, so the latest readings, hours, or configuration persist on the machine itself beyond the session.
• Email reports — when the task finishes, the results can be emailed as a report to support, a supervisor, or the customer.

Everything Claude builds is ordinary step content — the same HTML a dynamic step uses — so any of it can be refined later in the Task Editor, or changed by telling Claude what to adjust and pasting the corrected step back in.

The Task Template (JSON)

What Claude hands you is a task template — a single block of JSON that describes the whole task. You do not need to write or edit it by hand, but it helps to know what you are pasting:

{
  "name": "Filter Replacement",
  "published": 1,
  "roles": [0, 7, 8, 1, 2, 3, 5],
  "steps": [
    {
      "type": 3,
      "title": "Safety and PPE",
      "body": "…",
      "published": 1,
      "instructions": [],
      "tags": ["web"],
      "parts": [],
      "skills": [],
      "feedback_config": []
    }
  ]
}

• name and steps define the task and its steps, in order.
• type sets each step type: 1 solution, 2 observation, 3 information, 4 subtask. Claude uses information steps for procedure work and solution steps only in troubleshooting branches.
• body is the step's content. For dynamic steps it is an HTML fragment with the data capture built in; the "web" tag tells InSkill to run the step's scripts.
• roles controls who can see the task — Claude includes the default roles, because a task with no roles is invisible to everyone.
• parts and skills carry any parts and required skills named in the source.

The same format is what Copy Task produces in the Task List view, so a task template can also move a task between copilots or accounts.

Pasting the Task into InSkill

Follow these steps to add the task Claude created:

1. Copy the task template Claude produced.
2. In the Copilots portal, select the copilot and open the Tasks tab.
3. Click + Add New, then click Paste Task.
4. Paste the template into the Task Template box and click Save. InSkill creates the task and all of its steps in one action.

To add a single step to an existing task instead, ask Claude for one step and copy it. In the Task Editor, open the vertical ... menu on the step it should follow and select Add New > Paste Step.

Reviewing the Task

Pasted tasks are created published and visible to the default roles, so review the task before Technicians run it:

1. Open the task in the Task Editor and walk through each step against the source document.
2. Run the task once yourself and confirm each observation saves its value — the entries appear with the session in Task History.
3. Adjust anything specific to your operation: dependencies for branching, subtasks for shared sequences, and step visibility on the step's Info tab.
4. Check that InSkill GPT — Searchable is selected in the Task Details view, so InSkill GPT can find the task.

If a step needs a change, the fastest fix is often to tell Claude what to change and paste the corrected step back in.