reviewing-ffmpeg-skill-changes SKILL.md skillA
reviewing-ffmpeg-skill-changes from kajisho5/ffmpeg-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kajisho5/ffmpeg-skill/reviewing-ffmpeg-skill-changes@git:20261031.1dc2f52Pins git:20261031.1dc2f52 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kajisho5/ffmpeg-skill
- Path
.claude/skills/code-review/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261031.1dc2f52, committed Oct 31, 2026
- First version recorded
- Sep 22, 2026
- Size
- 9,074 bytes
- Repository stars
- 4,815
- License
- MIT
Review a change to the ffmpeg-skill repository for the failures its own contract makes possible — a claim in a result document that is true at one layer and false at the layer a caller reads, a new flag that reaches the code but not the contract/docs/demo surfaces, a "bug" that docs/design-decisions.md already decided with a pinning test, a fix with no regression test, a new runtime dependency or a raw ffmpeg shell call that breaks the scope boundary, a SKILL.md line added without one trimmed…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Reviewing ffmpeg-skill Changes This repository has an unusual failure mode, and a review that misses it looks thorough while catching nothing. The product is a **JSON result document** that an agent reads instead of watching the video. A change can be correct at the FFmpeg layer, correct at the Python layer, and still ship a lie at the layer that matters: `status: "completed"` next to a non-zero exit, `verified: true` for something the tool never measured, a cut described as lossless when the keyframe snap moved it 1.24 s. The 0.9.1/0.10.0 "honesty fix" (`cut.py`'s `mode` / `keyframe_snapped` / `duration_delta_seconds`, `check.py`'s `reason`, `render.py`'s check-stage exit code) exists because three such claims shipped and were caught after the fact. **Review the claim, not just the code.** The second failure mode is re-reporting decisions. Three review rounds on 2026-09-12 re-reported entries in `docs/design-decisions.md`, which is why that file exists. ## Establish the review base first Read the tree at the commit under review, not a summary of it and not your own working copy if it has moved. ```bash git fetch origin && git log --oneline -1 origin/main …
Read the whole file at its exact version.
How to install
mdr add kajisho5/ffmpeg-skill/reviewing-ffmpeg-skill-changes@sha256:c38d78a73b82b81aThe line at the top of this page pins the label git:20261031.1dc2f52, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qxcrlucwldcmoq2i)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 22, 2026 and Oct 31, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261031.1dc2f52 latest | 2026-10-31 | 1dc2f52 | 9,074 B | A | view · diff |
| git:20260922.1a77112 | 2026-09-22 | 1a77112 | 9,078 B | A | view · diff |
| git:20260922.abb41e3 | 2026-09-22 | abb41e3 | 9,034 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9074 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kajisho5/ffmpeg-skill · 4,815 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qxcrlucwldcmoq2i GET https://markdownregistry.com/api/v1/resolve?ref=kajisho5/ffmpeg-skill/reviewing-ffmpeg-skill-changes GET https://markdownregistry.com/api/v1/blob/c38d78a73b82b81a28dd56c9d6e163fdd34d0cd01bc2af4cd627be9b310bce36
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.