agentleFS
neomjsneomjs/neo-agent-skills/.agents/skills/video-create/SKILL.md

video-create

Skill11 starsChanged todayMITView on GitHub

End-to-end workflow for narrated product films, demos, and campaign videos; use when planning, producing, revising, or delivering a video deliverable (not isolated images, media conversion, or app testing).

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

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Read references/native-display-capture.md only when a claim requires popup/multi-page or native-desktop evidence.

    line 10
  2. Distinctive:

    Keep mechanics with their owning skill, app, provider, or platform.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Video Create

For an end-to-end film (binding claims, app choreography, voice, capture, composition, QA, publication, and artifact lineage; ANTI-trigger: isolated image generation, standalone media conversion, or app testing with no film deliverable), first read and strictly follow references/video-create-workflow.md, then copy assets/video-project-record-template.md into an owner-private, gitignored production root as the production authority.

Read references/native-display-capture.md only when a claim requires popup/multi-page or native-desktop evidence; page-only capture does not load it.

Keep mechanics with their owning skill, app, provider, or platform. This skill owns phase order, receipts, evidence-class admission, invalidation/resume, and artifact promotion—not a provider adapter, compositor, capture tool, schema, or universal scene runner.

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.