action-choreography-camera-logic

Use for fights, chases, transformations, and high-kinetic sequences that need readable geography, motivated camera logic, impact rhythm, and continuity-safe action coverage.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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, well-structured instruction skill that delivers actionable, enumerated cinematography guidance with no wasted tokens. Adding a worked example would push actionability to the top anchor.

Suggestions

Include one short worked example (e.g., a sample fight beat broken into orientation/impact/recovery) to make the guidance fully concrete.

Add a brief verification cue such as 'check that each camera move maps to one tactical reason and that geography stays readable' to give the rules a checkpoint.

Consider a one-line 'When not to use this skill' note to sharpen distinctiveness against general video-design guidance.

Dimension	Reasoning	Score
Conciseness	Every line is lean, actionable guidance with no padding and no explanation of concepts Claude already knows; each token earns its place.	5 / 5
Actionability	Directives are concrete with enumerated choices (e.g., "reveal threat, follow force, absorb impact, or trap the subject"; "onset, spread, rupture, aftermath"), but there are no worked examples of an actual sequence, leaving some interpretation to Claude.	4 / 5
Workflow Clarity	The sections are well-organized into a logical thinking order (core rules, coverage, transformation beats, avoid), but this is a principles set rather than a sequenced process, so there are no explicit checkpoints or feedback loops.	4 / 5
Progressive Disclosure	At under 50 lines with no need for external references (no bundle files present), the well-organized section structure fully satisfies the simple-skill progressive-disclosure exception.	5 / 5
	Total	18 / 20 Passed

Description

78%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 well-targeted description that names a clear niche and explicit trigger scenarios with good keyword coverage. Its main weakness is framing the skill through desired qualities rather than concrete actions.

Suggestions

Lead with a concrete verb-action (e.g., 'Choreograph and block...') before the trigger clause so the 'what' reads as actions rather than qualities.

Add natural synonym triggers such as 'action scene', 'battle', or 'stunt sequence' to broaden keyword coverage.

Tighten the when with a 'Use when the user mentions fights, chases, or transformations...' phrasing to reach the top completeness anchor.

Dimension	Reasoning	Score
Specificity	Lists several specific applications ("fights, chases, transformations, and high-kinetic sequences") and specific qualities ("readable geography, motivated camera logic, impact rhythm, and continuity-safe action coverage"), but uses quality-descriptors rather than concrete verb-actions, so it stops short of the comprehensive concrete-action anchor.	4 / 5
Completeness	Both halves are present: the "Use for fights, chases, transformations..." clause gives an explicit when, and the qualities list gives the what, but the when lacks the "when the user mentions X" phrasing and the what is quality-based rather than action-based.	4 / 5
Trigger Term Quality	Natural domain terms like "fights, chases, transformations" and "camera logic" are terms a user would say, giving good keyword coverage, though common synonyms like "action scene", "battle", or "stunt" are missing.	4 / 5
Distinctiveness Conflict Risk	The action-choreography/camera niche with triggers like fights, chases, and transformations is clearly distinct with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/action-choreography-camera-logic/SKILL.md
Commit: 595d863

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.