CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

short-drama-hook-engineering

Use for short-drama, trailer, and retention-first storytelling that must land a hard hook in the first 1-3 seconds and keep escalation pressure inside each clip.

Quality

76%

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/short-drama-hook-engineering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, instruction-only skill whose guidance is specific, measurable, and free of padding — the body reads like a professional editor's checklist rather than an explanation of concepts Claude already knows. The only meaningful gap is the absence of worked examples and an explicit self-check for the 1-3 second hook rule.

DimensionReasoningScore

Conciseness

The body is lean bullets with zero padding — "Start as late as possible in the action. Skip warm-up exposition" and "Open on the strongest playable behavior, not neutral atmosphere" assume Claude's competence and add only domain-specific judgment. Every token earns its place, matching the anchor-5 example.

5 / 5

Actionability

Directives are concrete and measurable: "The first 1-3 seconds must deliver conflict, danger, accusation…", "a visible framing or action change roughly every 2 seconds", "Use verbs that can be performed on camera". It falls short of anchor 5 only because there are no worked examples (e.g., a sample cold-open line) covering the common cases.

4 / 5

Workflow Clarity

The per-clip shape "hook, escalation, exit bridge" gives a clear sequence, and the "Avoid" section provides negative checkpoints. It is not a 5 because there is no explicit self-verification (e.g., "check: does the opening land conflict within 3 seconds?") or rule priority — well above anchor 3, and no batch/destructive operation applies to cap it.

4 / 5

Progressive Disclosure

This is a single-file skill under 50 lines with no bundle files and no content that belongs in separate references; the four labeled sections (Hook Rules, Editorial Rhythm, Writing Heuristics, Avoid) are well-organized, which per the rubric's simple-skill guidance merits a 5.

5 / 5

Total

18

/

20

Passed

Description

56%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.

The description has a strong, explicit trigger clause and a distinctive niche, but it never states what the skill does — it reads as a scope statement rather than a capability description. Adding 2-3 concrete actions (e.g., engineers cold-opens, paces escalation, structures clip endings) would raise both specificity and completeness.

Suggestions

Add concrete capability verbs to the description, e.g., "Engineers cold-open hooks, structures per-clip escalation, and edits openings to start at the latest playable moment" — this lifts specificity from 2 toward 4.

State the 'what' explicitly alongside the existing 'Use for…' trigger clause so completeness moves from a weakly-implied 'what' to both-halves-present (anchor 4).

Broaden trigger coverage with natural synonyms such as "micro-drama", "vertical drama", or "cliffhanger endings" to push trigger-term quality from 4 to 5.

DimensionReasoningScore

Specificity

"Use for short-drama, trailer, and retention-first storytelling" names the domain clearly but contains no concrete actions — no verb describes what the skill actually does (write, edit, pace, critique). It sits above anchor 1 (pure vagueness) but below anchor 3, which requires 1-2 concrete capabilities.

2 / 5

Completeness

The 'when' is explicit ("Use for short-drama, trailer, and retention-first storytelling"), but the 'what' is only implied — the description states constraints on the content ("must land a hard hook in the first 1-3 seconds") rather than the skill's capabilities. Scoring only what is explicit, this matches anchor 3 rather than anchor 4.

3 / 5

Trigger Term Quality

Includes natural terms users would say — "short-drama", "trailer", "hook" (plus tags "pacing", "escalation") — giving good keyword coverage. It falls short of anchor 5 because common variations like "micro-drama", "vertical drama", or "cliffhanger" are missing.

4 / 5

Distinctiveness Conflict Risk

"Short-drama, trailer, and retention-first storytelling" carves a clear niche with distinct triggers, but "trailer" and "storytelling" carry minor overlap risk with general video-editing or narrative skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nolanx-ai/nolanx.ai

Path

skills/short-drama-hook-engineering/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.