agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/video-use/SKILL.md

video-use

Skill2 starsChanged 2 months agoMITView on GitHub

Edit a supplied video through a source-preserving transcript, timeline and visual review workflow using available rendering tools.

13 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 13 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:

    Use installed tooling with verified command/API grammar.

    line 14

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

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

Edit the supplied video

Inspect the footage and read the user's intent before choosing a treatment. Preserve originals and existing project edits. The brief determines whether this is an interview, montage, tutorial or talking head; do not force all material through one preset.

Record a project note with source files, intended message, chosen output, edits and unresolved decisions. Use a timestamped transcript where speech drives the cut, and inspect visuals at decisions. Transcription/generation services are optional external dependencies with their own costs.

Build an EDL with source ranges and derive the output timeline. Keep exact word context around cuts and maintain mappings for captions, overlays and later revisions. Use shorts-cut, shorts-audio and shorts-motion where relevant.

Use installed tooling with verified command/API grammar; no universal render.py or transcription service is bundled. Generate only the requested assets. Keep intermediate and final renders separate from sources.

Render, inspect and iterate against the brief. Use shorts-qa for applicable final checks. Deliver the export and editable project/EDL with known limitations. Publication and uploads remain separate actions within the user's actual request.

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.