Index of every page on this site: llms.txt
All skills
matisolina avatar

/learn-from-demonstration

@3dd91e1
by Mati Solinamatisolina/busy98 stars
14
Run it yourself

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.

  • 1 file
  • 2 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/matisolina/busy/learn-from-demonstration

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈63 tokens for metadata: the name and description. ≈431 when used: this file.

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈253 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 3dd91e1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for matisolina/busy/learn-from-demonstration