CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-copyright

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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seedance-copyright/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

A compact, well-organized instruction skill with a genuinely useful risk→replacement table and a concrete example, but its workflow depends on a Director's Read file referenced via a bundle-escaping relative path that does not exist in this skill's directory, and there is no validation step confirming the rewrite is IP-safe. Tightening the Intent prose and fixing the reference would raise it substantially.

Suggestions

Fix the dangling reference: the body's core instruction depends on [Director's Read](../../references/directors-read.md), which resolves two levels outside the skill bundle and does not exist in references/. Either ship the file at references/directors-read.md within the skill or inline the essential classification steps so the skill is self-contained.

Add an explicit validation checkpoint before returning output, e.g., 'Scan the final prompt for protected names, brands, logos, and real-person descriptors; if any remain, re-apply the replacement table before responding' — the Output Contract lists what to return but never verifies IP-safety.

Trim the Intent section to a single sentence (e.g., 'The user pointing at protected work is showing you what they love; preserve that creative function, not the protected identity') to cut the motivational framing.

DimensionReasoningScore

Conciseness

The body is short (~35 lines), dense, and assumes competence: the risk/replacement table, the Authorization Gate, and the Output Contract are all business with no concept explanations. It is not a 5 because the Intent section ("The user pointing at protected work is not trying to steal - they are showing you the clearest example of what they love that exists... Protect the rights-holder and the user's heart in the same move") is motivational framing that could be trimmed to one line.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: a six-row risk→replacement mapping table, a copy-paste-ready example rewrite ("original masked rooftop courier in a red weatherproof jacket leaps between rain-slick buildings..."), and a specified Output Contract ("Return risk category, what was changed, safe replacement prompt, authorization requirement, and any residual constraints"). It is not a 5 because the core classification procedure is delegated to an external document and no guidance is given for handling cases outside the six rows.

4 / 5

Workflow Clarity

A sequence exists (load the Director's Read → classify the brief → complete the record → translate into carriers → keep labels out of prose → authorization gate → output contract) but it is spread across sections rather than enumerated, and there is no validation checkpoint confirming the final prompt is IP-clean before returning. This matches the anchor 'steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than the 4 anchor, which requires most checkpoints present.

3 / 5

Progressive Disclosure

Section headers are clear and the body is appropriately short, but the single external reference — [Director's Read](../../references/directors-read.md) — points two directory levels up, outside the skill bundle, and no references/, scripts/, or assets/ directories exist alongside SKILL.md. The skill's central procedure depends on a file that is not part of the bundle and unverifiable from its location, which is worse than the 4 anchor's 'minor organization gaps'.

3 / 5

Total

14

/

20

Passed

Description

81%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.

A strong description with an excellent, exhaustive set of natural trigger terms and an explicit 'use when' clause in third person. Its main weakness is that the capability side is compressed to a single phrase ('IP-safe rewrite'), so the what is thinner than the when.

DimensionReasoningScore

Specificity

The description names its domain ("a Seedance 2.0 prompt") and exactly one action — "needs an IP-safe rewrite" — matching the anchor for naming the domain with 1-2 concrete actions but not comprehensive coverage. It is not a 4 because no additional capabilities (classify risk, check authorization, produce output contract) are stated, only the single rewrite action.

3 / 5

Completeness

Both parts are present: 'when' is explicit and concrete ("This skill should be used when a Seedance 2.0 prompt mentions..."), and 'what' is carried by "needs an IP-safe rewrite". It falls short of the 5 anchor because the 'what' is implied by the prompt's need rather than stated as the skill's own actions (e.g., 'rewrites prompts, classifies IP risk, verifies authorization'), leaving the action list thinner than the exemplar.

4 / 5

Trigger Term Quality

It comprehensively enumerates natural trigger terms users would actually say: "named characters, franchises, studios, celebrities, public figures, private people, brand logos, copyrighted scenes, songs, voices, or real-person likeness workflows" — covering synonyms and variations of the IP/likeness space. It is not below 5 because no common variation (character, celebrity, likeness, logo, song, voice, scene) is missing.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — IP/copyright/likeness safety for Seedance 2.0 video prompts — with distinct triggers that no generic rewriting or video skill would naturally claim. The "Seedance 2.0 prompt" qualifier plus the enumerated IP surfaces give minimal conflict risk; it does not fit the 4 anchor, which expects minor overlap with closely related skills.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

skills/seedance-copyright/SKILL.md

Reviewed

Table of Contents

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.