CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

80%

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 ./skills/world-asset-identity-lock/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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-organized rule set that respects the token budget and needs no bundle files. Its one real gap is actionability: the rules say what to lock but never show how, with no template or worked example of an identity core or stable ID.

Suggestions

Add a short worked example of an identity core (e.g. a 3-4 line locked block for one hero character with its stable ID) so 'reuse the same identity core' is executable rather than abstract.

Show one before/after prompt pair demonstrating identity core plus per-shot action, the central prompt rule of the skill.

Make the continuation checkpoint explicit — e.g. 'confirm the asset's silhouette and palette match the last stable state before writing the next shot' — to add a validation step to the workflow.

DimensionReasoningScore

Conciseness

The body is a lean rule list — "Assign stable ids and reuse them everywhere", "New shots inherit the last confirmed stable state" — with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Directives are specific about what to lock ("face, silhouette, costume logic, material response, palette, and behavioral signature") but key execution details are missing: there is no example of a stable id scheme, no sample identity core, and no worked before/after prompt showing core-plus-per-shot-action. This lands between anchor 3 (concrete but incomplete, missing key details) and anchor 4 (mostly executable with minor gaps).

3 / 5

Workflow Clarity

Sections follow a logical sequence — lock identity, reuse core in prompts, inherit state on continuation — and "last confirmed stable state" implies a confirmation checkpoint. However, there is no explicit validation step for verifying identity held before continuing a run, which anchor 5 requires.

4 / 5

Progressive Disclosure

The body is under 50 lines with no external content needed, and it is organized into clean sections (Identity Lock, Prompt, Continuation, Avoid) with no inlined material that belongs in separate files. Per the simple-skill guideline this matches anchor 5.

5 / 5

Total

17

/

20

Passed

Description

73%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 concise, well-scoped trigger description with an explicit use clause and strong domain-specific vocabulary. Its main weakness is that it describes when to use the skill more concretely than what the skill actually does.

Suggestions

Add one or two concrete actions to the description, e.g. 'Assigns stable IDs and locks identity cores (face, silhouette, costume, palette) for recurring assets' before the 'Use for' clause.

Include common user phrasings as triggers, such as 'same character across shots', 'character consistency', or 'identity drift', to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Use for recurring characters, props, creatures, costumes, and environments that must keep stable identity" names the domain richly and states one capability (keeping identity stable), but lists no concrete actions such as assigning stable IDs or locking identity cores. It sits between anchor 2 (actions minimal) and anchor 4 (several specific actions), so 3 is the best fit.

3 / 5

Completeness

The 'when' is explicit ("Use for recurring characters... across multi-shot generation, world assets, and continuation runs") and a 'what' is present ("keep stable identity"), satisfying both halves. The 'what' is thin — it never states what the skill operationally does (assign IDs, lock traits, reuse identity cores) — so it falls short of anchor 5's fully explicit what-and-when.

4 / 5

Trigger Term Quality

Natural domain terms are present ("recurring characters", "props", "creatures", "costumes", "multi-shot", "continuation runs"), giving good keyword coverage. Common variations users might say — "same character", "consistent", "drift", "continuity" — are missing, so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"multi-shot generation", "continuation runs", and "world assets" carve out a clear niche in generative asset pipelines with distinct triggers, minimizing overlap with generic image/video skills. It is not so generic that any sibling skill would capture it, matching anchor 5 rather than anchor 4's 'minor overlap risk'.

5 / 5

Total

16

/

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.

Validation — 15 / 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

Path

skills/world-asset-identity-lock/SKILL.md

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.