CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-organized, actionable safety-rewrite skill with a concrete mapping table, worked example, decision gate, and output contract; the only tightening opportunity is the motivational Intent prose, which adds mild non-operational token cost.

Suggestions

Tighten or trim the Intent section to one operational sentence so it states the reframe-vs-refuse stance without the empathetic framing Claude can infer.

Consider making the implicit procedure explicit (e.g., a short numbered sequence: identify risk category → check authorization → apply rewrite → return Output Contract) to remove reliance on inferred section order.

Add an explicit IP-safety verification step (e.g., confirm no trademarked names/logos remain before returning) to close the loop on the rewrite.

DimensionReasoningScore

Conciseness

The body is largely lean, but the "Intent" section ("The user pointing at protected work is not trying to steal... Protect the rights-holder and the user's heart in the same move") is empathetic framing Claude could infer and could be tightened; otherwise tight.

2 / 3

Actionability

Concrete, actionable guidance throughout: a Risk→Replace-with mapping table, a fully worked replacement example prompt, an authorization decision gate, and an explicit Output Contract listing required return fields.

3 / 3

Workflow Clarity

For a simple single-purpose skill under 50 lines the single action is unambiguous, and the sections form a logical flow (detect risk → authorization gate → rewrite → output contract) with the Authorization Gate acting as a decision checkpoint.

3 / 3

Progressive Disclosure

No external bundle files exist and none are needed; the under-50-line body is cleanly split into well-labeled sections (Intent, Rewrite Principle, Authorization Gate, Safe Replacement Example, Output Contract), satisfying the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

90%

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, well-scoped description with explicit when/what triggers and natural keyword coverage; the only weakness is that it describes a single capability (IP-safe rewrite) rather than multiple distinct actions, capping specificity at 2.

DimensionReasoningScore

Specificity

Names a comprehensive, concrete trigger list ("named characters, franchises, studios, celebrities, public figures, private people, brand logos, copyrighted scenes, songs, voices, or real-person likeness") but only a single action ("IP-safe rewrite"), so it names the domain and one action rather than multiple distinct actions.

2 / 3

Completeness

Answers both what ("needs an IP-safe rewrite") and when ("This skill should be used when a Seedance 2.0 prompt mentions...") with an explicit trigger clause, in third-person voice.

3 / 3

Trigger Term Quality

Strong coverage of natural terms a user would actually say ("named characters, franchises, celebrities, public figures, brand logos, songs, voices, likeness") plus the tool-specific "Seedance 2.0 prompt".

3 / 3

Distinctiveness Conflict Risk

Clear, narrow niche (Seedance 2.0 IP/copyright rewrites) with highly specific triggers unlikely to overlap with unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
Emily2040/seedance-2.0
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.