video-to-skill
Original:🇺🇸 English
Translated
Watch a tutorial, demo, or walkthrough video and generate a Claude Code skill from it. Extracts the workflow, commands, tools, and patterns demonstrated and produces a SKILL.md with implementation. Supports Loom, YouTube, and local files.
8installs
Sourcemnvsk97/eyeroll
Added on
NPX Install
npx skill4agent add mnvsk97/eyeroll video-to-skillTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Video to Skill
Watch a tutorial, demo, or walkthrough video and generate a Claude Code skill from it.
What This Skill Does
Given a video demonstrating a workflow, tool, or technique, this skill:
- Analyzes the video to understand what's being demonstrated (via )
eyeroll watch - Extracts: commands run, tools used, patterns followed, workflow steps
- Identifies the core capability being shown
- Generates a SKILL.md following the agent skills specification
- Optionally scaffolds implementation scripts
Setup
bash
pip install eyeroll
eyeroll init # set up Gemini API key
brew install yt-dlp # for URL downloadsOr:
export GEMINI_API_KEY=your-keyWhen To Use This Skill
- User shares a video and says "create a skill from this"
- User shares a tutorial and wants to automate the workflow shown
- User says "watch this and make it into a skill/plugin/command"
- User shares a demo of a tool and wants a Claude Code skill that replicates it
- User wants to turn a screen recording of a manual process into an automated skill
Workflow
1. Run: eyeroll watch <source> --context "create a skill from this" --verbose
2. Read the structured notes — identify:
- What workflow/process is demonstrated
- What commands/tools are used
- What inputs does it take
- What outputs does it produce
- What are the trigger phrases (when should this skill activate)
3. Design the skill:
- Name: concise, lowercase, hyphenated
- Description: what it does and when to trigger
- Instructions: step-by-step agent instructions
- Setup: any dependencies or env vars needed
4. Generate SKILL.md following the agent skills spec
5. If the skill needs scripts, scaffold them
6. Validate: does the SKILL.md make sense? Are instructions clear?Example Interactions
User: "Watch this video on how to deploy to Fly.io and make a skill"
Steps:
eyeroll watch <url> --context "create a deployment skill for Fly.io"- Notes show: user runs , configures settings, runs
fly launch, checks statusfly deploy - Generate skill:
- Name:
fly-deploy - Trigger: user asks to deploy, mentions Fly.io
- Instructions: check for fly.toml, run fly deploy, verify health
- Setup: requires CLI
flyctl
- Name:
- Write
skills/fly-deploy/SKILL.md
User: "Turn this Loom into a skill for our release process"
Steps:
eyeroll watch <loom-url> --context "create a skill for our release process"- Notes show: user bumps version, updates changelog, creates tag, pushes, creates GH release
- Generate skill that automates the full release workflow
User: "Watch how I set up a new microservice and make it repeatable"
Steps:
eyeroll watch <video>- Notes show: user creates directory, copies template, updates config, registers in service mesh
- Generate a scaffolding skill that automates new service creation
Rules
- Always run first to understand the full workflow before generating the skill.
eyeroll watch - Follow the agent skills specification for SKILL.md format:
- : max 64 chars, lowercase, hyphens only
name - : max 1024 chars, describes what AND when
description - Body: clear instructions an agent can follow
- Keep SKILL.md under 500 lines. Move detailed reference material to separate files.
- The generated skill should be self-contained — an agent reading only the SKILL.md should understand what to do.
- Include example interactions showing realistic trigger phrases.
- Include setup instructions for any dependencies.
- If the video shows a complex multi-step process, break it into clear numbered steps.
- Ask the user to review the generated skill before finalizing — the video interpretation may miss nuances.
SKILL.md Template
markdown
---
name: {skill-name}
description: >
{What this skill does and when to use it.}
---
# {Skill Name}
{One-liner description.}
## What This Skill Does
{2-3 sentences explaining the capability.}
## Setup
{Dependencies, env vars, installation steps.}
## When To Use This Skill
{Bullet list of trigger conditions.}
## Workflow
{Numbered steps the agent should follow.}
## Example Interactions
{2-3 realistic examples with user input and expected agent actions.}
## Rules
{Guardrails and constraints.}