CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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-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 well-structured interview skill body with concrete question scripts, a clear three-tier user model, and an explicit output contract. Its main weaknesses are repetition that inflates token cost, and heavy dependence on reference files that either live outside this skill's bundle or are absent entirely, leaving the core record structures undefined within the skill.

Suggestions

Consolidate repeated directives: state the Director's Read loading rule, the five-question batch limit, and the skip-already-answered-questions rule once each instead of restating them across sections.

Ship the referenced files (directors-read.md, interview-starters.md, pro-filmmaking-standards.md, etc.) inside this skill's own references/ directory and use relative paths that resolve within the bundle, rather than '../../references/' paths that point outside it.

Inline a one-line definition of the canonical record's key fields (or a minimal example record) so the skill remains actionable even when the external Director's Read reference is unavailable.

DimensionReasoningScore

Conciseness

Mostly efficient instruction-only prose, but with real redundancy: the 'load the Director's Read' directive appears four times (lines 24, 34, 93, 111), the five-question limit is restated in both Question Quality Rules and Priority Question Pool, and 'skip every question the idea already answers' appears three times.

3 / 5

Actionability

Largely executable guidance: the Priority Question Pool gives exact question phrasings with defaults, question templates like '(not sure? I'll choose [option] because [reason tied to this brief])' are copy-ready, and the Output Contract is concrete. Minor gaps remain because core constructs (canonical record fields, starting-point menus) are deferred to external references not shown inline.

4 / 5

Workflow Clarity

The Process section gives a clear 6-step sequence, and 'Treat their reaction as the second interview round' plus 'adjust on reaction' establish feedback loops. This is an interview skill, not a destructive or batch operation, so the validation cap does not apply; the remaining gap is that intermediate checkpoints (when to confirm the lane choice, when to stop adjusting) are implicit rather than explicit.

4 / 5

Progressive Disclosure

References are clearly signaled with when-to-load conditions (e.g. 'Load [pro-filmmaking-standards]... if the user speaks production language fluently'), but the bundle check found no references/, scripts/, or assets/ directories at all, and every reference path escapes the skill's own directory ('../../references/directors-read.md'), so the navigation cannot be verified and the skill is not self-contained.

3 / 5

Total

14

/

20

Passed

Description

83%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 explicit 'Use when' trigger clause, a clear statement of what the skill does, and a distinctive Seedance 2.0 anchor. Its weaknesses are mild: the capability list mixes concrete actions with softer terms ('creative guidance') and omits some natural synonyms users might say.

DimensionReasoningScore

Specificity

The description names several concrete actions - 'creative guidance, story development, scene planning, or a director interview to turn a Seedance 2.0 idea into a production-ready prompt' - but the first three gerunds are somewhat generic, leaving minor gaps in coverage rather than a fully comprehensive list.

4 / 5

Completeness

It explicitly answers both: what ('a director interview to turn a Seedance 2.0 idea into a production-ready prompt') and when ('This skill should be used when the user wants creative guidance, story development, scene planning, or a director interview'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-keyword coverage including 'creative guidance', 'story development', 'scene planning', 'director interview', 'Seedance 2.0', 'shots, lenses, and blocking', but common variations users would say ('AI video', 'video prompt', 'storyboard', 'shot list') are missing.

4 / 5

Distinctiveness Conflict Risk

The 'Seedance 2.0' anchor gives it a clear niche with mostly distinct triggers, but 'turn... into a production-ready prompt' overlaps with closely related sibling skills in the same seedance family (seedance-prompt, seedance-pipeline).

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

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

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