breathe
Über
Die `breathe`-Fähigkeit ist ein leichtgewichtiger KI-Mikro-Reset, der eine einzige, bewusste Pause zwischen Aktionen wie Werkzeugaufrufen oder Denkschritten einfügt. Sie hilft, die Ausrichtung zu überprüfen und vor dem Fortfahren angesammelte Abweichungen zu bereinigen, beispielsweise zwischen dem Lesen einer Datei und dem Handeln auf ihrer Grundlage. Nutzen Sie sie als minimale Selbstfürsorge-Routine zwischen zwei verschiedenen Aufgaben, um den Fokus zu bewahren.
Schnellinstallation
Claude Code
Empfohlennpx 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/breatheKopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren
Dokumentation
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
Verwandte Skills
evaluating-llms-harness
TestenDiese Claude Skill führt den lm-evaluation-harness aus, um LLMs über 60+ standardisierte akademische Aufgaben wie MMLU und GSM8K zu benchmarken. Sie wurde für Entwickler entwickelt, um Modellqualität zu vergleichen, Trainingsfortschritt zu verfolgen oder akademische Ergebnisse zu berichten. Das Tool unterstützt verschiedene Backends, einschließlich HuggingFace- und vLLM-Modelle.
cloudflare-cron-triggers
TestenDiese Fähigkeit bietet umfassendes Wissen zur Implementierung von Cloudflare Cron Triggers, um Workers mithilfe von Cron-Ausdrücken zu planen. Sie behandelt das Einrichten periodischer Aufgaben, Wartungsjobs und automatisierter Workflows, während häufige Probleme wie ungültige Cron-Ausdrücke und Zeitzonenprobleme behandelt werden. Entwickler können sie zum Konfigurieren geplanter Handler, zum Testen von Cron-Triggers und zur Integration mit Workflows und Green Compute verwenden.
webapp-testing
TestenDiese Claude Skill bietet ein Playwright-basiertes Toolkit zum Testen lokaler Webanwendungen durch Python-Skripte. Es ermöglicht Frontend-Verifizierung, UI-Debugging, Screenshot-Aufnahme und Log-Einblick bei gleichzeitiger Verwaltung von Server-Lebenszyklen. Nutzen Sie es für Browser-Automatisierungsaufgaben, führen Sie Skripte jedoch direkt aus, anstatt deren Quellcode zu lesen, um Kontextverschmutzung zu vermeiden.
finishing-a-development-branch
TestenDiese Fähigkeit unterstützt Entwickler dabei, abgeschlossene Arbeiten zu finalisieren, indem sie testet, ob Tests bestehen, und dann strukturierte Integrationsoptionen präsentiert. Sie leitet den Workflow für das Zusammenführen von Code, das Erstellen von PRs oder das Bereinigen von Branches nach Abschluss der Implementierung. Nutzen Sie sie, wenn Ihr Code bereit und getestet ist, um den Entwicklungsprozess systematisch abzuschließen.
