CtrlK
BlogDocsLog inGet started
Tessl Logo

cinematic-hit-marking-action-director

Use for combat, chase, transformation, impact-heavy, or high-kinetic action video prompts that need 15-second temporal slicing, exact hit marks, physical feedback, non-centered camera choreography, and cinematic impact readability.

67

Quality

81%

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

80%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 concise, well-organized instruction skill with concrete technical specs and clean section structure. The main gap is workflow clarity: it reads as a categorized rulebook rather than a sequenced process with validation checkpoints, and a worked example would lift actionability.

Suggestions

Add a brief worked example showing one 15-second clip fully annotated (intervals + hit marks + camera intent) so the guidance is copy-paste ready.

Reframe the rules as a short ordered checklist with an explicit 'verify' step (e.g. confirm each hit mark has impact frame + screen shake + particle ejection) to add validation checkpoints.

Add an explicit trigger line in the body restating when to apply the skill, mirroring the description's 'Use when' clause.

DimensionReasoningScore

Conciseness

Lean bullet sections with no padding or over-explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Concrete, specific guidance ('hit marks accurate to 0.1 seconds', '4-5 core action intervals', '85mm, T1.8, ARRI Master Primes'), but lacks a worked example showing a complete annotated prompt output.

4 / 5

Workflow Clarity

Rules are organized into clear categories with a loose implicit sequence (split intervals -> place hit marks -> camera -> asset -> optical), but there are no explicit validation checkpoints or error-recovery feedback loops.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is split into well-signaled sections (Core Rules, Camera Rules, Asset Consistency, Optical Lock), satisfying the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

82%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, specific description with concrete capabilities and explicit trigger guidance, clearly distinguishing it from sibling skills. The only weakness is the second-person 'Use for' phrasing rather than third-person voice.

Suggestions

Rewrite in third person (e.g. 'Marks 15-second action clips with exact hit marks, physical feedback, and non-centered camera choreography. Use when a video beat contains combat, chases, impacts, transformations, or high-kinetic action.') to avoid the voice penalty.

Add a couple of common user synonyms (fight, battle, explosion) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('15-second temporal slicing, exact hit marks, physical feedback, non-centered camera choreography, and cinematic impact readability'), but the second-person imperative 'Use for' triggers the voice penalty, reducing the score by one.

3 / 5

Completeness

Explicitly answers both 'what' (temporal slicing, hit marks, choreography, impact readability) and 'when' ('Use for combat, chase, transformation, impact-heavy, or high-kinetic action video prompts') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural action-video terms ('combat, chase, transformation, impact-heavy, high-kinetic action video') give good coverage, though a few common synonyms (e.g. fight scene, battle, explosion) are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (cinematic action hit-marking) with distinct triggers and minimal overlap risk with other skills.

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

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