breathe
关于
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.
快速安装
Claude Code
推荐npx 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/breathe在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
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 仓库
相关推荐技能
evaluating-llms-harness
测试该Skill通过60+个学术基准测试(如MMLU、GSM8K等)评估大语言模型质量,适用于模型对比、学术研究及训练进度追踪。它支持HuggingFace、vLLM和API接口,被EleutherAI等行业领先机构广泛采用。开发者可通过简单命令行快速对模型进行多任务批量评估。
cloudflare-cron-triggers
测试这个Claude Skill提供了关于Cloudflare Cron Triggers的完整知识库,用于通过cron表达式定时执行Workers。它支持配置周期性任务、维护作业和自动化工作流,并能处理常见的cron触发错误。开发者可以用它来设置定时任务、测试cron处理器,并集成Workflows和Green Compute功能。
webapp-testing
测试该Skill为开发者提供了基于Playwright的本地Web应用测试工具集,支持自动化测试前端功能、调试UI行为、捕获屏幕截图和查看浏览器日志。它包含管理服务器生命周期的辅助脚本,可直接作为黑盒工具运行而无需阅读源码。适用于需要快速验证本地Web应用界面和交互功能的开发场景。
finishing-a-development-branch
测试这个Skill用于开发分支完成后的集成决策,当代码实现完成且测试通过时,它会引导开发者选择合适的工作流。它首先验证测试状态,然后提供合并、创建PR或清理等结构化选项。核心价值在于确保代码质量的同时,标准化分支收尾流程。
