continuity-editing-axis-match

Use for shot sequencing, axis preservation, 180-degree rule awareness, match-on-action design, and smooth visual continuity between cuts.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.nolanx/skills/continuity-editing-axis-match/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-organized, and free of padding, with a distinct, clearly sectioned structure appropriate for a simple instruction-only skill. It is held back only by actionability and workflow clarity, where directives lack an explicit ordered procedure and validation step for confirming axis continuity.

Suggestions

Add a short ordered procedure (e.g. establish axis -> place coverage shots -> cut on action -> verify screen direction) with a final verification step before delivering the sequence.

Make the storyboard-application guidance more executable by giving a concrete output template the agent should fill per shot (direction, axis status, cut point).

Add a quick checkpoint to re-confirm screen direction and axis integrity after each cut so errors are caught before delivery.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's domain knowledge — it lists rules and heuristics as terse bullet points without restating what continuity editing or the 180-degree rule are, so every token earns its place.	3 / 3
Actionability	Guidance is concrete in places ('Cut during the peak readable phase of movement', 'State motion direction: left-to-right...') but consists of directives rather than executable, copy-paste-ready artifacts; for an instruction-only skill this is actionable but missing some specific operational detail.	2 / 3
Workflow Clarity	Sections are logically grouped (Rules, Match-On-Action Heuristics, Apply To AI Storyboards) giving an implicit sequence, but there are no explicit ordered steps or validation/feedback checkpoints for confirming axis preservation before delivery.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines with no external references, the content is well-organized into clearly labeled sections, satisfying the rubric's simple-skills allowance for a top score without separate files.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and occupies a distinct, conflict-free niche, but it omits an explicit 'Use when...' trigger clause and only partially covers the natural vocabulary a user might voice, capping completeness and trigger quality at the mid level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when sequencing shots, preserving screen direction across cuts, or designing match-on-action continuity.'

Broaden natural-language trigger terms to include common user phrasings like 'match cuts', 'crossing the line', 'screen direction', and 'continuity between cuts'.

Lead with the 'Use when...' guidance after the capability list so the when-to-use trigger is unambiguous rather than implied.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete actions — 'shot sequencing, axis preservation, 180-degree rule awareness, match-on-action design, and smooth visual continuity between cuts' — comparable to the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit 'Use when...' trigger clause; the when-guidance is only implied by the topic listing, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	It surfaces domain-relevant terms (180-degree rule, match-on-action, axis), but everyday phrasing a user would actually say (e.g. 'match cuts', 'crossing the line', 'screen direction', 'continuity') is only partially covered, leaving common variations missing.	2 / 3
Distinctiveness Conflict Risk	The continuity-editing niche is well-defined with distinct technical triggers (180-degree rule, axis of action, match-on-action), making conflict with unrelated skills unlikely.	3 / 3
	Total	10 / 12 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: .nolanx/skills/continuity-editing-axis-match/SKILL.md
Commit: 595d863

Reviewed: about 10 hours 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.