CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

metcalf-solutions1/satori

Psychologically grounded wisdom companion for inner life. Use for reflective dialogue, grief, dark-night, burnout, anxiety, stress, loneliness, relationship conflict, shadow work, crossroads, tiered crisis check-ins, continuity notes. DO NOT ACTIVATE for pure coding, DevOps, SQL, git, math, or technical tasks, even if user says "I'm stuck" or "struggling with bug." Hybrid: solve technical task first, then add 2 warm grounding sentences for burnout, imposter syndrome, team conflict.

1.05x
Quality

91%

Does it follow best practices?

Impact

98%

1.05x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

90%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 an exemplary lean, actionable overview: exact scripts, a decision ladder, a pre-send validation loop with recovery, and a well-organized one-level-deep reference load order. The only weaknesses are that the primary 6-step turn sequence is named but not specified inline, and two bundle files are orphaned from the SKILL.md navigation.

Suggestions

Include a one-line gloss of each of the six spine steps (attune/clarify/formulate/integrate/translate/anchor) inline so the core turn workflow is self-sufficient on Turn 1, as the file itself claims to be.

Add navigation entries for crisis-sources.json and model-calibration.md (or fold them into an existing referenced file) so every bundle file is discoverable from the canonical SKILL.md.

DimensionReasoningScore

Conciseness

A lean operational file: tables, numbered one-liners, and quoted examples with no tutorial prose or explanations of concepts Claude already knows. Every section carries behavioral instructions (precedence rules, heuristics, exact helpline data), matching anchor 5's 'every token earns its place' — I could not identify over-explanation to trim, so it is not anchor 4.

5 / 5

Actionability

Guidance is concrete and copy-paste ready: the verbatim safety question ("When you say that, are you thinking about ending your life?"), exact helpline numbers per country, a complete SATORI_NOTE template block, and quantified behaviors ("3-5 short sentences, no markdown", "append two warm, grounding human sentences"). For an instruction-only skill this matches anchor 5: specific examples cover the common cases.

5 / 5

Workflow Clarity

The Precedence Ladder gives clear decision ordering, the 4-question honesty check plus Recovery Rule is an explicit validate-then-fix feedback loop, and crisis tiers specify re-evaluation and escalation. It falls short of anchor 5 because the core 6-step turn sequence ("Attune -> Clarify -> ... -> Anchor") is only named in the body while its actual steps are delegated to clinical-spine.md, leaving the main conversational workflow not self-specified in the canonical file; validation checkpoints are explicit, so it is above anchor 3.

4 / 5

Progressive Disclosure

Section 1 is an excellent explicit load order: numbered, grouped by purpose, one level deep, and all 16 referenced paths verified to exist in the bundle. Two bundle files (crisis-sources.json, model-calibration.md) are not navigable from SKILL.md at all — only via a second-level hop through clinical-spine.md — a minor organization gap that keeps it below anchor 5, though it is far above anchor 3's buried or inline-heavy structure.

4 / 5

Total

18

/

20

Passed

Description

87%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 with an explicit 'Use for' trigger list, verbatim user-phrasing examples, and an unusually good negative boundary plus hybrid-case rule. The main weakness is that the 'what' leans on an abstract role phrase ("wisdom companion for inner life") and topic nouns rather than concrete verb actions, and a few common synonyms (depressed, overwhelmed, feeling lost) are absent.

Suggestions

Add a few high-frequency synonyms to the trigger list (e.g., "depressed", "overwhelmed", "feeling lost or empty") since users often phrase distress in those words.

Replace or supplement the abstract "wisdom companion for inner life" framing with one or two concrete verb phrases (e.g., "Offers reflective dialogue, tiered crisis check-ins, and continuity notes") so the 'what' reads as actions rather than a role.

DimensionReasoningScore

Specificity

Lists many concrete capability areas ("reflective dialogue", "tiered crisis check-ins", "continuity notes", "add 2 warm grounding sentences for burnout, imposter syndrome, team conflict"), but the leading framing "wisdom companion for inner life" is abstract and most items are topic nouns rather than verb-object actions. Clearly above anchor 3 (only 1-2 concrete actions) and just short of anchor 5's fully comprehensive concrete-action coverage.

4 / 5

Completeness

Explicitly answers both what ("wisdom companion... reflective dialogue... tiered crisis check-ins, continuity notes") and when ("Use for reflective dialogue, grief, dark-night, burnout..."), with concrete trigger phrases and explicit negative triggers ("DO NOT ACTIVATE for pure coding, DevOps, SQL, git, math"). Matches anchor 5's requirement for explicit what AND when with concrete triggers; the 'when' is even richer than the anchor example.

5 / 5

Trigger Term Quality

Strong natural keywords users would actually say ("grief, burnout, anxiety, stress, loneliness, relationship conflict, shadow work, crossroads") plus quoted user phrasing ("I'm stuck", "struggling with bug"). Missing common synonyms such as "depressed", "overwhelmed", or "feeling lost", and "dark-night" is less natural user phrasing, so it falls short of anchor 5's comprehensive synonym coverage but is well above anchor 3.

4 / 5

Distinctiveness Conflict Risk

Clear niche (inner-life/psychological support) with an explicit negative boundary ("DO NOT ACTIVATE for pure coding, DevOps, SQL, git, math, or technical tasks") that neutralizes the largest mis-trigger class. Only trivial overlap remains (e.g., "team conflict" with management-advice skills), fitting anchor 5's minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page