agentleFS
Sign inStart free
SamRome1SamRome1/showrunner/.claude/skills/brief/SKILL.md

brief

Skill1 starsChanged 2 months agoMITView on GitHub

Fill in a video brief interactively, one section at a time, and save it to docs/briefs/. Use when the user wants to make a new video and has no brief yet, or types /brief.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 71 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Ask for the working title and composition id (PascalCase).

    line 8
  2. Very specific:

    Write the completed brief to docs/briefs/<composition-id>.md, show the user the path, and end with: "Brief saved.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 71 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

Walk the user through docs/VIDEO_BRIEF_TEMPLATE.md one section at a time. Do not write any composition code during this skill.

  1. Ask for the working title and composition id (PascalCase). Read docs/briefs/shortform-openai-postgres.md so your questions carry concrete examples.
  2. Section 0 — Format: canvas size, fps, placement, total duration, whether a VO script exists. If a VO exists, ask them to paste it now; every scene beat must later cite a VO phrase.
  3. Section 1 — Visual system: propose the src/theme.ts defaults as the answer and ask only what changes (accent hex is mandatory and has no default).
  4. Section 2 — Assets: list every real product/company the video will reference and the variant needed (white/color). Do not download anything yet.
  5. Section 4 — Scenes: for each scene ask for name, frame range, beats with timing, exact on-screen text, load-bearing components, sanctioned exceptions. Push back if a scene has no hold, if text isn't exact, or if beats overlap.
  6. Write the completed brief to docs/briefs/<composition-id>.md, show the user the path, and end with: "Brief saved. Next step is the assets batch — say go and I will fetch and verify every logo, then stop for your review."

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.

Check your setup, free