seedance-antislop▌
Emily2040/seedance-2.0 · updated Jun 16, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Enhance Seedance prompts by removing vague language and improving clarity.
| name | seedance-antislop |
| description | "This skill should be used when a Seedance 2.0 prompt contains generic AI filler, hollow superlatives, vague cinematic language, bloated adjectives, weak verbs, or needs sharper production-specific wording." |
| license | MIT |
| user-invocable | true |
| tags | - prompt-quality - anti-slop - seedance-20 |
| metadata | version: "5.5.2" updated: "2026-06-12" parent: "seedance-20" author: "Iamemily2050 (@iamemily2050)" repository: "https://github.com/Emily2040/seedance-2.0" openclaw: emoji: "🎬" homepage: "https://github.com/Emily2040/seedance-2.0" |
seedance-antislop
Remove filler that hides missing visual decisions. A strong Seedance prompt uses observable nouns, verbs, camera moves, light sources, sound cues, and constraints. A weak prompt asks for excellence without saying what excellence looks or sounds like.
Intent
Users reach for giant empty words precisely because they care intensely and don't know where to put it. The soul of de-slopping is conservation: every deleted "epic" must come back as a visible choice that holds the same caring. Strip a prompt without honoring the feeling that bloated it, and the user hears that their excitement was wrong.
Visibility Test
Every major phrase should be visible to a camera, measurable by a light meter, audible in the mix, or observable as motion. If a phrase cannot pass that test, replace it with production language.
| Filler | Ask what it means | Strong replacement pattern |
|---|---|---|
| cinematic | What camera and light make it cinematic? | locked close-up, warm practical key, cool rim light |
| epic | What is the scale or stake? | wide low-angle shot, tiny figure against storm wall |
| beautiful | What color, texture, or light behavior? | pearl highlights on wet ceramic, soft window bounce |
| dynamic | What moves, how fast, and where does it end? | fast lateral track ending on the hero label |
| professional | What production setup? | clean commercial tabletop, controlled reflection, no clutter |
The Six Slop Classes
Classify before rewriting - each class has a different repair:
- Empty evaluators (
cinematic, epic, stunning) - convert each to the one observable detail that earns it. - Borrowed image-model tokens (
8K, masterpiece, trending on ArtStation) - delete; quality and resolution are settings, not prose. - Tag salad (comma keyword dumps ported from image prompting) - rewrite as shooting-brief prose: one sentence per element, with an action and a time axis.
- Negation slop (
no blur, no artifacts, no extra fingers) - negation summons; describe what IS there instead, and keep negation only in the constraint slot. - Adjective stacking (three synonyms for one quality) - pick the single detail that matters.
- Feel-suffix words (
电影感, 雰囲気のある, 감성적인, atmosférico, атмосферный, vibey) - name the physical cause of the feeling; every language file inreferences/vocab/has a Slop Traps table for its own community's empty words.
Rewrite Pass
First, underline all superlatives and vague style labels and classify each by slop class. Second, decide whether each word should become camera, light, motion, material, sound, or constraint language. Third, reduce duplicates. Fourth, keep the prompt within the character budget and preserve reference tags.
Do Not Over-Correct
Do not remove useful genre language when it is paired with concrete direction. Noir hallway with hard venetian-blind shadows is useful; dramatic cinematic noir vibes is not. Keep terms that communicate medium, era, palette, or lens behavior.
Load [ref:anti-slop-lexicon] for the slop-class taxonomy and extended replacement table, and [skill:seedance-vocab-en] with references/vocab/en.md for the full function-organized English precision vocabulary. For non-English prompts, load the matching vocab file's Slop Traps table (references/vocab/zh.md, ja.md, ko.md, es.md, ru.md) - each language community has its own empty-quality words and decompositions.
Output Contract
Return removed words, replacements grouped by camera/light/motion/sound/constraint, and the tightened prompt.
https://github.com/Emily2040/seedance-2.0/blob/main/skills/seedance-antislop/SKILL.md
How to use seedance-antislop on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add seedance-antislop
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches seedance-antislop from GitHub repository Emily2040/seedance-2.0 and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate seedance-antislop. Access the skill through slash commands (e.g., /seedance-antislop) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★74 reviews- ★★★★★Pratham Ware· Dec 20, 2024
seedance-antislop has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Olivia Mehta· Dec 20, 2024
Registry listing for seedance-antislop matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Harper Ramirez· Dec 8, 2024
Keeps context tight: seedance-antislop is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yusuf Rao· Dec 8, 2024
Solid pick for teams standardizing on skills: seedance-antislop is focused, and the summary matches what you get after install.
- ★★★★★Olivia Srinivasan· Dec 8, 2024
seedance-antislop fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aisha Jain· Nov 27, 2024
seedance-antislop has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Yusuf Gill· Nov 27, 2024
Registry listing for seedance-antislop matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Olivia Malhotra· Nov 27, 2024
We added seedance-antislop from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Noor Smith· Nov 19, 2024
seedance-antislop reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakshi Patil· Nov 11, 2024
Keeps context tight: seedance-antislop is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 74