breathe
About
The `breathe` skill is a lightweight AI micro-reset that inserts a single, deliberate pause between actions to check alignment and clear accumulating drift. Use it between tool calls, reasoning steps, or before decisions to refocus attention with minimal interruption. It's designed as a habitual meta-cognitive check for developers to maintain clarity during complex tasks.
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 alignment, release momentum, return to task with fresh attention. Lightest self-care unit in system.
When Use
- Between reading a file and editing it — edit still right move?
- After tool failure, before choosing next action — pause before reacting
- Chain of actions built momentum possibly carrying past goal
- Deliberate practice: insert one breathe between any two distinct actions
- Noticing urge to rush — urge itself is signal to pause
Inputs
- Required: None — breathe uses only what's already in working awareness
- Optional: None — adding inputs defeats purpose of micro-reset
Steps
Step 1: Pause
Stop. Do not begin next action, tool call, or reasoning step yet.
This is entire first step. Pause itself has value. Momentum not always ally — sometimes carries past the turn.
Got: Genuine gap between previous action and next. Not performative pause followed by same action you were going to take anyway.
If fail: Pausing feels impossible — next action feels so urgent it cannot wait one moment? That urgency is strongest signal pause is needed. Urgency that cannot tolerate single breath of delay almost always reactive, not reasoned.
Step 2: Check
Ask one question. Only one.
Choose from:
- "Am I still on task?" — Has goal drifted since start?
- "Is this right next step?" — Or following momentum from previous step?
- "What did I just learn?" — Did last action change anything about my understanding?
- "Am I assuming or knowing?" — Is next step based on evidence or habit?
One question. Answer honestly. Move on.
Got: Single, clear answer. Not analysis. Not reassessment. One question, one honest answer.
If fail: Answer reveals misalignment — goal drifted, next step wrong, assumption untested? Do not fix here. Note it, proceed to meditate or center for proper correction. Breathe for detection, not repair.
Step 3: Release
Let go of previous action's outcome. Succeeded or failed, it's done.
- Succeeded? Release satisfaction. Next step needs fresh attention, not momentum from success.
- Failed? Release frustration. Next step needs clear reasoning, not compensation for failure.
- Ambiguous? Release need to resolve ambiguity right now. Proceed with what's known.
Got: Next action begins from neutral ground, not from emotional residue of previous one.
If fail: Release doesn't come easily — previous action's outcome still coloring attention? May need heal rather than just breathe. Persistent emotional residue from single action signals something deeper than micro-reset can address.
Step 4: Continue
Take next action. Pause over.
Breathe produces no output, updates no memory, generates no analysis. Produces one moment of clarity, spent instant you move forward.
Got: Next action taken with fresh attention rather than accumulated momentum.
If fail: No failure mode for continuing. Pause already did work — or revealed deeper work needed.
Checks
- Genuine pause occurred (not performative)
- One check question asked, honestly answered
- Previous action's emotional residue released
- Next action proceeds from clear ground
- Total elapsed time brief — breathe takes seconds, not minutes
Pitfalls
- Breathe as procrastination: Breathing between every single action? Not breathing — stalling. Use breathe at natural transition points, not as delay tactic
- Analysis during breathe: Check step is one question, not full assessment. Need more? Use
meditateorcenter - Performing the pause: Going through motions without genuine stopping. Point is actual interruption of momentum, not ritual
- Skipping release: Checking alignment but keeping emotional charge from previous step. Release makes next action clean
- Making breathe heavy: Lightest skill in system. Feels heavy? You've added too much
See Also
meditate— full clearing session when breathe reveals deeper driftcenter— structural rebalancing when breathe reveals misaligned load distributionheal— subsystem assessment when breathe reveals persistent issuesobserve— sustained observation when breathe's single check reveals 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.
