CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-interview-short

This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.

Quality

71%

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-short/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 tightly written instruction-only skill with genuinely actionable interview scripts, a concrete brief template, a routing table, and a pre-delivery validation screen. Its weaknesses are redundancy around loading the Director's Read, a flow whose core classification step depends on reference files that live outside the bundle and are not present, and the absence of any bundled reference material to back the heavy external linking. It lands solidly above the midpoint but short of excellent.

Suggestions

Consolidate the three separate "load the Director's Read" instructions into one directive at the top of Process, cutting the duplicated framing sentences in the opening paragraphs.

Bundle the referenced files (directors-read.md, interview-starters.md, moderation-prescreen.md) inside this skill's own references/ directory and update links to relative paths within the bundle, so the skill is self-contained and navigable.

Trim the Intent section's non-operational prose ("Speed is the form their trust takes") and add a one-line recovery instruction for the Pre-Delivery Screen — what to do when the pre-screen flags the draft — to close the validation loop.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific directives and explains nothing Claude already knows, but it repeats the same instruction three times — "load the [Director's Read]" appears in the opening, again two paragraphs later ("Load the [Director's Read] before producing the compact brief"), and once more in Process — and the Intent section carries non-operational prose ("The soul of this skill is restraint... Speed is the form their trust takes"). Anchor 4's "minor instances that could be trimmed" understates this redundancy, while anchor 1-2 verbosity (padding, known-concept explanation) is absent.

3 / 5

Actionability

The skill provides copy-paste-ready interview questions with defaults attached ("What happens in the video... (not sure? I'll pick one simple action with a visible ending)"), a fill-in brief template ("Mode: [T2V/I2V/V2V/R2V]. Subject: [anchor]..."), and an explicit routing table with named skills and conditions. It falls short of anchor 5 because the central workflow step — "classify the brief, and complete its canonical narrative or non-narrative record" — depends entirely on the Director's Read file, and none of the referenced files exist in this bundle, so the core action cannot be executed from the skill alone.

4 / 5

Workflow Clarity

The flow is legible across sections: load the Director's Read and classify, run the ≤3-question interview, fill the Compact Brief Pattern, run the Pre-Delivery Screen, then route. An explicit validation checkpoint exists ("Run the [moderation pre-screen] on the draft before it is shown"), plus the accepted-footage gate for sequences. It misses anchor 5 because the pre-screen has no feedback loop (what to do when the screen flags the draft is only sketched as "keep the scene, drop the cue") and steps are not explicitly sequenced against each other.

4 / 5

Progressive Disclosure

The body is well-sectioned with clearly signaled links, but every detailed reference — directors-read.md, interview-starters.md, directing-engine.md, moderation-prescreen.md — points to "../../references/", outside the skill's own bundle, and the referenced sibling skills (../seedance-sequence/SKILL.md, etc.) are likewise absent from this workspace. The bundle contains no references/, scripts/, or assets/ directories at all, so navigation from this skill alone is broken and the skill is not self-contained. That is a larger structural gap than anchor 4's "minor organization gaps", though better organized than anchor 3's typical buried-reference case.

3 / 5

Total

14

/

20

Passed

Description

70%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 trigger-focused description with an explicit "use when" clause and good natural keyword coverage, anchored to a specific product niche. Its main weakness is that it describes what the user wants rather than what the skill concretely does, leaving the capability side implied. It scores at the good-not-excellent level across all four dimensions.

Suggestions

State the skill's concrete behavior explicitly, e.g. "Asks at most three plain-language questions and returns a compact director brief (under 150 words) with a recommended prompt-writing route" — this would lift specificity and completeness.

Add one or two natural trigger synonyms users are likely to say, such as "quick brief" or "fast intake questions", to broaden trigger coverage.

Sharpen the boundary against sibling skills by signaling that this is the interview/brief step that precedes prompt writing, distinguishing it from the full seedance-prompt flow.

DimensionReasoningScore

Specificity

The description names the domain ("Seedance 2.0 creative brief") and several action nouns ("a short interview, a compressed intake flow, or a quick director-style clarification"), but these are near-synonymous facets of one fast-intake capability phrased as user desires rather than distinct skill actions. It sits above anchor 2 (domain named, minimal actions) but below anchor 4 because it does not enumerate several distinct concrete actions or cover what the skill actually produces.

3 / 5

Completeness

The "when" is fully explicit ("This skill should be used when the user wants a fast Seedance 2.0 creative brief..."), and the "what" is discernible but implied through noun phrases rather than stated as skill behavior (it never says it asks up to three questions and returns a compact brief). Not anchor 5 because the what-side lacks an explicit statement of what the skill does; clearly above anchor 3 since the when-clause is concrete and specific.

4 / 5

Trigger Term Quality

Natural trigger words are well covered: "fast", "quick", "short interview", "creative brief", "compressed", "clarification", plus the product name "Seedance 2.0". A few natural phrasings users might say are missing (e.g. "quick prompt", "brief me", "fast intake questions"), which keeps it below anchor 5 but comfortably above anchor 3.

4 / 5

Distinctiveness Conflict Risk

The "Seedance 2.0" niche and speed-oriented triggers ("fast", "short", "quick") make it mostly distinct, but the skill family it routes to (seedance-prompt, seedance-prompt-short, etc., per its own routing rule) creates minor overlap risk with closely related sibling skills. Anchor 5 would require a clean niche with essentially no sibling overlap.

4 / 5

Total

15

/

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

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

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