agentleFS
carlosbuelvas1carlosbuelvas1/openclaw-skills/video-to-skill/SKILL.md

video-to-skill

Skill0 starsChanged 6 months agoMITView on GitHub

Runs automatically after youtube-learn saves a note. Reads the note and decides if the video contains a repeatable workflow worth turning into a permanent OpenClaw skill. Drafts the skill and surfaces it for Charlie's approval — never installs without explicit OK.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the most recently saved file in ~/.openclaw/workspace/knowledge/youtube/.

    line 18
  2. Distinctive:

    If NOT skill-worthy → stay completely silent.

    line 34
  3. Very specific:

    If skill-worthy, draft a full SKILL.md using this structure:

    line 38
  4. Very specific:

    Do not install, save, or register anything until Charlie explicitly says to install it.

    line 91
  5. Very specific:

    If approved, save to ~/.openclaw/workspace/skills/[skill-name]/SKILL.md and register it in openclaw.json under skills.entries.

    line 92
  6. Distinctive:

    If the framework needs to be adapted to work as agent instructions, adapt it — don't copy-paste the video's language.

    line 97
  7. Distinctive:

    When you do surface a skill, make it tight.

    line 99

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Video-to-Skill

Runs after youtube-learn completes. Reads the saved note. Makes one decision: is there a repeatable system here worth building into a skill?

Trigger

Automatically after youtube-learn saves a note to ~/.openclaw/workspace/knowledge/youtube/. Can also be triggered manually by Charlie dropping a note path or saying "turn this into a skill."

Workflow

Step 1 — Read the note

Read the most recently saved file in ~/.openclaw/workspace/knowledge/youtube/.

Step 2 — Evaluate: is this skill-worthy?

A video is skill-worthy if it contains at least one of:

  • A repeatable workflow with clear steps
  • A framework Charlie or Elon would apply more than once
  • A system that maps to content creation, trading research, or AI tooling
  • A mental model that should change how the agent responds to a recurring situation

A video is NOT skill-worthy if:

  • It's a one-time news event or market update
  • It's purely motivational with no operational content
  • The insight is already covered by an existing skill
  • The framework is too vague to turn into concrete agent behavior

If NOT skill-worthy → stay completely silent. Do not output anything.

Step 3 — Draft the skill

If skill-worthy, draft a full SKILL.md using this structure:

---
name: [kebab-case-name]
description: [One line — when to trigger this skill and what it does. Be specific.]
---

# [Skill Name]

## Source
Derived from: [video title] — [channel]
Saved note: [path to note]

## When to Use
[Specific trigger conditions — what Charlie says or does that activates this]

## Core Framework
[The actual system from the video, rewritten as agent instructions]
[Steps, rules, or decision tree — make it operational, not descriptive]

## Output Format
[What the agent should produce when this skill runs]

## Charlie-Specific Application
[How this maps to Charlie's world: trading, content creation, or AI tooling]
[Be concrete — not "apply this to your content" but exactly how]

## What to Avoid
[Common misapplications of this framework]
[What the video got wrong or oversimplified, if anything]

Step 4 — Surface for approval

Output exactly this and nothing else:


🧠 NEW SKILL DRAFT — [Skill Name]

Source: [video title] Would activate when: [trigger description]

[paste the full SKILL.md content]


Reply "install it" to add this to your skill library, or "skip" to discard.


Step 5 — Wait for Charlie's approval

Do not install, save, or register anything until Charlie explicitly says to install it. If approved, save to ~/.openclaw/workspace/skills/[skill-name]/SKILL.md and register it in openclaw.json under skills.entries.

Voice

  • The draft should read like a real working skill, not a summary of the video.
  • If the framework needs to be adapted to work as agent instructions, adapt it — don't copy-paste the video's language.
  • Be skeptical. Most videos don't contain skill-worthy systems. Silence is the right output most of the time.
  • When you do surface a skill, make it tight. One sharp skill beats three vague ones.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.