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

build-style

Skill11 starsChanged 22 days agoMITView on GitHub

Builds (or rebuilds) the creator's video editing style from a short interview and 3 to 5 videos they love, so every edit after looks like theirs. Run once before the first edit, or any time they want a new look. Triggers on "/build-style", "build my style", "set up my style", "redo my style", "change my style".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Run the onboarding in .claude/skills/edit-video/references/onboarding.md from the top: the interview, then ./edit study on every reference, …

    line 8
  2. Very specific:

    If my-style/style.md already exists, ask first: start over, or adjust the current style?

    line 10
  3. Distinctive:

    When it's done, tell them: "Your style is saved.

    line 12

≈ “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.

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

/build-style

Run the onboarding in .claude/skills/edit-video/references/onboarding.md from the top: the interview, then ./edit study on every reference, then write my-style/style.md, style.json and feedback.md, then show a sample before the first real edit.

  • If my-style/style.md already exists, ask first: start over, or adjust the current style? Adjusting keeps feedback.md (their past notes stay rules).
  • Learn the thinking, not just the look. For each reference, write down why each choice works (why that beat is full screen, why the face comes back there, what the first frame is doing), not only what it looks like. The style guide should let you make a good call on a line none of the references ever had, so their videos feel like the same creator without all looking identical.
  • When it's done, tell them: "Your style is saved. Give me a video and type /edit-video."

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.