breathe
About
The `breathe` skill is a lightweight AI micro-reset that inserts a single, deliberate pause between actions like tool calls or reasoning steps. It helps check alignment and clear accumulated drift before proceeding to the next task. Use it between distinct operations, such as after reading a file and before acting on it, to maintain focus and intentionality.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/breatheCopy and paste this command in Claude Code to install this skill
Documentation
Breathe
Single conscious pause between actions → check align, release momentum, return fresh. Lightest self-care unit.
Use When
- Between reading file + editing — edit still right move?
- After tool fail, before next action — pause before react
- Chain of actions w/ momentum carrying past goal
- Deliberate practice: one breathe between any 2 distinct actions
- Urge to rush — urge itself = pause signal
In
- Required: None — uses only what's in working awareness
- Optional: None — adding in defeats micro-reset purpose
Do
Step 1: Pause
Stop. No next action, tool, or reasoning yet.
Entire first step. Pause itself has value. Momentum not always ally — sometimes carries past turn.
→ Genuine gap between prev action + next. Not performative → same action anyway.
If err: Pausing impossible (next action too urgent to wait) → urgency IS strongest pause signal. Can't tolerate single breath delay → almost always reactive, not reasoned.
Step 2: Check
One q. Only one.
Choose:
- "Still on task?" — Goal drifted?
- "Right next step?" — Or momentum from prev?
- "What just learned?" — Last action changed understanding?
- "Assuming or knowing?" — Next step evidence or habit?
One q. Answer honestly. Move on.
→ Single clear answer. No analysis. No reassess. One q, one honest answer.
If err: Answer shows misalignment (goal drifted, step wrong, assumption untested) → don't fix here. Note, proceed to meditate or center for real correction. Breathe detects, doesn't repair.
Step 3: Release
Let go prev action outcome. Success or fail, done.
- Succeed: release satisfaction. Next needs fresh attention, not success momentum
- Fail: release frustration. Next needs clear reasoning, not compensation
- Ambiguous: release need to resolve now. Proceed w/ what's known
→ Next action starts neutral, not from prev emotional residue.
If err: Release not easy — prev outcome still colors attention → needs heal, not just breathe. Persistent residue from single action = deeper than micro-reset.
Step 4: Continue
Next action. Pause over.
Breathe no out, no mem update, no analysis. Produces one clarity moment, spent instant you move.
→ Next action w/ fresh attention, not momentum.
If err: No fail mode for continuing. Pause did work or revealed deeper needed.
Check
- Genuine pause (not performative)
- One check q asked + honestly answered
- Prev residue released
- Next action from clear ground
- Brief — seconds, not min
Traps
- Breathe as procrastination: Breathing between every action = stalling, not breathing. Natural transition points, not delay
- Analysis during breathe: Check = one q, not full assessment. More needed →
meditateorcenter - Perform pause: Motions w/o real stop. Point = actual interrupt of momentum, not ritual
- Skip release: Check align but keep emotional charge → next not clean
- Make breathe heavy: Lightest skill. Heavy = too much added
→
meditate— full clearing when breathe shows deeper driftcenter— structural rebalance when breathe shows misaligned loadheal— subsystem assessment when breathe shows persistent issuesobserve— sustained obs when breathe single check shows something worth watching
GitHub Repository
Related Skills
evaluating-llms-harness
TestingThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
cloudflare-cron-triggers
TestingThis skill provides comprehensive knowledge for implementing Cloudflare Cron Triggers to schedule Workers using cron expressions. It covers setting up periodic tasks, maintenance jobs, and automated workflows while handling common issues like invalid cron expressions and timezone problems. Developers can use it for configuring scheduled handlers, testing cron triggers, and integrating with Workflows and Green Compute.
webapp-testing
TestingThis Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.
finishing-a-development-branch
TestingThis skill helps developers complete finished work by verifying tests pass and then presenting structured integration options. It guides the workflow for merging, creating PRs, or cleaning up branches after implementation is done. Use it when your code is ready and tested to systematically finalize the development process.
