CtrlK
BlogDocsLog inGet started
Tessl Logo

world-model-diagnostic

Twenty-minute conversational diagnostic for assessing a company's world-model readiness. Use when the user wants to map their company to the right world-model paradigm, identify where the highest-fidelity signal lives, audit the boundary layer between facts and interpretation, flag simulated-judgment exposure, and leave with a first/second/third build sequence. Works in plain chat and compounds when Open Brain search/capture tools are present.

71

Quality

87%

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

82%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 well-structured, highly actionable diagnostic workflow with clear phase sequencing and concrete rules. Minor conciseness redundancy and the absence of any reference-file split keep it from the top band.

Suggestions

Deduplicate the final-assessment output contract between the Phase 5 section and the Persistence Contract to recover tokens.

Make the validation/checkpoint steps explicit (e.g., a 'confirm intake coverage before classification' gate) to push workflow clarity higher.

Consider moving the detailed Persistence Contract artifact schemas into a short reference file so SKILL.md stays a tighter overview.

DimensionReasoningScore

Conciseness

Mostly lean procedural guidance with no padding of concepts Claude already knows, though the final-assessment output contract is restated in the Persistence Contract and could be tightened.

4 / 5

Actionability

Provides concrete executable guidance: explicit paradigm-mapping rules with thresholds, a five-principle classification taxonomy with labels, a per-flow audit field list, and a fixed output contract.

5 / 5

Workflow Clarity

Five clearly ordered phases with a provisional-until-audit checkpoint and a Firm-finding/Inference/Open-question labeling gate; validation is more implicit than explicit, keeping it below a 5.

4 / 5

Progressive Disclosure

Well-organized into clearly named sections with no nesting, but everything lives in one file with no external references; beyond the simple-skill threshold yet still cleanly navigable.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong, specific description that clearly states what the skill does and when to use it, with concrete trigger guidance and a distinctive niche. Slightly niche vocabulary keeps trigger-term quality just short of fully comprehensive.

DimensionReasoningScore

Specificity

Lists five concrete actions — map paradigm, identify highest-fidelity signal, audit the boundary layer, flag simulated-judgment exposure, produce a first/second/third build sequence — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (twenty-minute conversational diagnostic for world-model readiness with five concrete actions) and 'when' (a 'Use when the user wants to...' clause with concrete triggers).

5 / 5

Trigger Term Quality

Includes a 'Use when the user wants to...' clause with several relevant phrases, but terms like 'world-model paradigm' and 'simulated-judgment exposure' skew toward specialized jargon rather than universally natural phrasings.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche — a world-model readiness diagnostic — with distinctive triggers and minimal overlap risk with other skills; written in third person.

5 / 5

Total

19

/

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.

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
NateBJones-Projects/OB1
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.