---
name: learn-from-demonstration
description: Use when the user recorded a demonstration on your screen (the hub's Teach button saves it under /data/demos/<id>/) and asks you to learn it. Turns the frames and URL log into a reusable skill and offers it with propose_skill.
title: learn-from-demonstration
canonical_url: https://skilld.dev/gh/matisolina/busy/learn-from-demonstration
last_updated: 2026-11-12T03:00:58.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install matisolina/busy/learn-from-demonstration`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/learn-from-demonstration`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/matisolina/busy/learn-from-demonstration) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/learn-from-demonstration`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/learn-from-demonstration --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/learn-from-demonstration --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Learn from a demonstration

The user did a task on your screen while you watched. The hub saved what happened in `/data/demos/<id>/`:

- `NNNN.png`: a screenshot every ~2 seconds, only when the screen changed. File names are in order.
- `log.jsonl`: one line per frame, `{"t": <ms since start>, "frame": "NNNN.png", "url": "<Chrome's URL or null>"}`.

## Steps

1. Read `log.jsonl` first. The URL changes tell you which sites and pages the task went through and roughly where each step starts.
2. Look at a sample of frames with `read_file`: the first and last, and the frames around each URL change or long pause. Don't read every frame. A frame over 3 MB doesn't show: shrink it into a separate file first (for example Python/Pillow) and read that one.
3. Work out the goal (what the user wanted done) and the steps that got there: where they went, what they clicked, what they typed and what they checked before moving on.
4. If a step is unclear (why they picked one option, where a value came from, whether a step is always needed), ask the user one short question with what you saw. Don't guess.
5. Write the skill so a fresh run can follow it from scratch:
   - Steps in order, each with what to look for on the page, not screen coordinates.
   - Values that change each time (dates, amounts, names, files) become inputs the user gives or you work out, with how to find them.
   - No passwords, codes, card numbers or other secrets, and no one-off values from this recording. Where a login or sensitive field comes up, say to use `request_form` or `request_login`.
   - How to tell it worked.
6. Call `propose_skill` with it. The user saves it or not.

Don't redo the task while learning it unless the user asks.
