CtrlK
BlogDocsLog inGet started
Tessl Logo

dialogue-performance-blocking

Use for dialogue scenes, emotional performance beats, actor blocking, lip-sync-driven moments, and character interaction with clear emotional progression.

61

Quality

72%

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 ./.nolanx/skills/dialogue-performance-blocking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A lean, well-organized instruction-only skill with concrete behavioral categories and decision rules. It is held back by the absence of a worked example and a lack of explicit end-to-end sequencing or alignment-check checkpoints.

Suggestions

Add one short worked example: a sample line with its objective, subtext, emotional vector, and resulting body/facial behavior plus camera proximity, so the per-line template is demonstrated end-to-end and actionability reaches 3.

Insert an explicit sequenced workflow (analyze the scene -> assign per-line objectives/subtext -> block movement and framing -> verify lip-sync/emotional-arc alignment) with a final 'check that arcs and lip-sync align' checkpoint to lift workflow_clarity to 3.

DimensionReasoningScore

Conciseness

The body is a lean set of bullets and rules that assumes Claude knows what blocking, subtext, and lip-sync are, with no padding or explaining of basic concepts, matching the score-3 'every token earns its place' anchor.

3 / 3

Actionability

It gives a concrete per-line template (objective / subtext / emotional vector / body behavior / facial behavior) and a decision rule ('every line should either attack, defend, reveal, conceal, or break'), but no worked example shows what finished output looks like, leaving it at 'concrete guidance but incomplete' rather than fully copy-paste-ready.

2 / 3

Workflow Clarity

The per-line 'Performance Design' template gives a partial sequence, but there is no explicit end-to-end flow from scene analysis to final blocking, and no checkpoint verifying that 'lip-sync and emotional arcs aligned' (stated in Goals) actually holds, matching the score-2 'sequence present but checkpoints missing' anchor.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no external references needed and is organized into clear sections (Goals, Performance Design, Blocking Rules, Dialogue Scene Rules, Lip Sync / Voice Rules), so per the simple-skills scoring note it earns 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

72%

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, niche description with explicit trigger guidance and low conflict risk. Its main weakness is that it states when to use the skill far more clearly than what the skill produces.

Suggestions

Add a concrete action verb + output before the 'Use for' clause, e.g. 'Designs actor blocking and emotional performance beats for dialogue scenes. Use for ...', so 'what it does' is explicit and completeness/specificity reach 3.

Keep the natural domain keywords but pair each with the produced artifact (e.g. 'blocking plans', 'performance notes', 'lip-sync timing') to turn domain references into concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain richly ('dialogue scenes, emotional performance beats, actor blocking, lip-sync-driven moments, and character interaction') but uses no concrete action verbs describing what the skill produces, so it matches 'names domain and some actions, but not comprehensive' rather than the multi-action score-3 anchor.

2 / 3

Completeness

The 'Use for ...' clause explicitly answers when to invoke the skill, but what it actually outputs (a blocking plan, performance notes) is only implied, so it does not reach the score-3 'clearly answers both what AND when' anchor; it is above 1 because the 'when' is explicit and strong.

2 / 3

Trigger Term Quality

Terms a video/film user would naturally say ('dialogue scenes', 'actor blocking', 'lip-sync', 'character interaction') give good coverage of natural trigger language for this niche, matching the score-3 anchor despite slight specialization.

3 / 3

Distinctiveness Conflict Risk

The niche (dialogue performance/blocking with lip-sync and emotional arcs) is clearly bounded with distinct triggers unlikely to collide with other skills, matching the score-3 anchor.

3 / 3

Total

10

/

12

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.