agentleFS
harshil-1411harshil-1411/claude_plugin_video_studio/skills/stills/SKILL.md

stills

Skill0 starsChanged 48 days agoApache-2.0View on GitHub

Look at chosen moments of a planned video-studio project's HyperFrames scenes (motion pages and every other motion-graphic kind) as a labelled sheet of still frames drawn straight from the composed pages in headless Chrome, before the full render - on every beat or downbeat of the music, at exact times, or in/mid/out - and fix cramped, overlapping, off-grid or unreadable moments. Use when the user runs /video-studio:stills, after writing or editing a motion page, or before a render of a spec with motion scenes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. langchain-ai/design-agent★ 596same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository24 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 3

    Very specific

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

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

    After spec_validate passes and before render_submit, call mcp__plugin_video-studio_engine__stills {project_dir, at: "downbeats"} when the …

    line 20
  2. Distinctive:

    no empty, near-identical or cluttered frames.

    line 32
  3. Very specific:

    After a render, use review with transitions: true to see each transition at its midpoint.

    line 45
  4. Very specific:

    Every motion scene is also checked automatically before it renders: the page is seeked to the same times in a different order and the …

    line 48

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

Stills before the render

stills is not a render. It composes each HyperFrames scene exactly as the renderer does (tokens, safe zones, word cues, the music's beat grid), opens the page in headless Chrome, seeks it to the chosen moments and tiles the frames into review/stills/stills-<quality>[-<scene>].jpg (full-size frames in review/stills/frames/). Nothing in renders/ or dist/ changes and no voice is synthesized, so it takes seconds, not minutes.

Stills and determinism

  1. After spec_validate passes and before render_submit, call mcp__plugin_video-studio_engine__stills {project_dir, at: "downbeats"} when the spec has a music bed (at: "beats" for fast cuts), else {project_dir} (in/mid/out of every scene). Limit to the scenes you changed with scenes: ["s03"]; use times: [0.4, 1.2] (scene-local seconds) for exact moments.
  2. Read every image in images. Each tile is labelled <scene> <moment> <time> (beat 3, bar 2, in/mid/out). Check:
    • text fits, is readable at phone size and is not cramped against an edge;
    • nothing overlaps or sits under captions or the platform UI;
    • each state change lands on its beat or bar (the label says which), and no beat shows a frame that is half-way through nothing;
    • no empty, near-identical or cluttered frames.
  3. Fix the page (motion/*.html) or the spec and run stills again on the changed scenes. Render only when the sheet looks right.

Stills hand each page the same data the render does. That includes the music envelope (vs.energy, vs.bass, vs.onset) of motion pages and, with audio.beat_sync on, the beat-placed reveals of text scenes. So a still at time t matches the render's frame at t. Before the first render, reveals sit on the bed's beats at spec durations (a note says so), and the render can still move cuts.

Transitions are not in stills. Crossfades and other transitions are drawn when the scenes are assembled, and stills draw one scene at a time. After a render, use review with transitions: true to see each transition at its midpoint.

Every motion scene is also checked automatically before it renders: the page is seeked to the same times in a different order and the frames must be identical, else the scene fails with nondeterministic_scene (a clock, unseeded randomness, or state carried between frames: window.seek(t) must rebuild the whole frame from t). With props.loop, the frame at the end must match the first (loop_seam warning). The result is cached until the page changes.

Errors

  • RENDER_LOCKED: a render of this project is running; wait for it (job_status), then run stills.
  • Chrome or the producer missing: run doctor; the render can still fall back to ffmpeg, but stills need Chrome.
  • stills at downbeats: this project has no beat grid: there is no music bed (or no clear beat); use times or count.
  • A scene in skipped (footage, provider scenes, a motion page the lint refuses): fix what the reason says, or review it after the render with the review skill.

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.