seedance-interview-short
Skill42 starsChanged 4 months agoMITView on GitHub
This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Emily2040/seedance-2.0edited, first seen Oct 8, 2026
- 381487190/opengodword for word, first seen Aug 8, 2026
Other versions2 projects use a version of this.
Word for word · 1
- 381487190/opengod★ 0100% same
Edited · 1
- Emily2040/seedance-2.0★ 7.6k41% same
Wrote their own version · 0
None found.
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 repository28 other files it gives its agents.
- seedance-20Skill
- seedance-antislopSkill
- seedance-audioSkill
- seedance-cameraSkill
- seedance-charactersSkill
- seedance-continuationSkill
- seedance-copyrightSkill
- seedance-examples-jaSkill
- seedance-examples-koSkill
- seedance-examples-zhSkill
- seedance-filterSkill
- seedance-interviewSkill
- seedance-lightingSkill
- seedance-motionSkill
- seedance-pipelineSkill
- seedance-prompt-shortSkill
- seedance-promptSkill
- seedance-recipesSkill
- seedance-sequenceSkill
- seedance-styleSkill
- seedance-troubleshootSkill
- seedance-vfxSkill
- seedance-vocab-enSkill
- seedance-vocab-esSkill
- seedance-vocab-jaSkill
- seedance-vocab-koSkill
- seedance-vocab-ruSkill
- seedance-vocab-zhSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 24
Use this when speed matters more than exhaustive creative discovery.
- Distinctive: line 32
Ask at most three questions, and only ask them if the answer materially changes the prompt.
- Distinctive: line 38
If the user already supplied enough information, do not ask.
≈ “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
seedance-interview-short
Use this when speed matters more than exhaustive creative discovery. The goal is to turn a vague idea into a compact director brief with no more than three questions, then route to prompt writing.
Intent
The user here knows what they want and is asking you to respect their momentum. The soul of this skill is restraint: find the one missing piece that would sink the generation, ask only that, and get out of the way. Speed is the form their trust takes.
Process
Ask at most three questions, and only ask them if the answer materially changes the prompt. Assume no film background: ask in everyday words, give pickable options, and attach a default so "I don't know" never stalls the brief. Prioritize:
- What happens in the video, and what is different at the end?
(not sure? I'll pick one simple action with a visible ending) - Is this one complete clip, connected clips, a longer scene to divide, a continuation of accepted footage, or are you unsure?
(not sure? I'll plan the whole story but only finalize the first prompt) - How must the complete story end, and do you have photos, clips, final frames, or sound that define the look, motion, or sound?
(none is fine; if continuing, I need the accepted clip or final frame)
If the user already supplied enough information, do not ask. Produce a brief immediately. If the user speaks production language fluently, drop the plain phrasing and ask in director terms.
Run the interview and brief in the user's language; for native starting-point menus and invites, load [ref:interview-starters]. If the user gives explicit shot, lens, camera, blocking, or performance direction, keep it verbatim and compile it into a shot-contract-grade brief - never simplify or override a professional's spec. When the user has no idea at all, offer a starting-point menu to react to instead of asking a question they cannot answer.
Even in fast mode, the brief states one motivated intention, not a generic "cinematic" look: name what the scene is doing and let the camera, light, and performance serve that. Load [ref:directing-engine] only when the right setup for the scene is genuinely unclear; otherwise apply its coherence rule inline.
Compact Brief Pattern
Mode: [T2V/I2V/V2V/R2V]. Subject: [anchor]. Beat: [before -> action -> final state]. Camera: [one move]. Light/style: [physical source and safe descriptor]. Sound: [dialogue/ambience/SFX/music/silence]. Constraints: [identity, IP, safety, product, prompt budget].
Routing Rule
Route to [skill:seedance-sequence] for connected clips, long scenes, unclear total duration, or continuation-ready planning; [skill:seedance-continuation] for accepted-footage continuation; [skill:seedance-prompt] for a full standalone production prompt; [skill:seedance-prompt-short] for a compact prompt; [skill:seedance-copyright] for IP/likeness risk; or [skill:seedance-troubleshoot] when the user starts from a bad result.
Output Contract
Return one compact brief under 150 words, any missing high-impact question, and a recommended skill route. If the request is a sequence, include the complete story ending, likely clip count, current clip job, and the fact that future prompts stay provisional until accepted footage is reviewed.
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.

