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.02x
Quality

88%

Does it follow best practices?

Impact

95%

1.02x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

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 tightly engineered operational core: every section is executable configuration rather than explanation, with an unusually strong safety spine (tiered risk model, tool lockout, verbatim scripts) and a genuine validate-and-recover loop. The main residual issues are minor redundancy between the precedence ladder and the risk model, and two bundle files missing from the root load order.

Suggestions

Consolidate the tool-lockout/'code waits' language between Section 2 (Precedence Ladder) and Section 5 (Tier 1/Tier 2 rows) so each rule is stated once and cross-referenced.

Add `references/model-calibration.md` and `references/crisis-sources.json` to the Section 1 load-order list (e.g., under a 'Calibration & Verification' entry) so every bundle file is discoverable one level deep from SKILL.md.

Either inline one sentence per step of the 6-step turn sequence (what 'Formulate' or 'Anchor' concretely requires) or explicitly state that clinical-spine.md is mandatory reading before the first full session.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no space is spent explaining what grief, IFS, or polyvagal theory are — and safety-critical data like the helpline table earns its tokens. Minor duplication keeps it below anchor 5: "Lock all tools"/"code waits" in the Precedence Ladder repeats the Tier 1/Tier 2 rows, and "stay present" appears twice within the Tier 2 bullet.

4 / 5

Actionability

Guidance is copy-paste ready for an instruction-only skill: the exact safety question ("When you say that, are you thinking about ending your life?"), verified helpline numbers per country, a fully specified SATORI_NOTE format with per-field char limits, the verbatim trust warning, and concrete anti-slop examples ("clarity, purpose, and peace", "Here's the thing"). The precedence ladder enumerates every input class with an unambiguous behavior.

5 / 5

Workflow Clarity

The precedence ladder is a clear ranked decision sequence re-evaluated "every turn", and the honesty self-check plus Recovery Rule ("If any check fails, revise before sending") forms an explicit validate-then-fix feedback loop. Minor validation gaps hold it at 4: the six-step turn sequence ("Attune → Clarify → Formulate → Integrate → Translate → Anchor") is only named, with execution checkpoints delegated to clinical-spine.md, and the body never links the helpline verification source.

4 / 5

Progressive Disclosure

A canonical sub-8KB overview with a numbered, category-labeled load order linking 16 reference files — all of which exist and are one level deep. Two minor organization gaps: `crisis-sources.json` and `model-calibration.md` are absent from the load order and only discoverable via clinical-spine.md, and reference files cross-link each other (e.g., traditions-quickref.md → traditions-eastern.md), adding mild navigation depth.

4 / 5

Total

17

/

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.

An exemplary trigger description: it answers what, when, and when-not with concrete user-quotable phrases and explicitly defuses the most likely misfire case. The only slack is a slightly abstract opening clause and a few missing common synonyms for distress states.

DimensionReasoningScore

Specificity

Concrete actions are stated — "tiered crisis check-ins", "continuity notes", "solve technical task first, then add 2 warm grounding sentences" — listing several specific behaviors beyond the generic opener "Psychologically grounded wisdom companion for inner life". Not anchor 5 because the lead framing is abstract and the reflective-dialogue behavior itself is not further specified; not anchor 3 because more than 1-2 concrete actions are given.

4 / 5

Completeness

Both what and when are explicit: the what covers reflective dialogue, tiered crisis check-ins, continuity notes, and hybrid grounding behavior; the when enumerates concrete trigger phrases ("Use for reflective dialogue, grief, dark-night, burnout...") plus explicit negative triggers ("DO NOT ACTIVATE for pure coding, DevOps, SQL, git, math") and the tricky-case rule. This matches the anchor-5 pattern of answering both with concrete trigger phrases, well above anchor 4's 'when could be more specific'.

5 / 5

Trigger Term Quality

Strong natural-language coverage users would actually say: "grief, dark-night, burnout, anxiety, stress, loneliness, relationship conflict, shadow work, crossroads", plus quoted user phrases ("I'm stuck", "struggling with bug") and "imposter syndrome". A few common terms are missing (e.g., depression, feeling lost, existential dread), so it sits at anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (inner-life / emotional support) with unusually strong disambiguation: negative triggers for technical domains and an explicit rule for the highest-risk collision case ("even if user says 'I'm stuck' or 'struggling with bug'"), plus a defined hybrid path for burnout/imposter-syndrome in technical sessions. Minimal conflict risk, matching anchor 5.

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