CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-continuation

This skill should be used when a Seedance 2.0 user asks to continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage.

Quality

74%

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-continuation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 tightly written, checkpoint-rich instruction body with concrete gates, refusal scripts, and a crisp output contract. Its critical defect is that the entire execution apparatus — seven reference files and one script — is referenced but absent from the bundle, and via "../../references/" paths that escape the skill directory, leaving the skill non-self-contained and its navigation broken.

Suggestions

Ship the referenced bundle files (directors-read.md, continuation-handoff.md, sequence-project-state.md, prompt-compiler.md, reference-transfer-contract.md, continuity-qc.md, failure-atlas.md, directing-engine.md, and scripts/extract_last_frame.py) inside the skill directory, or inline the essential record/compile steps so SKILL.md is self-contained.

Fix the reference paths to live within the skill folder (references/directors-read.md, not ../../references/directors-read.md) so links resolve relative to SKILL.md.

Assemble the scattered steps (load read, classify, gate, observe, compile, output) into one ordered workflow section so the sequence and its validation checkpoints are readable end-to-end without jumping between sections.

DimensionReasoningScore

Conciseness

The body is dense domain-specific rule-making (input gate fields, canon rule, scene boundary rule, extension-depth cap) with no generic concept explanations Claude already knows. Minor trimmable material keeps it from 5: the philosophical "Intent" paragraph ("The soul of this skill is fidelity to what actually happened..."), the duplicated Director's-Read load instruction at the top and in the reference list, and the "never paste internal labels into final generation prose" rule stated twice. Not 3 because there is no genuinely unnecessary explanation, just slight tightening opportunities.

4 / 5

Actionability

Concrete, executable guidance throughout: an exact refusal script to quote verbatim, a runnable command ("python scripts/extract_last_frame.py <take>"), a 15-item required-input checklist, five defined continuation types, and a numbered 10-item output contract. Not 5 because the core compilation steps ("complete its canonical narrative or non-narrative record", "compile the exact visible or audible carriers") are delegated to reference files that are not present in the bundle, so a reader cannot fully execute from this file alone; not 3 because what is written here is specific and directly executable rather than pseudocode.

4 / 5

Workflow Clarity

A real sequence with explicit checkpoints: source gate before any prompt is written, observation confidence flags ("observation_confidence: low", "requires_user_confirmation: true") when pixels aren't in hand, the intent echo "confirmed before generation spends money", the extension-depth re-anchor cap, and the scene-boundary rule. Not 5 because the end-to-end order of operations is never assembled into one flow — it is distributed across the intro, gate, and rules sections — and error recovery is delegated to absent references (continuity-qc, failure-atlas); not 3 because checkpoints are explicit and well-placed, not merely implied.

4 / 5

Progressive Disclosure

References are clearly signaled with load conditions ("Load failure-atlas... when the continuation failed or drift is visible"), but the bundle contains only SKILL.md — none of the seven referenced files (directors-read.md, continuation-handoff.md, sequence-project-state.md, prompt-compiler.md, reference-transfer-contract.md, continuity-qc.md, failure-atlas.md, directing-engine.md) nor scripts/extract_last_frame.py exist, and the links point to "../../references/", two levels above the skill directory and outside it. Every load instruction leads to a missing file, so the overview is an orphaned index with broken navigation. Not 3 because the signaling quality cannot compensate for the fact that the referenced structure simply is not provided; not 1 because the SKILL.md itself is well-sectioned and the references are one conceptual level deep.

2 / 5

Total

14

/

20

Passed

Description

75%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 focused, trigger-rich description with an explicit "should be used when" clause and multiple concrete continuation actions anchored to a specific tool (Seedance 2.0). The main weakness is that the what is expressed only through the trigger verb list rather than a distinct capability statement, and a couple of natural synonyms (e.g., "seamless", "next clip") are absent.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage" — each naming a distinct operation. Not 5 because the deliverable of each action (a compiled continuation prompt with an output contract) is only implied by "create a successor prompt", leaving minor coverage gaps; not 3 because far more than 1-2 actions are named.

4 / 5

Completeness

An explicit when-clause is present ("This skill should be used when a Seedance 2.0 user asks to...") with concrete triggers, and the what is conveyed through the enumerated actions. Not 5 because the capability statement is folded entirely into the trigger clause rather than stated as a distinct what (e.g., "Writes Seedance 2.0 continuation prompts grounded in accepted footage"); not 3 because both what and when are explicitly present.

4 / 5

Trigger Term Quality

Good coverage of natural phrases a user would say: "continue", "extend", "make the next part", "repair the tail", "successor prompt". Not 5 because common variations like "seamless", "pick up where it left off", "next clip", or "keep going" are missing; not 3 because multiple natural phrasings beyond the generic are present.

4 / 5

Distinctiveness Conflict Risk

Distinctive vocabulary like "repair the tail", "re-anchor drift", "bridge between known frames", and "accepted footage" carves out a clear Seedance 2.0 niche. Not 5 because the frontmatter declares a parent skill ("seedance-20") and bare "continue/extend" requests could plausibly match either this or the general parent prompting skill — minor overlap risk with a closely related skill.

4 / 5

Total

16

/

20

Passed

Validation

75%

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

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

skills/seedance-continuation/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.