seedance-copyright
Skill42 starsChanged 4 months agoMITView on GitHub
This skill should be used when a Seedance 2.0 prompt mentions named characters, franchises, studios, celebrities, public figures, private people, brand logos, copyrighted scenes, songs, voices, or real-person likeness workflows and needs an IP-safe rewrite.
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.6k87% 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-examples-jaSkill
- seedance-examples-koSkill
- seedance-examples-zhSkill
- seedance-filterSkill
- seedance-interview-shortSkill
- 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
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 52
Instead of a named superhero swinging through a recognizable franchise city, write:
≈ “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-copyright
Use this before finalizing prompts involving protected IP, named brands, public figures, private people, voices, logos, songs, studios, exact scenes, or lookalike character requests. The goal is not to dilute the idea; the goal is to preserve the creative function with original, authorized, and safer production language.
Intent
The user pointing at protected work is not trying to steal - they are showing you the clearest example of what they love that exists. The job is to find what the love is made of and give it back as something safely theirs. Protect the rights-holder and the user's heart in the same move.
Rewrite Principle
Preserve the scene function, genre, mood, camera logic, emotional beat, and production intent. Replace protected identity with an original archetype, original costume logic, original world details, and descriptive style layers.
| Risk | Replace with |
| Named character or franchise | Original archetype, genre function, and non-identical costume language |
| Studio or living-creator style | Medium, texture, palette, composition, line quality, and motion rhythm |
| Celebrity or private person | Original performer description or authorized reference workflow |
| Brand logo | Generic product mark, blank label, or user-owned brand if explicitly authorized |
| Song, voice, or performance | Tempo, energy, instrumentation, mood, or newly composed sound direction |
| Exact scene recreation | Original scene with similar narrative function and different setting/blocking |
Authorization Gate
If the user clearly owns the brand, asset, or likeness rights, keep the authorized elements but still preserve them with explicit constraints. If authorization is unclear, ask a short confirmation or provide a safe original rewrite. Do not assume rights from an uploaded image, song, or video.
For real human faces, portraits, or voices, separate three questions: does the active surface support the input, does the user have authorization, and does the prompt avoid imitation of a public figure or private person without consent. Some surfaces use verified virtual portrait assets or authorization flows; do not collapse those into a universal allow or deny rule.
Safe Replacement Example
Instead of a named superhero swinging through a recognizable franchise city, write: original masked rooftop courier in a red weatherproof jacket leaps between rain-slick buildings, low handheld tracking camera, blue police lights far below, no logos or franchise symbols.
Output Contract
Return risk category, what was changed, safe replacement prompt, authorization requirement, and any residual constraints.
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.