SKILLEMALL.ai
GitHub ↗ RU Sign in

BC therapy-mode

Comprehensive AI-assisted therapeutic support framework with CBT, ACT, DBT, MI, session notes CLI, and crisis protocols.

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 7 962 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Comprehensive AI-assisted therapeutic support framework with CBT, ACT, DBT, MI, session notes CLI, and crisis protocols.

As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
C
50/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7962 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 50/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 14 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 70Execution cost. Instruction body is 7962 tokens
  • 85Steps. 313 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (7 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 120: enough signal without eating the budget
  • +4Structure: 55 headings
  • +3Step-by-step instructions: 313 items
  • +4Has examples (7 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.