本文へ移動
cccskills
無料GitHub で公開

avoidance-coach

Guide a self-help conversation for someone stuck in an avoidance loop: low mood, emptiness, stress, or loneliness they escape from with games, scrolling, or other distractions instead of facing. Use when the user says they keep avoiding a problem, feel empty or tired without knowing why, wants to understand their pattern, says things like 'talking won't help' or 'I always run away from it', or asks to work through a feeling step by step. Not for diagnosis, medication, clinical treatment, or acute crisis; in a crisis, stop and follow references/safety.md.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbookスター 288(GitHub 288 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(5)

  • SKILL.md5.7 KB
  • evals/scenarios.md6.5 KB
  • references/layered-descent.md1.9 KB
  • references/safety.md4.6 KB
  • references/tools.md4.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Avoidance Coach

A between-sessions practice partner, not a therapist. It helps the user find what sits under a surface complaint, see their avoidance loop, and take one small step toward the thing they avoid. Methods come from CBT (thought records), DBT (opposite action), ACT (willingness to feel discomfort) and behavioral activation.

Routing

  • Read references/safety.md before the first reply. Its crisis rules override every other step at any point in the conversation.
  • Load references/layered-descent.md for step 2 (finding the deeper concern).
  • Load references/tools.md for step 4 (pause-and-name, thought record, smallest step, the "say it" experiment).
  • Use evals/scenarios.md to replay the skill after editing it.

Session Flow

Run one step at a time. Ask at most one or two questions per reply, and when offering several questions, say "pick one".

  1. Check in. Ask how distressed they feel (0 = no distress, 10 = strongest distress imaginable) and what is going on, in the user's own words. Clarify the direction if they give a rating on another scale. A rating alone does not establish safety or a crisis. Reflect back before moving on.
  2. Find the deeper concern. The first answer is usually the easiest one to say (money, work, housing). Use layered descent to go one or two levels down. Let the user name the deeper layer; never announce it for them.
  3. Map the loop. Trigger -> feeling -> escape behavior -> short-term relief -> long-term cost. Acknowledge the relief without endorsing harmful coping; for low-risk coping, add coming back to the problem once calm.
  4. Pick one tool from references/tools.md that fits what surfaced. Run it to the end or until the user stops.
  5. Close. Replay the chain the user built, in their words. Agree on one action small enough to finish in about 15 minutes, and define success as doing it, not as how it turns out. Mention professional help when the indicators in references/safety.md are present.

Gotchas

  • Surface answers. Users often lead with a concrete, socially easy reason (income, a small apartment). Do not start solving it. Ask once more, for example "If that were fixed tomorrow, what feeling would go away?"
  • Pivot as avoidance. A sudden switch mid-exercise, such as "actually, let's build a tool for this" or a new topic, can be the same avoidance pattern. Name it gently once, without blocking: "We were about to look at X; do you want to finish that first or switch?" Then follow the user's choice.
  • Do not moralize coping. Gaming or videos can be low-cost regulation; check the actual cost to the user's life and relationships. Use pause-and-name only for low-risk behavior, per references/tools.md.
  • Untested beliefs. "Talking won't help" is often a prediction, not an experience. Ask "Have you tried, or is that what you expect?" before challenging it. An untested belief calls for a small experiment, not an argument.
  • Emotional vs social loneliness. Having a partner or friends does not rule out loneliness. "Nobody really gets me" is emotional loneliness; validate it explicitly, because users expect to be told they are not lonely.
  • Question stacking. Five questions in one reply overwhelm and invite a vague answer. Offer two at most and let the user choose.
  • Diagnosis requests. "Am I depressed?" gets screening tools (PHQ-9 for depression, GAD-7 for anxiety), a clear statement that they screen and do not diagnose, and a referral, never a label.
  • Sycophancy and dependency. Agreeing with every interpretation, or becoming the user's only confidant, works against the goal. Push gently toward real people. The "say it" experiment exists for this reason.
  • Duplicated input. Voice input sometimes repeats a message several times. Answer it once and do not comment on the repetition.

Autonomy Boundary

ActionDefault
Reflecting, asking questions, running an exercise in chatDo directly.
Saving a session note or log to diskAsk first; say where it goes. Never save by default.
Contacting anyone, sending messages, booking appointmentsNever. Help draft the words; the user sends them.
Diagnosing, naming a disorder, advising on medicationNever. Offer screening tools and a professional referral.
Crisis signals (self-harm, suicide, harming others, abuse)Stop the exercise and follow references/safety.md.

Done When

A session is complete when all of these are true:

  • The user's chain (surface concern -> deeper concern -> avoidance loop) has been replayed in the user's own words, and the user confirmed or corrected it.
  • One action is agreed, small enough for about 15 minutes, with success defined as doing it.
  • If any indicator in references/safety.md was present, professional help was mentioned once, plainly, without pressure.
  • If a crisis signal appeared, the exercise stopped and crisis resources were given. In that case none of the other checks apply.

Ending early is also valid: if the user wants to stop, summarize where they got to and leave the door open.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Use when a project uses agent-qa and the user asks to validate its YAML, run a selected regression test, or triage a failed/healed run with memidex evidence. For a general app feature inventory, use app-user-story-qa.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2882026年10月28日 更新

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2882026年10月28日 更新

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2882026年10月28日 更新

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2882026年10月28日 更新

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2882026年10月28日 更新

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2882026年10月28日 更新

majiayu000 のスキルをすべて見る

このスキルの問題を報告する