video-prompt
Skill1 starsChanged 34 days agoMITView on GitHub
Write video prompts in the project's brand, sized and timed for each platform, ready for any video generator. Triggers: 'write a video prompt', 'prompt for a reel', 'make a prompt to animate this photo', 'prompt for a product video', 'give me a prompt I can paste into Kling', 'how long should this reel be', 'video prompt'. Reads the project's own brand file for palette, look, motion, tone and a don't list, and never stores brand values itself. Writes the prompt, a JSON with size, ratio, length and a suggested model, and on request short paste steps for a web tool. It never generates a video and never spends credits. Needs Node 18 or newer.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- chenthedesignmaker/ComfyUI-Pickytheir own version, first seen Nov 1, 2026
- ZhongBiao-zheng/video-prompttheir own version, first seen Oct 20, 2026
- wanna-money/video-prompt-craft-skilltheir own version, first seen Aug 17, 2026
- Mikefluff/skillstheir own version, first seen Aug 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- chenthedesignmaker/ComfyUI-Picky★ 29same name
- Mikefluff/skills★ 26same name
- wanna-money/video-prompt-craft-skill★ 0same name
- ZhongBiao-zheng/video-prompt★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- audio-narrateSkill
- audio-transcribeSkill
- cloudflare-opsSkill
- dokploy-opsSkill
- elevenlabs-studioSkill
- hetzner-opsSkill
- higgsfield-studio-brandkitSkill
- higgsfield-studio-marketplace-cardsSkill
- higgsfield-studio-product-photoshootSkill
- higgsfield-studioSkill
- higgsfield-studio-soul-idSkill
- higgsfield-studio-video-explainerSkill
- higgsfield-studio-websitesSkill
- higgsfield-studio-youtube-thumbnailSkill
- image-promptSkill
- namecheap-opsSkill
- plane-fleetSkill
- toolkit-credentialsSkill
- toolkit-updatesSkill
- video-watchSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 69
No brand file is fine: the prompt carries no brand style, and the tool says so.
- Distinctive: line 70
Never invent brand values, and never copy them into this skill.
- Distinctive: line 79
Read the brand file every time: Never write a brand value from memory.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video Prompt
Writes the prompt for a short video: in the project's brand, in the right size and length for the platform, with the motion spelled out and a don't list. It writes text only. It never generates a video, so it costs nothing.
The prompt then goes to a video generator. When the higgsfield-studio skill is installed, hand it over there: it quotes the price before anything is spent, and video is where credits go fastest. Otherwise the user pastes it into any web tool.
Who you are doing this for
Assume the person asking has never opened a terminal. You run the commands; they never do. Show them the prompt in plain words and say what happens next. If they are clearly comfortable with a terminal, let them drive.
Before anything else: check the dependencies
sh scripts/setup-deps.sh --checkNon-zero exit means Node is missing or older than 18. sh scripts/setup-deps.sh (Windows: .\scripts\setup-deps.ps1) prints the right install command for the machine and asks before running it; --yes skips the question.
Commands
node scripts/prompt.mjs --subject "..." [--type turntable] [--platform instagram_reel] [--variant square]
[--size 1080x1920] [--seconds 7] [--reference] [--people] [--scene "..."] [--motion "..."]
[--brand FILE] [--brand-mode full|minimal|none] [--paste "Tool name"] [--out DIR] [--force]
node scripts/prompt.mjs sizes every platform, variant, size and accepted length
node scripts/prompt.mjs brand which brand file is used and what was read from it--subjectis what the video shows, in plain words.--typeis the shot:turntable(default),hero-reveal,editorial,detailoranimate-still. Seereferences/prompt-craft.md.--platformand--variantset size and default length from the table below.--size WxHsets the size directly.--secondssets the length. A length the platform does not accept is refused.--referencewhen there is a photo of the real subject (image to video).animate-stillalways uses one.--motionreplaces the shot's motion line. The brand's own motion rules are still added after it.--paste "Kling"also writesPASTE.md: short, general steps for pasting the prompt into that web tool.
Each run writes a folder with prompt.txt (the prompt alone, ready to copy) and prompt.json (the prompt, size, ratio, length, don't list, the brand file used, and a suggested Higgsfield model with ratio, clip length, number of clips and a cheaper draft model).
Platforms
| Platform | Variants | Size | Default length |
instagram_reel, facebook_reel, tiktok, youtube_short | 1080x1920 | 7 to 10 s | |
instagram_story, facebook_story | 1080x1920 | 7 s | |
instagram_post | portrait (default), square | 1080x1350, 1080x1080 | 7 s |
facebook_feed, linkedin_post | square (default), landscape | 1080x1080, 1280x720 or 1920x1080 | 10 s |
youtube | 1920x1080 | 10 s | |
product_page | 1080x1080 | 5 s |
node scripts/prompt.mjs sizes shows the exact length range each one accepts.
The brand
The brand comes from a Markdown file the project owns: --brand FILE, else BRAND_FILE, else brand.md, BRAND.md, brand/brand.md or docs/brand.md in the folder the command runs from. Its sections (palette, look, studio, motion, tone, don't) are found by their headings. The full contract and an example are in references/brand-file.md.
- No brand file is fine: the prompt carries no brand style, and the tool says so. Offer to write one with the user. For video, also ask how things should move: pace, camera, cuts.
- Never invent brand values, and never copy them into this skill. Read the file every time.
--brand-mode minimalkeeps only the look and the don't list.noneignores the brand.
Handing it to Higgsfield
prompt.json has a higgsfield block: the model, a cheaper draft model, the aspect ratio, the length of each clip and how many clips. With the higgsfield-studio skill installed, use its create command with --prompt-file pointing at prompt.txt, the model, --aspect_ratio and --duration, and --image for a reference. It quotes the price first. Make the draft, check the motion, then render the final once.
Rules
- Read the brand file every time. Never write a brand value from memory.
- Short first. 5 to 10 seconds fails less and costs less. A longer piece is several clips.
- One prompt, then look. Fix with one change at a time (
references/prompt-craft.mdlists the usual fixes). - Respect the log. Exit code 3 means a similar prompt was already written in this project. Show the user the earlier one. Use
--forceonly when they want a new one. - Disclosure. Generated video counts as AI-generated material on most platforms. Tell the user to use each platform's AI label when they publish.
Updates
This skill is versioned. Its version is metadata.version in the header of this file. CHANGELOG.md in this folder lists what changed in each version, newest first.
To check for a newer version, open the address on the Latest: line of CHANGELOG.md and compare its top version with the installed one. If the newer one is ahead, read every entry between the two and tell the user what changed before anything is updated. A Breaking section means the user has to do something. To update, reinstall the skill from its source repository, the same way it was installed.
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.

