CtrlK
BlogDocsLog inGet started
Tessl Logo

think

Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.

72

Quality

88%

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

92%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, lean instruction-only skill with explicit staged sequencing, verification checkpoints, and a feedback loop. The only notable gap is the absence of a concrete worked example demonstrating a full pass through the loop.

Suggestions

Add a short worked example showing the ten stages applied to one realistic decision (e.g., a small architecture tradeoff), to lift actionability from concrete guidance to fully demonstrated execution.

Consider one or two explicit example trigger phrases mapped to expected output shapes (trivial lookup -> skip loop vs. consequential decision -> full loop) to make the scaling guidance more concrete.

DimensionReasoningScore

Conciseness

Lean and efficient throughout with no padding or explanation of concepts Claude already knows; every stage is 2-3 sentences of directive guidance and every token earns its place.

5 / 5

Actionability

Provides concrete, specific directive guidance per stage (e.g., 'smallest reversible test that could disprove the leading hypothesis') and a copy-paste output template, but lacks a worked end-to-end example of the loop applied to a real case.

4 / 5

Workflow Clarity

Clear 10-stage sequence with an explicit numbered verification discipline checkpoint and a loop-back feedback mechanism; the read-only scope means the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

Self-contained ~125-line skill with clean section headers and no bundle files needed; well-organized sections qualify for the simple-skill exception to score 5.

5 / 5

Total

19

/

20

Passed

Description

83%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 description that clearly states what the skill does, when to use it via natural trigger phrases, and how it differs from adjacent repair workflows. The main gap is specificity being a procedural meta-process rather than a list of discrete concrete actions.

DimensionReasoningScore

Specificity

Names the reasoning/decision domain and a concrete structured action (the named 10-stage loop), but the actions are a procedural meta-process rather than multiple distinct discrete outputs, leaving it just below the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (apply the 10-stage loop to consequential/ambiguous reasoning) and 'when' (concrete 'Use for...' trigger phrases), matching the clearly-and-explicitly-answers-both anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('think this through', 'deep think', 'architecture review', 'postmortem', 'tradeoff analysis', 'challenges to assumptions'), though a few common synonyms like 'reason through' or 'sanity check' are absent.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (reasoning review) plus a negative boundary ('not a deterministic vault health check or repair workflow'), with only minor overlap risk against general planning/architecture skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
AgriciDaniel/claude-obsidian
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.