返回技能列表

breathe

pjt222
更新于 Yesterday
4 次查看
17
2
17
在 GitHub 上查看
测试aitesting

关于

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.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/breathe

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

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 meditate or center
  • 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 drift
  • center — structural rebalancing when breathe reveals misaligned load distribution
  • heal — subsystem assessment when breathe reveals persistent issues
  • observe — sustained observation when breathe's single check reveals something worth watching

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-lite/skills/breathe
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

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或清理等结构化选项。核心价值在于确保代码质量的同时,标准化分支收尾流程。

查看技能