CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

environment-scene-extraction-bible

Use for location-first, no-human, and scene-bible workflows that need stable environment naming, spatial continuity, lighting logic, and clean world extraction without character contamination.

Quality

85%

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.

A compact, well-structured rule-set skill that is lean and easy to navigate. Adding a brief worked example and an ordered checklist would lift actionability and workflow clarity from strong to fully executable.

DimensionReasoningScore

Conciseness

Lean bullet rules with no padding and no explaining of concepts Claude already knows; every line earns its place (e.g., "Lock time of day, weather, light direction, and dominant materials.").

5 / 5

Actionability

Concrete, specific instructions ("Describe foreground, midground, background, and atmosphere"; "Remove stray body parts, silhouettes, crowds") are actionable for an instruction-only skill, but no worked example grounds the rules into copy-paste-ready output.

4 / 5

Workflow Clarity

Content is well-organized into clear rule groups and the single purpose is unambiguous, but there is no sequence or checklist ordering how to apply Scene, Continuity, and No-Human rules together.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and the body is well-organized into clearly labeled sections (Scene Rules, Continuity Rules, No-Human Rules, Avoid), satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

78%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 tightly scoped, domain-specific description with an explicit trigger clause and concrete capability areas. It is distinct and well-targeted, with only minor room to sharpen the "what" into discrete actions and broaden trigger synonyms.

DimensionReasoningScore

Specificity

Lists several specific capability areas ("stable environment naming, spatial continuity, lighting logic, and clean world extraction without character contamination") but phrases them as workflow needs rather than discrete verb-led actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both halves — "Use for ... workflows" gives the when, and the capability list gives the what — but the "what" is cast as needs/capabilities rather than concrete discrete actions, so it sits just below the fully-explicit anchor.

4 / 5

Trigger Term Quality

Good coverage of natural domain terms ("location-first", "no-human", "scene-bible", "environment naming", "lighting logic") that a user would plausibly say, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined by "location-first, no-human, scene-bible" plus "clean world extraction without character contamination," giving clear distinct triggers with minimal overlap risk.

5 / 5

Total

17

/

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/environment-scene-extraction-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.