CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

81%

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

86%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.

The body is a tight, well-structured instruction-only skill with concrete continuity rules and a clear reference priority order. Its only gap is the lack of worked examples and explicit validation checkpoints, which keep actionability and workflow_clarity at 4.

DimensionReasoningScore

Conciseness

The body is lean bullet-and-phrase prose with no padding and no explanation of concepts Claude already knows; every section earns its tokens, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Concrete directives like "describe the before/after state and the irreversible steps between them" and "Preserve battle damage, dirt, blood, cracks...unless story logic clears them" give mostly executable guidance; not a 5 because no worked examples illustrate the rules in practice.

4 / 5

Workflow Clarity

The ordered Reference Hierarchy (1-4) and the if-then Working Rules give a clear prioritized sequence; as a non-destructive guidance skill no validation cap applies, but explicit checkpoints are absent so it stays below 5.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external bundle files (none exist), and is organized into clear labeled sections (Goals, Continuity Checklist, Working Rules, Reference Hierarchy, Failure Modes), matching the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

70%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.

The description has a strong, explicit trigger clause and clear niche distinctiveness with good natural keywords. It is slightly weak on stating concrete actions, framing the skill mostly as a use-case rather than listing what it does.

Suggestions

Lead with a concrete action verb stating what the skill does (e.g., 'Tracks and enforces character, environment, prop, and tone continuity across...') before the 'Use for' trigger clause.

Add one or two natural synonyms or file/format terms a user might say to broaden trigger coverage toward a 5.

DimensionReasoningScore

Specificity

The description enumerates concrete consistency domains ("character, environment, prop, and tone consistency") but frames them as a use-case need rather than listing the concrete actions the skill performs, matching the anchor that names the domain with limited action detail.

3 / 5

Completeness

It has an explicit "Use for..." trigger clause (when) plus an implied maintain-consistency what ("needs strong...consistency over time"), with the when clearly explicit; not a 5 because the what is implied rather than stated as concrete actions.

4 / 5

Trigger Term Quality

Natural niche keywords "multi-shot, episodic, sequel, or continuation" are terms a user would plausibly say, giving good coverage just short of comprehensive synonym/file-extension breadth.

4 / 5

Distinctiveness Conflict Risk

The long-form continuity niche with triggers like "episodic, sequel, continuation" is clearly distinct with minimal overlap risk against other skills; not a 5 only because the phrasing is use-case oriented rather than action oriented.

4 / 5

Total

15

/

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/long-form-continuity-bible/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.