agentleFS
krusemediallckrusemediallc/video-editor-agent/.claude/skills/hook-variations/SKILL.md

hook-variations

Skill168 starsChanged 5 days agoNo licenceView on GitHub

Combine ONE finished body cut with MANY hook clips to produce one standalone video per hook — the hook A/B batch you upload as separate ad creatives. Use whenever someone wants to "add all these hooks to this body", "combine this video with every hook in that folder", "make 21 versions with different openers", "swap the hook", "build hook variants", "test these hooks against the same body", or hands over one body file plus a folder of hooks and expects N finished videos out. Also use for the same shape with different words: intro variants, opener tests, cold-open A/B sets, or re-running an existing variant batch against a NEW cut of the body. Joins losslessly (body frames stay bit-identical), matches hook loudness to the body so the seam does not jump, and verifies with AVFoundation because an ffmpeg-only check cannot catch the parameter-set freeze that makes these files play fine in ffmpeg and stall in QuickTime. Do NOT use for editing a single video, adding captions, or cutting the hooks themselves out of a longer recording.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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.