Adom Video Post-Production
Public Made by Adomby adom
AI-driven studio for finishing demo videos: review every captured clip, flag and re-record the weak ones, speed up dead air, narrate, mux and auto-level, validate the final cut, and publish straight to the wiki, driven end to end by your AI.
Skills
The skills this repo ships, by tier, each with a quick health read. Install the user skills with:
adom-wiki skills install adom/adom-video-postdev-skills/ or publish-skills/, so a contributor (or their AI) has no in-repo guide to build, debug, or publish it. Consider adding them; they stay source-only and never ship in the tarball.Post-production for demo recordings: speed up boring parts with overlay captions, add voiceover narration after the fact, or publish the final video to a wiki page. For pre-production and recording (writing demo scripts, setting up panels, driving the recording), use the demo-recording skill instead. Trigger words: speed up demo recording, speed up video, timelapse video, fast forward boring parts, compress slow parts of video, video post-production, voiceover after recording, narrate a recording, demo speedup, demo post-process, post-process demo, publish demo video to wiki.
Use when the user wants to record a demo, make a video, create a walkthrough, record their screen, or capture a demo of a feature. Handles the full pre-production and recording workflow: writing the demo script, generating captions, verifying the setup, choreographing panels, and driving the recording. Hands off to adom-video-post for post-production (speedup, voiceover, publish). Trigger words: record a video, record a demo, make a movie, create a walkthrough, record my screen, demo video, screen recording, narrate a walkthrough, capture a demo, make a demo.
No dev skills in this repo.
How to build, debug, and test this app. Source-only (dev-skills/), never shipped in the tarball.
No publish skills in this repo.
The app-to-wiki publish glue. Source-only (publish-skills/), never shipped in the tarball.
Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.