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 accumulating drift before proceeding, such as between reading a file and acting on it. Use it as a minimal self-care habit between any two distinct tasks to maintain focus.
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
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
meditateorcenter - 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 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.
