example-skill
This file is not generated - it is a small, hand-written illustration of what a yt2skill output looks like, so you know the shape before you run the tool.
A real generated SKILL.md has two parts:
Frontmatter (the
---block above).nameis the slug.descriptionis the one line a session sees before it decides to load the skill, so it names the trigger and the task, not just the topic. "Reach for this when you need to X" beats "About X".The body: what the thing is, then a procedure written as concrete actions the agent takes - real commands, real paths, real values. It never says "the video shows..."; it just gives the instruction, as if the author had learned the method and written it down.
Example procedure
Say the source video demonstrated setting up a nightly database backup. The generated skill would read something like:
Create the backup script at
/opt/backups/pg-backup.sh:#!/usr/bin/env bash set -euo pipefail pg_dump -Fc mydb > "/opt/backups/mydb-$(date +%F).dump" find /opt/backups -name 'mydb-*.dump' -mtime +14 -deleteMake it executable:
chmod +x /opt/backups/pg-backup.sh.Add the cron entry (runs 02:30 nightly):
30 2 * * * /opt/backups/pg-backup.sh
Note the exact retention window (14 days) and the exact time (02:30) - those numbers are the product. A generated skill transcribes them precisely from the transcript or a frame, and flags any it could not read rather than guessing.
Bulky detail (full config tables, option lists, edge cases) would go in a sibling
reference.md, keeping this file short enough to load and act on.