agentleFS
ahmedsakriahmedsakri/youtube-agent-pro/skills/yt-shorts/SKILL.md

yt-shorts

Skill1 starsChanged 38 days agoMITView on GitHub

Find the Shorts hiding inside a long video and write them, using the transcript to pick self-contained moments. Use for "cut this into shorts", "clip this", "repurpose this video", "what should I clip".

8 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.

    line 11
  2. Distinctive:

    Read the timestamped transcript and inspect footage when available.

    line 19
  3. Distinctive:

    A self-contained first line: Prefer a usable existing line for a footage-only edit.

    line 32

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

yt-shorts

Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.

A Short cut out of a long video is not a clip of the best moment. It is a moment that survives without the video around it, which is a much smaller set.

Picking

Read the timestamped transcript and inspect footage when available. Select self-contained spans for the requested duration (20–55 seconds is a useful starting range, not a platform limit). Verify current Shorts eligibility if the requested length or aspect ratio depends on it. All three should be true:

  1. It opens on a complete thought. If the first sentence needs the previous minute, it is not a Short.
  2. There is a turn in it - a claim, then something that complicates or proves it.
  3. It ends on a line, not a trail-off.

Rank the candidates and show the user the top five with their timecodes and first line, so they can reject one without reading the whole transcript.

Writing each one

  • A self-contained first line. Prefer a usable existing line for a footage-only edit. If a new hook helps, label it as a proposed voiceover or rerecording, not a quote from the footage. Run candidates through the sibling ../yt-script/hookscore.py using its resolved absolute path.
  • On-screen text for the first two seconds, different words from the spoken line.
  • A loop point: what the last line sets up so the first line answers it.
  • Vertical framing note - what gets cropped out of a 16:9 frame and whether that matters.

Deliverable

Return start/end timecodes, original source lines, proposed recording changes, captions, and crop notes. Without timestamped source material, mark timings as estimates. These are clip plans; claim a finished Short only after a separate media tool has exported and verified it. Keep text clear of the platform's interface overlays and check the portrait composition on an actual frame.

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.