agentleFS
TakeOff-TeamTakeOff-Team/claude-shortform-video-editor/.claude/skills/captions/SKILL.md

captions

Skill11 starsChanged 21 days agoMITView on GitHub

Adds word-by-word captions to a talking-head video, spelled right, in the creator's caption style, with no other graphics. Clips raw footage first if it needs it. Triggers on "/captions", "caption this", "add captions", "subtitle this video".

11 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Ask for the video (and script, optional).

    line 9

“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

/captions

  1. ./edit doctor. If my-style/style.json doesn't exist, ask two quick questions instead of a full onboarding: caption look (clean pill, bold outline TikTok style, plain, highlighted active word) and colour/font if they have one. Run ./edit new-style and set just captions, fonts.caption, colors.captionText / captionBg / accent and vocabulary (names and brands they say). They can run /build-style later for the full look.
  2. Ask for the video (and script, optional). ./edit new <slug> "<video>" [script.txt].
  3. Already edited → ./edit precut <slug>. Raw (retakes, long pauses) → ask if they want it clipped first; if yes, follow .claude/skills/edit-video/references/clipping.md.
  4. ./edit captions <slug>. Read every word against the script / what they meant; fix mishearings in projects/<slug>/caption_fixes.json and run it again. Spelling has to be perfect.
  5. ./edit face <slug>, then write projects/<slug>/edit.json with faceCenter and one face beat per sentence (no panels). Face beats alternate wide and punched-in automatically, which keeps a captions-only video moving.
  6. ./edit render <slug> then ./edit qa <slug> (check every caption is inside the safe zone and spelled right). Send the file.
  7. Log any note in my-style/feedback.md; lasting caption preferences go in style.json.

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.