CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

Does it follow best practices?

Impact

98%

1.05x

Average score across 8 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is metcalf-solutions1/satori

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a tightly written, highly actionable control file: concrete phrasings, exact safety data, validation loops, and a clear precedence model. Its critical flaw is structural — the entire reference bundle it orchestrates does not exist, so the progressive-disclosure architecture and the detailed workflows it points to are unreachable.

Suggestions

Ship the references/ bundle that Section 1 promises (SOUL.md, clinical-spine.md, the tradition/toolkit files, all protocols, onboarding, tone-and-voice, memory-system, and core-compact.md), or inline the essential content into SKILL.md so the skill functions standalone.

Define the six-step turn sequence (Attune → Clarify → Formulate → Integrate → Translate → Anchor) in the body or in an existing clinical-spine.md file — currently only the names appear, so the core turn workflow cannot be executed from the canonical file.

Consider moving the per-country helpline table into a crisis reference file (keeping only the load trigger and one universal fallback like findahelpline.com inline) to reduce canonical-file bulk — but only once the reference bundle actually exists, since crisis-time data must remain immediately reachable.

DimensionReasoningScore

Conciseness

Dense, operational sections — precedence ladder table, tier model, note template, anti-slop prohibitions — with no explanations of concepts Claude already knows. Not 5: the ten-country helpline table is bulk data that could largely live in a crisis reference file, and a few meta lines ("Turn 1 is self-sufficient from this `<8 KB` canonical file") could be trimmed.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a verbatim safety question ("When you say that, are you thinking about ending your life?"), exact helpline numbers per country, a copy-paste-ready SATORI_NOTE template with field length constraints, named prohibited phrases, and explicit condition-to-behavior mappings. Specific examples cover the common cases.

5 / 5

Workflow Clarity

A clear sequence is present: sense risk tier, apply the precedence ladder ("re-evaluate every turn; escalate immediately if new risk emerges"), run the turn sequence, then the 4-question honesty self-check with an explicit recovery loop ("If any check fails, revise before sending"). Not 5 because the six-step Attune→Anchor sequence is only named in the body — its execution detail is deferred to a reference file.

4 / 5

Progressive Disclosure

Section 1 lays out a well-signaled, one-level-deep load order with markdown links, but every one of the ~17 referenced files is absent — no references/ directory exists in the bundle, so SOUL.md, clinical-spine.md, all protocols, toolkits, traditions, and the compact fallback are dangling links. The hub-and-spoke design is good on paper, but with the spokes missing the disclosure structure collapses and the skill is unnavigable beyond the inline summary.

2 / 5

Total

15

/

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: it names the domain and several concrete functions, gives an explicit and comprehensive when-clause with both positive triggers and anti-triggers, and sharply delimits its niche against technical work. The only weaknesses are a slightly abstract opening phrase and a few missing common synonyms for the emotional triggers.

DimensionReasoningScore

Specificity

Enumerates several concrete functions — "reflective dialogue", "tiered crisis check-ins", "continuity notes", "add 2 warm grounding sentences" — with only minor coverage gaps. It falls short of 5 because the headline "wisdom companion for inner life" is abstract and the mechanics of each function are not detailed.

4 / 5

Completeness

Explicitly answers both what ("wisdom companion... reflective dialogue, tiered crisis check-ins, continuity notes") and when ("Use for..."), plus explicit anti-triggers ("DO NOT ACTIVATE for pure coding, DevOps, SQL, git, math") and a hybrid case. The when-clause is maximally explicit with concrete trigger phrases, so it matches the top anchor rather than the 4 anchor.

5 / 5

Trigger Term Quality

Natural user phrasings are well covered: "grief", "burnout", "anxiety", "stress", "loneliness", "relationship conflict", "shadow work", "crossroads", "struggling with bug". Not 5 because common synonyms such as "depressed", "overwhelmed", "sad", or "feeling down" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (inner-life/psychological support) with distinct triggers, and the "DO NOT ACTIVATE... even if user says 'I'm stuck'" clause explicitly prevents mis-triggering on technical sessions. Minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 16 missing

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

14

/

16

Passed

Repository

MetcalfSolutions/Satori

Path

.agents/skills/satori/SKILL.md

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.