Agent skill · affaan-m
tasteforge-video
Use for file-driven multimodal image, video, and 3D-asset discovery; taste interviews; distill or apply workflows; style-pack validation; editable EDL/FCPXML export; provenance audits; and offline planning that must fail closed before provider generation.
What it needs
About 8k tokens when loaded.
What this skill does
TasteForge Video For the complete standalone creative pipeline, use taste-distillation then taste-application. Those ECC skills ship their Python scripts directly: measure references, generate or pass through existing takes, grade, cut, composite, verify, and hand off to Blender and Resolve. No separate video repository is required for that flow. This skill documents ECC's packaged offline engine and its strict evidence contract. TasteForge turns "make it feel like this reference" into a repeatable, inspectable workflow: interview taste, distill it into a structured style pack, validate the pack, apply its measured cadence and look to local media, and export an editable timeline. The canonical implementation is the tasteforge package shipped inside ECC at skills/taste-application/scripts/tasteforge/. Ito-Markets/ito-video is an example project that consumes the packaged ECC engine. When to Use The user asks to interview for video taste before any footage is made ("ask me about the look", "interview me about aesthetic direction"). The user wants to distill an aesthetic into structured constraints — a reusable style pack rather than vibes ("turn these references into a pack"). The user wants to validate a style pack (is the metadata complete, schema-valid, cadence measured, spec distilled?). The user wants to apply a style pack to local footage — plan a cut from the pack's measured cadence over local clips, deterministically. The user wants to export EDL/FCPXML — an editable, frame-exact handoff to DaVinci Resolve / Premiere / Final Cut. The user asks for a generated-media provenance audit — where did this pack, spec, or cut come from; what was measured locally versus generated by a provider; what was dry-run. The user asks to discover or plan file-driven multimodal image, video, or 3D-asset outputs from local reference files, including separate manifests, subject-anchored CV effects, or Resolve effect recipes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/tasteforge-video