agentleFS
raphaelbgrraphaelbgr/ai-video-prompting/skills/veo-prompt-lint/SKILL.md

veo-prompt-lint

Skill0 starsChanged 2 months agoMITView on GitHub

Use before submitting a Veo prompt or a batch of clip prompts, and when a generated clip came back with unwanted speech, the wrong camera motion, ignored references, or a wrong environment after a cut. Runs a regex linter over prompt text and proposes rewrites for the gotchas that recur every episode. Triggers on "lint veo prompt", "check this veo prompt", "veo prompt review".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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. Distinctive:

    Run the linter on the prompt or batch.

    line 56
  2. Distinctive:

    Run each one through the linter.

    line 72
  3. Very specific:

    If a pattern is wrong, edit the corresponding _*_RE / _REF_PATTERNS in scripts/veo_lint.py and repeat steps 2–3 until your known-good and …

    line 76
  4. Distinctive:

    Write down the known blind spots, so future-you reads the WARNs with the right scepticism.

    line 79
  5. Very specific:

    Add a clear Dialogue: label, or accept the WARN.

    line 85

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

Veo prompt lint — screen before you spend

A regex-based linter that catches the Veo prompt mistakes that recur on every production. It is a heuristic, not a parser — it nudges, it does not guarantee. The point is to catch a 15-credit mistake before you pay for it.

Script: scripts/veo_lint.py — stdlib only, Python 3.8+.


Rules

IDTriggerWhy it bitesFix
R1aA silent / non-dialogue clip that has an Audio language: <X> lineThe explicit language directive forces Veo to generate unwanted speechDelete the language line; add No dialogue - ambient sound only
R1bA non-dialogue clip with no explicit silence directiveVeo defaults to English speech and invents linesAdd No dialogue - ambient sound and SFX only — and never an Audio language: line
R2LOCKED TRIPOD / locked-tripodMisread; Veo adds motion anyway, and sometimes renders a literal tripodUse static shot (optionally static shot, no camera movement)
R3More than 3 reference images / ingredientsVeo supports at most 3; the extras are silently ignoredReduce to ≤3; merge, or split across shots
R4An environment transition (door, hallway, room change) with no Extend from prior clipVeo guesses the destination environment, usually wrongAdd Extend from prior clip. and describe the destination

The rule logic, patterns and exact rewrite text live in scripts/veo_lint.py — that file is the single source of truth. Tune the patterns there, not in this table.


Usage

# a single prompt string
python scripts/veo_lint.py "your prompt text"

# a prompt file
python scripts/veo_lint.py path/to/clip07.txt

# a batch: blank-line-separated blocks, or a JSON array / JSONL of {"id","prompt"}
python scripts/veo_lint.py path/to/episode_prompts.txt

# machine-readable
python scripts/veo_lint.py prompts.json --json

# pipe
cat prompt.txt | python scripts/veo_lint.py --stdin

Exit code: 0 = clean · 1 = at least one violation.


How to apply it

  1. Run the linter on the prompt or batch.
  2. For each violation, apply the suggested rewrite — or justify keeping it (e.g. the clip genuinely has dialogue the regex missed).
  3. Re-run until clean, or until only knowingly-accepted WARNs remain.
  4. Report ERRORs vs WARNs separately. ERRORs (R1a, R2, R3) almost always need fixing; WARNs (R1b, R4) need a judgment call.

Calibrate it before you trust it

These are heuristics with expected false positives and negatives. Before running it on a real production:

  1. Pick 4–6 of your own past prompts — a mix: a silent clip, a dialogue clip, a continuity/transition clip, a multi-reference clip.
  2. Run each one through the linter.
  3. For every flag, confirm the rule actually applied (true positive) versus misfired (false positive). For every prompt you know had a problem, confirm it was flagged (catch the false negatives).
  4. If a pattern is wrong, edit the corresponding _*_RE / _REF_PATTERNS in scripts/veo_lint.py and repeat steps 2–3 until your known-good and known-bad prompts classify correctly.
  5. Write down the known blind spots, so future-you reads the WARNs with the right scepticism.

Known false positives

  • A dialogue clip whose lines are phrased without says: / dialogue: → R1b misfires. Add a clear Dialogue: label, or accept the WARN.
  • "door" used metaphorically rather than as a real environment change → dismiss R4.
  • A prompt listing four nouns that are not actually reference ingredients → R3 over-counts. Check the actual reference panel.

What it does not check

The linter is text-shaped, so it cannot see the things that need a human or another pass: continuity between clips (multiclip-continuity), whether the framing matches the emotional beat (cinematography), or whether the prompt will trip a content filter (docs/content-filters-and-policy.md). Run those separately.

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.