agentleFS
badgidsbadgids/Story-Film-Skills/skills/delivery-qc/SKILL.md

delivery-qc

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Probe finished film, trailer, social, and audio deliverables against explicit delivery specifications for file existence, streams, codecs, resolution, frame rate, duration, audio properties, checksums, and optional signal warnings.

2 other projects use a version of this.

Adopted by

Most recently taken up by

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. Very specific:

    Read ../../references/RELEASE_DELIVERY.md and the relevant delivery specification.

    line 13
  2. Very specific:

    Use scripts/delivery_qc.py to inspect actual files.

    line 14
  3. Distinctive:

    Treat missing required files, unreadable containers, missing required streams, or specification mismatches as blockers.

    line 15
  4. Distinctive:

    Treat optional black/freeze detectors as evidence and warnings unless a project rule makes them blocking.

    line 16
  5. Distinctive:

    Never infer QC from a successful generation command alone.

    line 18

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

Delivery QC

Workflow

  1. Read ../../references/RELEASE_DELIVERY.md and the relevant delivery specification.
  2. Use scripts/delivery_qc.py to inspect actual files.
  3. Treat missing required files, unreadable containers, missing required streams, or specification mismatches as blockers.
  4. Treat optional black/freeze detectors as evidence and warnings unless a project rule makes them blocking.
  5. Record SHA-256 for every final deliverable.
  6. Never infer QC from a successful generation command alone.

Done

Each final media deliverable has an evidence-backed QC report and checksum.

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.