video-forge-setup
Skill2 starsChanged 25 days agoMITView on GitHub
Set up or diagnose Video Forge in an agent host, verify local rendering prerequisites, and choose a usable production or planning path.
In this repository8 other files it gives its agents.
- video-audioSkill
- video-captionsSkill
- video-deliverySkill
- video-editingSkill
- video-forgeSkill
- video-generationSkill
- video-motionSkill
- video-planningSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Verify with run <toolkit-root>/examples/reel-smoke.json --out <new-workspace-directory> and inspect <new-workspace-directory>/vertical.mp4.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video Forge Setup
Locate the toolkit root two directories above this skill folder. Read installation for the current host and host adaptation for capability differences.
Use the current installation rather than creating another copy. Run node <toolkit-root>/dist/cli.js doctor when dependencies exist. If Node modules are missing, prepare the locked runtime in that root with npm ci, npm run setup:binaries, and npm run build, then run doctor again. Respect the session's permissions. No credentials or paid services are needed for the local smoke job.
Verify with run <toolkit-root>/examples/reel-smoke.json --out <new-workspace-directory> and inspect <new-workspace-directory>/vertical.mp4. Report the actual installed version, discovered skills and successful checks. Setup is complete when the required runtime and local render work, not merely when a marketplace was added.
Install optional Python speech/transcription only when needed for the user's workflow. In an environment without shell/browser access, provide the planning/handoff route from compatibility, without claiming a local runtime was installed. Do not change other host settings or publish content as part of setup.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.