agentleFS
45ck45ck/video-evaluator/skills/source-media-signals/SKILL.md

source-media-signals

Skill2 starsChanged 7 months agoMITView on GitHub

Collect first-pass source media facts, audio silence/energy, shot estimates, representative frame status, and persistent text/caption risk evidence.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when an agent needs conservative source-video signals before deeper review.

    line 8

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

Source Media Signals

Use this when an agent needs conservative source-video signals before deeper review. This skill is intended as an intake layer, not a semantic video understanding pass.

This skill owns:

  • ffprobe facts through the existing media probe
  • audio energy and silence signals through ffmpeg when available
  • coarse shot and scene estimates through video-shots when possible
  • representative frame evidence status
  • persistent text/caption risk evidence from nearby OCR/layout artifacts when present
  • deterministic frame/video fallback evidence when OCR/layout artifacts are absent

Inputs

Required:

{
  "videoPath": "./output/example-run/output.mp4"
}

Optional fields:

  • outputDir: directory for source-media.signals.json; defaults next to the video.
  • outputPath: exact JSON output path.
  • sceneThreshold: ffmpeg scene-change threshold, default 0.08.
  • minShotDurationSeconds: minimum shot duration, default 0.5.
  • extractRepresentativeFrames: whether to write video-shots/shot-*.jpg, default true.
  • runAudioSignals: whether to run ffmpeg audio analysis, default true.
  • runVideoShots: whether to run shot analysis, default true.
  • silenceNoiseDb: silence threshold, default -35.
  • silenceMinDurationSeconds: minimum silence duration, default 0.25.

Outputs

The result contains manifestPath and manifest. The manifest is source-media-signals.v1 and writes:

  • ffprobe.status and normalized media facts
  • audio.status, volume fields, and silence segments
  • video.status, shot counts, boundaries, and scene-estimate metadata
  • representativeFrames.status and frame paths when available
  • textRisk.status, riskLevel, metrics, artifact paths, and bounded evidence items for visible source text, caption/bottom text, layout text issues, or deterministic frame/video fallback signals.

Interpretation Notes

Evidence status is part of the output contract. Treat unavailable, failed, and skipped as abstention signals, not as proof that a risk is absent. When OCR/layout artifacts are unavailable, textRisk.evidence still records fallback frame/video signals so downstream guards can persist why the text risk decision was conservative.

Repo-side runner:

node --import tsx scripts/harness/source-media-signals.ts

Installed-pack runner:

node ./.video-evaluator/agent/run-tool.mjs source-media-signals

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.