track-assets

Maintains a versioned manifest of media assets and renders with hashes, provenance, and rights.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill track-assets-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-assets
Source: https://github.com/alvis/.agents/tree/main/plugins/production/skills/track-assets
Command: npx skills add https://github.com/alvis/.agents --skill track-assets-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Media production work loses track of which footage, audio, graphics, and renders were used, which revision was approved, and what became stale after a decision changed. This Skill gives every asset and render a durable identity with exact provenance so a specific revision can be reproduced and approved without ambiguity. ## Core Features & Use Cases - Asset Registration: Records each source asset with a stable id, content hash, technical facts, provenance inputs, and rights status (owner, consent, licence, expiry). - Render Tracking: Adds a new entry per render revision capturing timeline revision, input hashes, render settings, output hash, and delivery destination. - Staleness Marking: Appends validity markers naming the invalidating decision while preserving history, never deleting referenced entries. - Use Case: A video editor needs to reproduce render v12 after a font licence changed. The manifest shows the exact asset revisions and settings used, and flags which entries the licensing decision invalidated. ## Quick Start Ask the assistant to register the current footage and audio files in the asset manifest and record the latest render with its exact inputs and settings.

Frequently Asked Questions about track-assets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track versions of video renders and media assets?

Record each asset with a stable id and content hash, then add a new manifest entry per render revision capturing its exact input hashes, settings, and output hash. Entries are never edited into successors, so any revision stays reproducible.

How to mark a media asset stale after a decision changes?

Append a validity marker naming the invalidating decision id to the affected entry and leave the entry in place. Never delete an entry that any render or approval still references; record which entries the decision preserves.

Does this tool store or modify the actual media files?

No. Media bytes stay outside Git and are never edited, moved, or deleted. Only their identity, hashes, provenance, and rights metadata are written to the manifest.

What happens when a file hash cannot be computed?

The hash is recorded as pending rather than guessed. The completion report lists all pending hashes so a later session can compute them once the bytes are reachable.

When should I not use an asset manifest approach?

Do not use it for reviewing or approving renders, managing work-stream lifecycle state, or performing actual media editing. Those belong to separate review and state-management workflows.