Skip to main content

Turn a recording into an SOP, a lab, or documentation

Once a recording is approved, download its bundle and give it to an AI agent. The console writes the prompt for you, to build a reusable skill, a written procedure, a lab exercise, or an audit.

Once a recording is approved, download its bundle and give it to an AI agent. The console writes the prompt for you, to build a reusable skill, a written procedure, a lab exercise, or an audit.

Before you start

The download page

The recording download page with its summary, buttons and example prompt numbered 1 to 7

  1. The status: Ready to download.

  2. The system, when it was recorded, its duration, the number of events, the bundle size, and when it expires.

  3. Download bundle.

  4. Edit again: reopens the review.

  5. Delete.

  6. Example prompt: choose what you want the agent to make.

  7. The prompt, ready to copy.

NOTE: The bundle expires, and the page shows when. Download anything you want to keep.

Step 1 - Download the bundle

Click Download bundle. It's a zip file.

Step 2 - Choose what to make

Under Example prompt, choose:

  • Create an AI skill: a reusable skill that performs the task with the hv CLI. The agent then tests it by replaying the task.

  • Have AI create instructions or an SOP: a written procedure for a person to follow.

  • Create lab exercise instructions: a training exercise based on the task.

  • Have an AI audit a live user: a review of how the task was carried out.

Step 3 - Give it to your agent

  1. Click the copy button next to the prompt.

  2. Paste the prompt into your AI agent, with the zip attached or saved next to it.

The prompt is plain text, so edit it to say exactly what you want.

What's in the bundle

  • meta.json: the recording's details: duration, screen layout, and how many events and screenshots it has.

  • events.jsonl: one line per step: each click with the control it hit, typed text, scrolls and window changes.

  • screenshots/: the screenshots each step refers to.

  • transcript.json: your narration, with timings.

Because each click records the control it hit by name, an agent can find the same control on another system even if the screen looks different.

Getting a good result

  • Test a skill on a spare system first. A recording made on one machine may depend on something that isn't true on others.

  • Record one task per recording. Two tasks in one bundle give you a skill that always does both.

  • Narrate why, not what. The steps already record what you clicked.

Related articles

Did this answer your question?