CtrlK
BlogDocsLog inGet started
Tessl Logo

world-asset-identity-lock

Use for recurring characters, props, creatures, costumes, and environments that must keep stable identity across multi-shot generation, world assets, and continuation runs.

59

Quality

68%

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/world-asset-identity-lock/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.

The body is concise, well-organized, and appropriately scoped for a simple single-purpose skill, but it would benefit from a concrete identity-core example and an explicit verification step to confirm identity stability across shots.

Suggestions

Add a short example of an identity core (e.g., a compact id + locked-traits block) so the 'assign stable ids' and 'reuse them' guidance is copy-paste ready.

Include an explicit verification checkpoint (e.g., 'Before generating the next shot, confirm the reused identity core matches the last confirmed state') to close the continuation loop.

DimensionReasoningScore

Conciseness

The body is lean and rule-based with no padding or explanations of concepts Claude already knows; every line ('Assign stable ids and reuse them everywhere', 'Separate immutable traits from variable shot-specific behavior') earns its place.

3 / 3

Actionability

Directives like 'Lock face, silhouette, costume logic, material response, palette, and behavioral signature' are concrete, but there is no example identity-core format or template showing how to encode or reuse an id, leaving the guidance incomplete for direct execution.

2 / 3

Workflow Clarity

Rules are organized into clear sections and the continuation rule is procedural ('New shots inherit the last confirmed stable state'), but this multi-shot (batch-like) operation lacks an explicit validation/verification step to confirm identity stability, which caps the score at 2.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and its content is organized into well-labeled sections (Identity Lock Rules, Prompt Rules, Continuation Rules, Avoid), satisfying the simple-skill criterion for a top score.

3 / 3

Total

10

/

12

Passed

Description

65%

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 has a clear, distinctive niche and an explicit 'Use for' trigger covering both what and when, but it lists domain objects rather than concrete actions and uses second-person imperative voice rather than third person.

Suggestions

Rewrite in third person to name concrete actions (e.g., 'Assigns stable identity ids and locks silhouette, palette, and costume logic for recurring characters, props, and environments').

Add common user trigger variations such as 'character consistency' or 'continuity' phrasing alongside the technical terms.

DimensionReasoningScore

Specificity

Lists concrete domain objects ('recurring characters, props, creatures, costumes, and environments', 'multi-shot generation', 'world assets', 'continuation runs') but describes conditions rather than actions, and the imperative 'Use for' is second-person voice, triggering the -1 specificity penalty from a base of 2.

1 / 3

Completeness

The 'Use for ...' clause explicitly states the trigger condition, and 'must keep stable identity' states what the skill does, so both what and when are answered with an explicit trigger.

3 / 3

Trigger Term Quality

Relevant natural terms like 'recurring characters' and 'stable identity' appear, but 'multi-shot generation', 'world assets', and 'continuation runs' lean technical and common user variations are missing.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply defined (asset identity continuity across multi-shot generation and continuation runs), making it unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

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.