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.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/seedance-antislop/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-structured, and actionable with a clear rewrite workflow and output contract, but its progressive disclosure is undermined because every referenced bundle file is absent from the skill package.

Suggestions

Ship the referenced bundle files (directors-read.md, anti-slop-lexicon.md, references/vocab/*.md, seedance-vocab-en/SKILL.md) or remove the links so navigation does not point to missing material.

Add an explicit validation step to the Rewrite Pass, e.g. 'Re-run each major phrase through the Visibility Test before emitting the Output Contract.'

State the concrete output action (rewrite/tighten the prompt) up front in the body so the skill's capability is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and purposeful: no padding explaining concepts Claude already knows, and each section (Intent, Visibility Test table, Six Slop Classes, Rewrite Pass, Do Not Over-Correct, Output Contract) earns its place.	5 / 5
Actionability	Concrete replacement patterns in the filler table, named slop classes with specific repairs, a four-step Rewrite Pass, and an Output Contract give mostly executable guidance; as an instruction-only skill it lacks copy-paste code but the guidance is specific and actionable.	4 / 5
Workflow Clarity	A clear classify-then-rewrite sequence is present (classify by slop class, assign carrier language, reduce duplicates, respect budget/tags) plus an Output Contract, but there is no explicit validation checkpoint to confirm the rewrite passes the Visibility Test before returning.	4 / 5
Progressive Disclosure	References are well-signaled in-text and one level deep (directors-read.md, anti-slop-lexicon.md, per-language vocab files, seedance-vocab-en/SKILL.md), but none of these referenced files exist in the bundle and the references/, scripts/, assets/ directories are absent, so the navigation points to missing material.	3 / 5
	Total	16 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a clear, distinctive niche and strong trigger phrasing, but it foregrounds when-to-use conditions while leaving the actual capability (rewriting/tightening prompts) implicit, capping completeness.

Suggestions

Add an explicit 'what' clause naming the concrete action, e.g. 'Tightens and rewrites Seedance 2.0 prompts into production-specific camera/light/motion/sound/constraint language.'

Move or duplicate the trigger conditions so the description leads with the capability before listing when to use it, improving both specificity and completeness.

Dimension	Reasoning	Score
Specificity	The description names the domain (Seedance 2.0 prompts) and several concrete trigger conditions ('generic AI filler, hollow superlatives, vague cinematic language, bloated adjectives, weak verbs'), but stops short of listing the concrete actions the skill performs, leaving the 'what' mostly implicit.	4 / 5
Completeness	The 'when' is explicit and strong ('should be used when a Seedance 2.0 prompt contains...'), but the 'what' is only weakly implied via 'needs sharper production-specific wording' rather than stating the skill rewrites or tightens the prompt, so the 'what' is missing/implicit per the completeness anchors.	3 / 5
Trigger Term Quality	Phrases like 'generic AI filler', 'hollow superlatives', 'vague cinematic language', and 'weak verbs' are natural symptoms a user would voice, giving good keyword coverage with only minor variations missing.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific (Seedance 2.0 prompt de-slopping) with distinct triggers, so it is clearly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 9 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	12 / 16 Passed

Repository: Emily2040/seedance-2.0
Path: skills/seedance-antislop/SKILL.md
Commit: 44b5149

Reviewed: 25 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.