agentsclimarketplace

Visual director gate

Skill tars1230/evidence-video-factory/skills/visual-director-gate

Review and improve AI workflow videos as a visual director. Use when planning, redesigning, proxy-reviewing, or final-gating narrated Remotion videos, tutorial videos, Skill demos, evidence videos, or account-branded video episodes where visual communication, first-frame impact, typography hierarchy, UI focus, motion purpose, and improvement over the previous episode must be judged and scored.From its SKILL.md

Install
npx -y skills add tars1230/evidence-video-factory --skill visual-director-gate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.9 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Visual Director Gate

Use this skill after the story is clear and before final render approval. It does not enforce one fixed style. It enforces a stronger visual communication standard for each new video.

Required Inputs

Prefer these artifacts:

  • current episode.json;
  • first-frame or cover still;
  • scene contact sheet;
  • caption-midpoint contact sheet;
  • raw key frames for important UI actions;
  • previous published episode first-frame and scene sheet, when available.

If artifacts are missing, stop and generate the cheapest missing artifact first. Do not approve final render from memory.

Review Order

  1. Read references/account-visual-brief.md.
  2. Run the score script on available artifacts:
python3 skills/visual-director-gate/scripts/score_video_artifacts.py \
  --episode-json /path/to/episode.json \
  --first-frame /path/to/first-frame.png \
  --scene-sheet /path/to/scene-sheet.png \
  --caption-sheet /path/to/caption-sheet.png \
  --previous-scene-sheet /path/to/previous-scene-sheet.png \
  --out /path/to/visual-gate-report.md

For a first episode with no baseline, add --first-episode. Otherwise the previous scene sheet is mandatory.

  1. Inspect the actual images. Fill or amend the report with visual scores.
  2. If the score is below the gate threshold, revise the visual direction before rendering final.

Scorecard

Use 100 points. Passing threshold is 82. A video below 70 is a redesign, not a polish pass.

  • First-frame memory: 20
    • 0-8: topic visible but no memorable claim or asset;
    • 9-15: claim is readable but visual identity is generic;
    • 16-20: one-second silent frame clearly communicates topic, creator asset, and why it matters.
  • Information hierarchy: 20
    • 0-8: screenshots or captions compete without a dominant reading order;
    • 9-15: main action is understandable after listening;
    • 16-20: the eye knows what to read or click first in every scene midpoint.
  • UI focus and magnification: 15
    • 0-5: key UI is merely present;
    • 6-11: key UI is enlarged but not always centered or timed;
    • 12-15: each critical click/copy/input target becomes the unique focal point, normally at least 20% of frame width or with an unmistakable pointer.
  • Motion purpose: 15
    • 0-5: movement is decorative;
    • 6-11: movement creates energy but not always attention;
    • 12-15: push, pan, cursor, wipe, or reveal changes the viewer's understanding.
  • Caption discipline: 10
    • 0-3: captions explain what the picture failed to show;
    • 4-7: captions are short but sometimes carry the main action alone;
    • 8-10: captions label and reinforce what is already visually obvious.
  • Evidence and privacy: 10
    • 0-3: fake UI, unclear proof, or privacy risk;
    • 4-7: real assets are present but proof/privacy is uneven;
    • 8-10: real artifacts are visible, sensitive data is masked, and evidence does not distract.
  • Progress over prior episode: 10
    • 0-3: weaker or merely different;
    • 4-7: comparable, with one clear improvement;
    • 8-10: visibly more precise, memorable, or mature than the chosen baseline.

Blocking Rules

Block final approval when any item is true:

  • first frame cannot be understood silently within one second;
  • title, narration hook, and first visual imply different promises;
  • a critical UI click/copy/input target is not visually findable within two seconds;
  • captions are the only place the viewer can understand the main action;
  • text overlaps, clips, or looks smaller than the scene's purpose allows;
  • a privacy-sensitive token, cookie, account identifier, or personal field is exposed;
  • final scene sheet is visually weaker than the approved proxy or previous published baseline without a deliberate reason.

Design Bias

Prefer:

  • large claims and step labels paired with real UI evidence;
  • one focal target per shot;
  • local zoom, crop, cursor, and micro-labels over broad boxes;
  • motion that carries attention from old state to new state;
  • fewer visual objects with stronger hierarchy;
  • visible improvement over the prior episode rather than strict sameness.

Avoid:

  • screenshot collage without a dominant message;
  • decorative movement that does not clarify anything;
  • tiny UI shown only for authenticity;
  • overusing callout boxes after the user has rejected broad selection frames;
  • explaining boundaries that are not part of the core viewer task.

Output

Every visual gate pass should produce a short report with:

  • score by category;
  • pass/fail decision;
  • top three visual weaknesses;
  • required edits before final, if any;
  • evidence paths inspected.

What ships with it: 3 files

9.2 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Gives 0 of the 12 instructions most video audio skills give in ~1.1k tokens

Counted across 622 of the 795 authors here whose files we hold, read 2026-08-07

  • Read individual rule files for detailed explanationsin 21 of 622, across 10 files
  • Render final videoin 13 of 622, across 6 files
  • Use WAV PCM 16kHz mono audio formatin 12 of 622, across 3 files
  • Use this skill when dealing with Remotion codein 11 of 622, across 4 files
  • Save generated audio to a WAV filein 11 of 622, across 4 files
  • Handle conversion errors gracefullyin 10 of 622, across 6 files
  • Add captions to videos alwaysin 10 of 622, across 4 files
  • Generate music from text descriptions using MusicGenin 9 of 622, across 2 files
  • Do not skip pipeline layersin 9 of 622, across 3 files
  • Do not make one tool do everythingin 9 of 622, across 3 files
  • Use Azure Document Intelligence for complex PDFsin 9 of 622, across 4 files
  • Never ask the user to paste their full API keyin 9 of 622, across 3 files

Said here and by no other author read

  • generate missing artifacts before approval
  • read the account visual brief
  • run the score script on available artifacts
  • inspect actual images manually
  • revise visual direction if score is below threshold
  • block final approval when blocking rules apply

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.