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.

74

Quality

92%

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.

A tightly written, highly actionable conversational-diagnostic skill with a clear phased workflow, explicit output contracts, and appropriate validation checkpoints. It models its own fact-vs-inference thesis well and respects the token budget.

DimensionReasoningScore

Conciseness

Lean, well-organized prose that assumes Claude's competence without explaining basic concepts; every section earns its place (Purpose, Modes, Rules, Paradigm Mapping, Workflow).

3 / 3

Actionability

Highly actionable instruction-only guidance: explicit classification vocabularies, a concrete output contract (Firm findings / Inferences / Open questions / build order), quoted prompt patterns, specified flow-audit fields, and exact persistence artifact names with prefixes.

3 / 3

Workflow Clarity

A clearly sequenced 5-phase workflow (Orientation through Final Assessment) with provisional-validation checkpoints ('Treat this as provisional until the boundary audit is done', 'Only move the order around when the evidence is strong'); this interactive diagnostic does not require batch/destructive feedback loops.

3 / 3

Progressive Disclosure

A single cohesive diagnostic flow with clearly labeled sections and no nested/deep references; it needs no external bundle files and is well-organized as one overview.

3 / 3

Total

12

/

12

Passed

Description

85%

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 with explicit 'Use when' triggers and a clear niche. Its main weakness is trigger-term quality: the description relies on paradigm-specific jargon rather than the natural phrasings users would actually say.

Suggestions

Soften jargon with natural phrasings users would actually say (e.g., 'figure out which world-model architecture fits us', 'audit where our system makes interpretive calls') alongside the technical terms.

Consider adding the everyday trigger phrases already listed in the body's 'Direct-Use Trigger Prompts' directly into the description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('map their company to the right world-model paradigm', 'identify where the highest-fidelity signal lives', 'audit the boundary layer', 'flag simulated-judgment exposure', 'leave with a first/second/third build sequence'), matching the multi-action anchor; uses third person.

3 / 3

Completeness

Explicitly answers both what ('Twenty-minute conversational diagnostic for assessing...') and when via a detailed 'Use when the user wants to...' clause.

3 / 3

Trigger Term Quality

Contains relevant terms ('world-model paradigm', 'boundary layer', 'simulated-judgment exposure') but leans on specialized jargon rather than natural phrasings a user would say verbatim; the body's trigger prompts show better natural phrasing that the description itself lacks.

2 / 3

Distinctiveness Conflict Risk

A clearly defined niche (world-model readiness, boundary-layer auditing, simulated-judgment exposure) with distinct triggers unlikely to overlap with unrelated skills.

3 / 3

Total

11

/

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