media-preservation · git:20260905.c61cda3 · 2026-09-05 · sha256 9b072b7ea54539e6
media-preservation git:20260905.c61cda3A
Immutable. This exact content never changes and is served at /api/v1/blob/9b072b7ea54539e6.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_u2yw2s7mykgz5bs2/9b072b7ea54539e61877d929d51fdafc6ee26480a60e8f0adea2776f5524fdfb.json
Then /plugin install media-preservation@markdownregistry-u2yw2s7mykgz5bs2 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: media-preservation description: Process and verify audio, image, video, and archive collections with repository-native utilities and explicit preservation contracts. Use for archival conversion, packaging, extraction, or utility development in these workflows, not generic image generation or browser recordings. --- # Media preservation Establish what must survive the transformation before choosing a converter, packager, or extractor. Prefer the repository's verified media utilities and format contracts over a new shell pipeline. ## Select the workflow Read [utility family integration](references/utility-family.md) when using or extending `audio-utils`, `image-utils`, `video-utils`, or `archive-utils`/`archiving-utils`. Reuse each repository's current tools, shared engine, catalog, generation, and validation contract. Check implementation maturity instead of assuming all siblings expose identical flags or supported formats. For image transformation, archive packaging, or extraction, read [images and archival packages](references/images-and-archives.md). For audio/video, use the stream and playback checks below. Load only the references needed by the selected operation. ## Define the preservation contract Identify source formats, destination use, playback requirements, intended losslessness, selected tracks, language/default dispositions, channel layout, sample rate/depth, frame timing, color/HDR metadata, chapters, tags, artwork, subtitles, attachments, and sidecars where applicable. Do not assume a preferred archival format is universal. Read the local utility's platform and dependency requirements before running it. Inspect representative sources with installed tools such as `ffprobe` and format-native validators. Inventory actual streams rather than selecting the first audio/video track blindly. Decide separately whether to copy compressed streams, decode/re-encode losslessly, or produce a lossy derivative. Converting a lossy source to a lossless container cannot recover discarded information. [FFmpeg stream selection and processing](https://ffmpeg.org/ffmpeg.html#Stream-selection). Read [validation and batch recovery](references/validation-and-batches.md) for lossless claims, metadata migration, or multi-file work. Resolve ambiguous track selection or intentional quality loss before the dependent conversion. Preserve originals unless their removal is explicitly requested and validated output satisfies the agreed contract. ## Transform and verify Use existing converters first. Quote paths, preserve unusual filenames, and handle output collisions explicitly. For audio/video, build an explicit stream/metadata mapping compatible with the target container. An indiscriminate `-map 0` may include unsupported attachments or streams. Record intentional omissions and format limitations instead of silently dropping content. Write to a distinct temporary output with an explicit format or suitable extension. Treat the process exit code as only one check. Validate decodeability and the promised properties before promoting output to its final path. Keep source checksums, tool versions, conversion options, and validation results in a compact manifest when the batch needs reproducibility. For archival packages, verify both file integrity and the media contract. Use [backup-restore-verification](../backup-restore-verification/SKILL.md) when the question concerns backup recoverability. Use [cli-web-evidence](../cli-web-evidence/SKILL.md) for browser recordings, not as the archival validation workflow. Report completed, failed, skipped, and intentionally lossy items. State exactly which streams, frames, archive members, and properties were compared where applicable. Do not describe an unverified batch or a checksum-only check as preservation proof.