agentleFS
marciobmarciob/youtube-research/SKILL.md

youtube-research

Skill1 starsChanged 3 months agoNo licenceView on GitHub

Research and learn any topic from YouTube. Use when the user wants to understand, study, or get up to speed on a subject using video content — e.g. "what does YouTube say about X", "learn/research X from videos", "summarize the best videos on X", "find and explain a tutorial/talk/interview about X". Searches for relevant videos, pulls their transcripts, and synthesizes an answer with citations and timestamps. Also handles narrow requests: find videos by keyword/channel, or get the transcript of a single YouTube URL or video ID. Supports filtering the search by upload date ("only videos from this year", "since March 2025").

  • Installs packages

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instagram-research, tiktok-research and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bradautomatesSkill

    instagram-research

    Research high-performing Instagram content (posts and reels) from tracked accounts using Apify's Instagram Scraper. Identifies outlier content, analyzes top 5 videos with AI, and generates reports with actionable hook formulas.

    Also in 3 projects that use this

  • bradautomatesSkill

    tiktok-research

    Research high-performing TikTok videos from tracked accounts using Apify's TikTok Scraper. Identifies outlier content, analyzes top 5 videos with AI, and generates reports with actionable hook formulas.

    Also in 3 projects that use this

  • +1 more from bradautomates

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 13 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.

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.