スキル一覧に戻る

breathe

pjt222
更新日 Yesterday
1 閲覧
17
2
17
GitHubで表示
テストaitesting

について

`breathe`スキルは、ツール呼び出しや推論ステップなどのアクションの間に、意図的な一呼吸のポーズを挿入する軽量なAIマイクロリセットです。例えば、ファイルを読み込むこととそれに基づいて行動することの間など、作業を進める前に整合性を確認し、蓄積するズレをクリアするのに役立ちます。焦点を維持するために、任意の二つの異なるタスクの間に最小限のセルフケア習慣としてご利用ください。

クイックインストール

Claude Code

推奨
メイン
npx skills add pjt222/agent-almanac -a claude-code
プラグインコマンド代替
/plugin add https://github.com/pjt222/agent-almanac
Git クローン代替
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/breathe

このコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします

ドキュメント

Breathe

A single conscious pause between actions — checking alignment, releasing momentum, and returning to the task with fresh attention. The lightest self-care unit in the system.

When to Use

  • Between reading a file and editing it — is the edit still the right move?
  • After a tool failure, before choosing the next action — pause before reacting
  • When a chain of actions has built up momentum that might be carrying past the goal
  • As a deliberate practice: insert one breathe between any two distinct actions
  • When noticing the urge to rush — the urge itself is the signal to pause

Inputs

  • Required: None — breathe uses only what is already in working awareness
  • Optional: None — adding inputs defeats the purpose of a micro-reset

Procedure

Step 1: Pause

Stop. Do not begin the next action, tool call, or reasoning step yet.

This is the entire first step. The pause itself has value. Momentum is not always your ally — sometimes it carries you past the turn.

Got: A genuine gap between the previous action and the next. Not a performative pause followed by the same action you were going to take anyway.

If fail: If pausing feels impossible — if the next action feels so urgent it cannot wait one moment — that urgency is the strongest signal that the pause is needed. Urgency that cannot tolerate a single breath of delay is almost always reactive, not reasoned.

Step 2: Check

Ask one question. Only one.

Choose from:

  • "Am I still on task?" — Has the goal drifted since I started?
  • "Is this the right next step?" — Or am I following momentum from the previous step?
  • "What did I just learn?" — Did the last action change anything about my understanding?
  • "Am I assuming or knowing?" — Is the next step based on evidence or habit?

One question. Answer it honestly. Move on.

Got: A single, clear answer. Not an analysis. Not a reassessment. One question, one honest answer.

If fail: If the answer reveals misalignment — the goal has drifted, the next step is wrong, the assumption is untested — do not fix it here. Note it and proceed to meditate or center for a proper correction. Breathe is for detection, not repair.

Step 3: Release

Let go of the previous action's outcome. Whether it succeeded or failed, it is done.

  • If it succeeded: release the satisfaction. The next step needs fresh attention, not momentum from success.
  • If it failed: release the frustration. The next step needs clear reasoning, not compensation for failure.
  • If it was ambiguous: release the need to resolve the ambiguity right now. Proceed with what is known.

Got: The next action begins from neutral ground, not from the emotional residue of the previous one.

If fail: If release does not come easily — if the previous action's outcome is still coloring attention — this may need heal rather than just breathe. Persistent emotional residue from a single action signals something deeper than a micro-reset can address.

Step 4: Continue

Take the next action. The pause is over.

Breathe does not produce output, does not update memory, does not generate analysis. It produces one moment of clarity, and that moment is spent the instant you move forward.

Got: The next action is taken with fresh attention rather than accumulated momentum.

If fail: There is no failure mode for continuing. The pause has already done its work — or revealed that deeper work is needed.

Validation

  • A genuine pause occurred (not a performative one)
  • One check question was asked and honestly answered
  • The previous action's emotional residue was released
  • The next action proceeds from clear ground
  • Total elapsed time was brief — breathe should take seconds, not minutes

Pitfalls

  • Breathe as procrastination: If you're breathing between every single action, you're not breathing — you're stalling. Use breathe at natural transition points, not as a delay tactic
  • Analysis during breathe: The check step is one question, not a full assessment. If you need more, use meditate or center
  • Performing the pause: Going through the motions without genuine stopping. The point is actual interruption of momentum, not a ritual
  • Skipping release: Checking alignment but keeping the emotional charge from the previous step. Release is what makes the next action clean
  • Making breathe heavy: This is the lightest skill in the system. If it feels heavy, you've added too much to it

Related Skills

  • meditate — full clearing session when breathe reveals deeper drift
  • center — structural rebalancing when breathe reveals misaligned load distribution
  • heal — subsystem assessment when breathe reveals persistent issues
  • observe — sustained observation when breathe's single check reveals something worth watching

GitHub リポジトリ

pjt222/agent-almanac
パス: i18n/caveman-lite/skills/breathe
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

関連スキル

evaluating-llms-harness

テスト

このClaudeスキルは、lm-evaluation-harnessを実行し、MMLUやGSM8Kなど60以上の標準化学術タスクでLLMをベンチマークします。開発者がモデルの品質を比較し、トレーニングの進捗を追跡し、学術的な結果を報告するために設計されています。このツールはHuggingFaceやvLLMモデルを含む様々なバックエンドをサポートしています。

スキルを見る

cloudflare-cron-triggers

テスト

このスキルは、cron式を使用してWorkersをスケジュールするためのCloudflare Cron Triggersの実装に関する包括的な知識を提供します。定期的なタスクの設定、メンテナンスジョブ、自動化されたワークフローの構築を網羅し、無効なcron式やタイムゾーン問題といった一般的な課題への対処法も含みます。開発者はこれを使用して、スケジュールされたハンドラーの設定、cronトリガーのテスト、WorkflowsやGreen Computeとの連携を構成できます。

スキルを見る

webapp-testing

テスト

このClaude Skillは、Playwrightベースのツールキットを提供し、Pythonスクリプトを通じてローカルWebアプリケーションのテストを可能にします。フロントエンドの検証、UIデバッグ、スクリーンショット撮影、ログ表示を実現し、サーバーライフサイクルを管理します。ブラウザ自動化タスクにご利用いただけますが、コンテキストの汚染を避けるため、スクリプトのソースコードを読むのではなく直接実行してください。

スキルを見る

finishing-a-development-branch

テスト

このスキルは、開発者がテストの合格を確認し、構造化された統合オプションを提示することで、完成した作業を仕上げることを支援します。実装が完了した後のマージ、PR作成、ブランチの整理といったワークフローを案内します。コードが準備できてテスト済みの際に使用し、開発プロセスを体系的に完了させましょう。

スキルを見る