CtrlK
BlogDocsLog inGet started
Tessl Logo

long-form-continuity-bible

Use for ongoing multi-shot, episodic, sequel, or continuation work that needs strong character, environment, prop, and tone consistency over time.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tightly written, well-structured instruction skill that adds only what Claude would not already infer — concrete continuity anchors, a prioritized reference order, and a failure-mode checklist — with no verbosity or concept restatement.

DimensionReasoningScore

Conciseness

The body is lean with no concept padding or unnecessary explanation; every section (Goals, Checklist, Working Rules, Reference Hierarchy, Failure Modes) earns its place and assumes Claude's competence.

3 / 3

Actionability

For an instruction-only skill the guidance is concrete and specific — explicit anchors (face shape, hair, silhouette; weapon form, glow behavior), directives ('describe the before/after state and the irreversible steps between them'), and an ordered reference priority — so absence of code is not penalized per the instruction-skill note.

3 / 3

Workflow Clarity

As a simple, single-purpose skill under 50 lines it qualifies for the simple-skill allowance: the Reference Hierarchy sequences priorities (1–4) and the Failure Modes To Block list functions as a verification gate against drift.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the under-50-line body is organized into clearly signaled sections, satisfying the simple-skill allowance for a well-organized overview with no nested references.

3 / 3

Total

12

/

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.

The description has strong, natural trigger terms and a clearly distinct niche, but frames the skill as a condition ('needs...consistency') rather than naming concrete actions, leaving the 'what it does' implied rather than explicit.

Suggestions

Lead with a concrete action clause naming what the skill does, e.g. 'Maintains character, environment, prop, and tone consistency across multi-shot, episodic, sequel, or continuation work.'

Add 2–3 specific verbs (e.g. 'locks', 'tracks', 'preserves') so the capability reads as actions rather than a stated need.

Keep the existing 'Use for...' trigger intact; prepend the action statement before it to satisfy both 'what' and 'when' explicitly.

DimensionReasoningScore

Specificity

Names the concrete domain and the dimensions to keep stable ('character, environment, prop, and tone consistency') but states no action verbs describing what the skill actually does, matching the 'names domain and some actions but not comprehensive' anchor rather than the multi-action score-3 example.

2 / 3

Completeness

The 'when' is explicit ('Use for ongoing multi-shot, episodic, sequel, or continuation work'), but the 'what' is only implied as a need ('needs strong...consistency') rather than stated as the skill's action, so it stops short of the explicit what-AND-when score-3 anchor.

2 / 3

Trigger Term Quality

Natural terms a user would say for this need are well covered — 'multi-shot, episodic, sequel, or continuation work' plus 'consistency over time' — giving good coverage of the phrasings users reach for when requesting continuity.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche — long-form continuity/sequel consistency — with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' 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.