CtrlK
BlogDocsLog inGet started
Tessl Logo

cinematic-story-architecture

Use for story-driven film, trailer, short drama, adaptation, or multi-shot video requests that need strong narrative escalation, beat design, and production-ready scene structure.

69

Quality

87%

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

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.

The body is a tight, well-structured instruction-only skill that assumes Claude's competence and gives a concrete narrative framework. Its main gap is the absence of a worked example and an explicit validation loop, though neither is strictly required for a generative skill.

Suggestions

Add one short worked example showing a 3-5 beat breakdown for a representative trailer or short-drama request to make the framework fully concrete.

Add an explicit self-check step after beat generation (e.g. 'Verify each beat raises stakes, reveals, or reverses; revise if any beat only explains') to close the validation loop.

Consider folding the Beat Design Heuristics into the Workflow or Structural Rules to reduce section count, since the skill is already compact.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: short sections of bullet guidance with no padding and no explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Concrete, specific instruction guidance ('Lock the narrative engine: protagonist desire, obstacle/pressure, turning point, payoff') with per-beat fields defined, but lacks a fully worked example beat sequence to anchor the common case.

4 / 5

Workflow Clarity

A clear five-step workflow with an implicit checkpoint in step 5 ('Ensure each successive beat either raises stakes, reveals new information, or reverses power'), but no explicit validate-and-retry feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into well-labeled sections (Goals, Workflow, Structural Rules, Beat Design Heuristics, Output Requirements, Guardrails) for easy navigation.

5 / 5

Total

18

/

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.

The description is well-constructed, pairing an explicit 'Use for' trigger clause naming natural film/narrative terms with concrete deliverables. It clearly distinguishes the skill's narrative-architecture purpose with only minor overlap risk.

DimensionReasoningScore

Specificity

Lists several concrete deliverables ('narrative escalation, beat design, and production-ready scene structure') alongside the named domain, but stops short of comprehensive coverage of all production tasks.

4 / 5

Completeness

Explicitly answers both when ('Use for story-driven film, trailer, short drama, adaptation, or multi-shot video requests') and what ('strong narrative escalation, beat design, and production-ready scene structure') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger coverage ('film, trailer, short drama, adaptation, multi-shot video') that users would actually say, though a few synonyms (e.g. screenplay, scene, storyboard) are absent from the description.

4 / 5

Distinctiveness Conflict Risk

Carves a clear story-driven narrative niche with distinct triggers, though minor overlap risk remains with more general video-generation skills.

4 / 5

Total

17

/

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