Skip to main content

seedance-antislop

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.

跳到安装

来源信息

仓库
Emily2040/seedance-2.0
最近来源活动
2026年9月7日 13:04
检测到的 SKILL.md 语言
英语
星标
7,342
分支
1,065

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
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":"6.7.0","updated":"2026-08-01","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 Before producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the [Director's Read](../../references/directors-read.md), classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers and keep its internal labels out of final generation prose. Clarify wording that hides an unresolved production decision. Preserve useful style, genre and mood language; concrete detail should support the user's direction, not replace it with a stock look. These are editorial choices, not measured rules about which words improve Seedance output. ## Intent Keep the intended energy, medium, era, palette and performance. A word such as "epic" may communicate a useful ambition even when the brief still needs a decision about scale or stakes. Do not infer the user's taste or confidence from their adjectives. ## Rewrite Pass 1. Identify what is already decided: creative intent, exact dialogue, actual reference tokens, continuity, safety boundaries, exclusions and requested settings. Preserve those through the edit. 2. Check whether an abstract phrase leaves a material choice unresolved. Keep it when context is sufficient. Otherwise use the brief to clarify it; if the user has delegated creative choices, propose a coherent interpretation and state any material assumption. Ask only when a necessary choice remains unresolved outside that scope. 3. Remove redundant praise where it adds no distinct intent. Surface conflicting requirements instead of silently choosing one. Add only details that serve this brief; neither a camera move nor a lighting recipe is required for every style word. Load [anti-slop-lexicon](../../references/anti-slop-lexicon.md) for conditional repairs and delivery requirements. 4. Apply a length limit only when the user requests it or the selected operation documents it. Do not invent a universal character budget or silently discard must-haves to fit one. ## Do Not Over-Correct Keep useful labels such as noir, documentary or ultra-realistic when they describe the chosen look. Observable detail is a way to resolve ambiguity, not a test that every phrase must pass. A locked shot may already serve an energetic scene; "dynamic" does not automatically authorize a lateral track. Likewise, "professional" does not require a clean product tabletop. Treat output resolution as a delivery requirement. Preserve the requested value and carry it into a supported setting when available. Prompt text alone does not guarantee that resolution. If support is unknown or the value is unavailable, state the gap and offer an explicit option within the user's scope; do not silently lower the target, switch providers, add an upscale or spend credits. For English wording, load [seedance-vocab-en](../seedance-vocab-en/SKILL.md) with [English vocabulary](../../references/vocab/en.md). For another prompt language, consult its Slop Traps table only when needed: [Chinese](../../references/vocab/zh.md), [Japanese](../../references/vocab/ja.md), [Korean](../../references/vocab/ko.md), [Spanish](../../references/vocab/es.md), or [Russian](../../references/vocab/ru.md). These are contextual wording examples, not language-wide lists of useless words. ## Output Contract Return the revised prompt in the requested format and briefly explain material edits when useful. Keep delivery settings separate from scene prose, retaining any unresolved requirement. Disclose content changes or assumptions; a wording rewrite does not authorize another submission. Provide a word-by-word removal table only when requested or needed for the review.
在 GitHub 查看