CtrlK
BlogDocsLog inGet started
Tessl Logo

seedance-interview

This skill should be used when the user wants creative guidance, story development, scene planning, or a director interview to turn a Seedance 2.0 idea into a production-ready prompt - adapting to users who have no idea yet, a rough concept, or precise professional direction in shots, lenses, and blocking.

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

63%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 richly operational body with concrete question pools, translation tables, and a clear sequenced process, weakened mainly by rhetorical padding and by inline references that point to bundle files which are not present in the skill directory.

Suggestions

Trim rhetorical passages (the 'front door' metaphor, the Intent philosophy block, and repeated Director's-Read restatements) to tighten conciseness toward the lean anchor.

Add the missing reference bundle files (directors-read.md, pro-filmmaking-standards.md, cinematography-shot-language.md, interview-starters.md, reference-workflow.md, directing-engine.md) to references/, or remove the dead links, so progressive disclosure resolves to real content.

Sharpen the conditional directing guidance ('set one coherent setup... rather than a generic cinematic look') into a concrete decision rule or example to lift actionability.

DimensionReasoningScore

Conciseness

Mostly efficient operational content (numbered rules, question-pool table, translation table), but it carries noticeable rhetorical padding — the 'front door' metaphor, the 'Intent' philosophy passage, and roughly five restatements to load the Director's Read — that could be trimmed without loss.

3 / 5

Actionability

Highly actionable for an instruction-only skill: exact questions with defaults ('not sure? I'll go with [default]'), a feeling-to-film translation table, a Starting Points menu, and a 6-step Process; minor gaps remain in conditional guidance such as 'set one coherent setup... rather than a generic cinematic look'.

4 / 5

Workflow Clarity

A clear 6-step Process sequences read-user → question pool → genre path → pro intake → sequence branch → standalone routing, with an explicit propose-then-adjust feedback loop ('Treat their reaction as the second interview round'); no formal validation checkpoint, but the skill is non-destructive so the cap does not apply.

4 / 5

Progressive Disclosure

Structure and inline signaling are good — references to directors-read.md, pro-filmmaking-standards.md, cinematography-shot-language.md, interview-starters.md, reference-workflow.md, and directing-engine.md are clearly linked — but none of those bundle files exist in references/, so the one-level-deep disclosure does not actually resolve to real files.

3 / 5

Total

14

/

20

Passed

Description

87%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, well-targeted description that explicitly covers what the skill does and when to use it, with good natural trigger terms and a distinct niche. The only weakness is that several named actions are abstract creative-process verbs rather than concrete operations.

DimensionReasoningScore

Specificity

Names several specific actions ('creative guidance, story development, scene planning, or a director interview to turn a Seedance 2.0 idea into a production-ready prompt') and three distinct user scenarios, but several verbs ('creative guidance', 'story development') stay abstract rather than naming concrete operations, so it stops short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both: the 'when' via 'This skill should be used when the user wants...' and the 'what' via 'turn a Seedance 2.0 idea into a production-ready prompt', with concrete trigger phrases — matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keywords a user would say ('creative guidance', 'story development', 'scene planning', 'director interview', 'shots, lenses, and blocking') plus the product name 'Seedance 2.0'; a few natural synonyms or phrasings are missing, so it is not the fully comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Seedance 2.0 idea → production-ready prompt via director interview) tied to a named product and a distinctive workflow, with minimal risk of triggering for an unrelated skill.

5 / 5

Total

18

/

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.

Validation12 / 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: 20 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

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.