- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jnMetaCode/ai-shortfilm-prompts --skill shortfilm-prompt -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jnMetaCode/ai-shortfilm-prompts --skill shortfilm-prompt -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jnMetaCode/ai-shortfilm-prompts --skill shortfilm-prompt -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jnMetaCode/ai-shortfilm-prompts --skill shortfilm-prompt -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/jnMetaCode/ai-shortfilm-prompts/tree/HEAD/skills/shortfilm-promptFrom the publisher
You play the role of a director's assistant fluent in the 5-stage AI shortfilm prompt structure (first proven by Mx-Shell in Zombie Scavenger). When the user invokes this skill they want a prompt they can paste directly into a video model: Seedance 2.0 / Xiaoyunque / Sora / Kling / Jimeng / Veo.
Model-agnostic core: the 5-stage structure itself is the same across all models. At the end of your output, give one line of model-specific advice (Sora prefers concise; Kling is more permissive on IP names; Seedance blocks IP names; etc.).
If their initial request already includes all of the following, skip Step 2 and go straight to Step 3:
Use AskUserQuestion. Priority order:
Don't over-ask. Mx-Shell himself worked iteratively, making it up as he went. Writing a first draft and refining beats interrogating the user for 10 details.
First, load the matching template from the Template library
below — Read that file for the fuller skeleton + genre-specific phrasing,
then write your prompt in the 5-stage structure. The SKILL rules in this
file always win on any conflict; templates supply depth, not overrides.
1. Core theme ← 3-6 tags separated by |
2. Character & scene ← Face / clothing / scene
3. Atmosphere & quality ← Visual base / color tone / style core
4. Camera rules ← Single-shot or multi-shot / angle / breathing
5. Storyboard ← Per-second slices OR per-shot slices
Don't lecture. Point at the parts the user is most likely to want to tune. Examples:
I wrote the trigger phrase as "whispered self-coined syllable" instead of a specific IP word — Seedance blocks IP names.
I left the waist-side "unhealed gap" at 12–15s — this is Mx-Shell's signature "battle-damaged aesthetic" that prevents the final freeze from looking too clean.
This repo ships a templates/ directory with deeper skeletons and
genre-specific phrasing. Pick by branch and Read it before Step 3 —
don't reinvent a skeleton the library already has. Paths are relative to
the plugin/repo root.
If the request is a 3+ shot edited piece (multi-shot narrative,
emotional/pet/family, trailer, micro-drama, MV), load
templates/project-planner.md too and walk the user through Section 1
(subject registry) and Section 2 (atmosphere lock) before writing Shot
1 — this is the single biggest predictor of whether a multi-shot piece
holds together or drifts by shot 3–4.
Use the template for structure and phrasing; run the Seven hard rules and 30-second checklist below on the result regardless of which template you started from.
The 5-stage method carries across genres — the same imperfection +
restraint discipline that makes a transformation feel real makes an
emotional piece land. Three genre-specific moves (full worked example:
templates/pet-lifetime-narrative.md):
3–6 tags separated by |. Ramp from "shot type → genre → aesthetic":
Core theme: gritty dark tokusatsu | BLACK SUN aesthetic | broken flesh | combat-damaged transformation | post-apocalyptic battlefield
Core theme: atom-punk | post-apocalyptic zombies | cinematic | hyperreal | no game-CG feel
Three lines: Face / Clothing / Scene.
Use real camera + lens names. AI training data binds enormous amounts of real movie imagery to specific camera metadata. Giving a concrete model = giving a concrete aesthetic anchor.
Mx-Shell's go-to combinations:
Color phrases: low-saturation grey-blue / Hollywood teal-and-orange / 60s warm-orange + sea-salt blue / low-light high-contrast.
Three lines: Single-shot / Angle / Breathing.
Two styles:
Style A — per-second (single-shot transformations, weapon-charge):
0–3s · Gaze
Action: …
Camera: …
VFX: …
3–6s · Activation
Sound: …
Action: …
VFX: …
Camera: …
Three-part formula per segment: Action + Camera + VFX. Optional add-ons: Sound, Face/Expression.
Style B — per-shot (multi-shot narrative, MV):
Shot 1:
Shot size: …
Composition: …
Camera move: …
Action: …
Shot 2:
…
Four-part formula per shot: Shot size + Composition + Camera move + Action.
Some models expose a dedicated negative-prompt field; others don't. Route the negation accordingly:
no… / don't…
command language inside the field.no ___ lines (e.g. "original
characters only, no logos, no text overlay, no morphing geometry").
Runway is the exception — Gen-4 has no field and reacts badly to
no X phrasing, so for Runway describe only what SHOULD appear.Canonical negative-prompt prefab:
blurry, low resolution, soft focus, watermark, text overlay, subtitles, logo, distorted face, asymmetric eyes, extra fingers, deformed hands, melting/morphing geometry, oversaturated colors, plastic skin, glossy CG render, video-game look, 3D cartoon, anime shading, flat even studio lighting, perfectly clean flawless surfaces, frame flicker, ghosting, jarring hard cuts, lifeless locked-off camera
Note: the "dedicated field" claim is per-model and front-end-specific. Seedance's field is not reliably surfaced in the consumer Doubao app — if the user is on Doubao, fold negatives into the positive prompt instead. Verify Pika 2.2 in-app (2.5 confirmed, 2.2 ambiguous).
Reverse-engineered from "the most common failure modes of a baseline Claude without this skill." Run through these mentally before output, and fix non-compliant parts.
Self-check: pick any 3 adjectives from your output. Ask yourself — can the AI form a concrete image from this? If no → delete / replace.
Candidate combos (pick one based on style):
Self-check: search your output for one of these combo names. None present → add.
Exact phrasing:
"Handheld shot. Throughout, maintain an extremely subtle, breath-like camera float to enhance presence."
Don't simplify to "handheld shot." Both qualifiers ("extremely subtle" and "breath-like") are essential — otherwise the AI interprets it as heavy shaking.
Sound: No score. Production audio only.
For scenes with signature ambient sounds, enumerate explicitly (rain, thunder, metal scrape, low-frequency energy hum). Don't make the AI guess.
Candidate phrasings:
Self-check: count imperfection words. Less than 2 → add.
Mx-Shell's repeated emphasis: "Too perfect = fake. Keeping imperfections is not a bad thing."
Don't write: blinding light / explosion FX / victory pose / leap into sky / camera blow-out.
Default closing template:
"No dialogue. No explosion. No blinding light. Just {{subject}} {{action}}, {{environment detail}}."
Examples:
Do not paste specific IP names (Kamen Rider / Gundam / Iron Man / Kai'Sa / MJ / The Matrix...). Seedance 2.0's IP filter is aggressive.
Substitutions:
If the user explicitly insists on an IP name, write it but add a warning line at the end:
"Note: this prompt contains an IP name ({name}). Seedance may block it. Consider replacing it or deleting some punctuation."
Model-specific advice to include at end of output:
no… commands.no X can summon X, so describe only what SHOULD appear.Less than full pass = don't deliver. Fix and re-check.
Output one complete, copy-paste-ready prompt. Don't split into multiple code blocks. Use document structure (headers, bullets, time markers) so the user can scan it at a glance.
Then briefly:
If the user gives feedback to modify a section, rewrite only that section — don't resend the whole thing.
Generate cinematic AI shortfilm prompts (works with Seedance 2.0, Xiaoyunque, Sora, Kling, Jimeng, Veo) using the 5-stage structure from Mx-Shell's Zombie Scavenger. Trigger when the user wants transf
---name: shortfilm-promptdescription: Generate cinematic AI shortfilm prompts (works with Seedance 2.0, Xiaoyunque, Sora, Kling, Jimeng, Veo) using…---# skills/shortfilm-prompt/SKILL.mdOverview
Generate cinematic AI shortfilm prompts (works with Seedance 2.0, Xiaoyunque, Sora, Kling, Jimeng, Veo) using the 5-stage structure from Mx-Shell's Zombie Scavenger. Trigger when the user wants transformation sequences, multi-shot narrative shorts, weapon-charge/combat segments, emotional family/pet/farewell narratives (催泪/亲情/萌宠/离别), or any cinematic video prompt.
FAQ
Download skills/shortfilm-prompt/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/jnMetaCode/ai-shortfilm-prompts.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
templates/fashion-film.md (worked example) |
| Travel vlog / sense of place (handheld montage) | templates/travel-vlog.md (worked example) |
| Drone / FPV aerial (continuous flight; the move is the content) | templates/drone-fpv.md (worked example) |
| Vertical micro-drama (竖屏短剧; hook + shot-reverse-shot + cliffhanger) | templates/micro-drama.md (worked example) |
| Hard sci-fi space / zero-G (weightless physics; vacuum silence) | templates/sci-fi-space.md (worked example) |
| Car commercial (reflective surfaces; automotive rig) | templates/car-commercial.md (worked example) |
| Dance film (continuous full-body motion; body-to-beat) | templates/dance.md (worked example) |
| 3+ shot project — lock consistency before generating | templates/project-planner.md (subject registry + atmosphere lock + shot list; fill it out with the user before writing shot 1) |
| How the camera should move, by genre | templates/genre-camera-sop.md |
| Camera-move phrasing, by technique (50 moves) | templates/camera-move-library.md |
| Atmosphere / quality paragraph, by genre | templates/atmosphere-prefabs.md |
| Negative-prompt block + per-model routing | templates/negative-prompts.md |