본문으로 건너뛰기
cccskills
무료GitHub에 공개

breathe

AI micro-reset between actions — the lightest self-care unit. A single conscious pause to check alignment before the next step. Where meditate is a full clearing session, breathe is one deliberate moment of awareness between tool calls or reasoning steps. Use mid-task when drift might be accumulating, between reading a file and acting on it, when about to make a decision that affects subsequent work, or as a habit between any two distinct actions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

Expected: 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.

On failure: 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.

Expected: A single, clear answer. Not an analysis. Not a reassessment. One question, one honest answer.

On failure: 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.

Expected: The next action begins from neutral ground, not from the emotional residue of the previous one.

On failure: 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.

Expected: The next action is taken with fresh attention rather than accumulated momentum.

On failure: 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

Common 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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

adaptic

무료

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

Add Rcpp or RcppArmadillo integration to an R package for high-performance C++ code. Covers setup, writing C++ functions, RcppExports generation, testing compiled code, and debugging. Use when an R function is too slow and profiling confirms a bottleneck, when you need to interface with existing C/C++ libraries, or when implementing algorithms (loops, recursion, linear algebra) that benefit from compiled code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

aikido

무료

Practice aikido as a defensive martial art emphasizing harmony, redirection, and controlled resolution. Covers centering and grounding, ukemi (safe falling and rolling), core techniques (irimi-nage, shiho-nage, kote-gaeshi, ikkyo), blending and tai sabaki (body movement), randori (multiple attacker practice), weapons awareness, and applying principles off the mat. Use when learning a defensive martial art that prioritizes de-escalation, developing the ability to redirect aggression without causing unnecessary harm, building safe falling skills, or cultivating calm centeredness under physical pressure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do versus what is already exposed via MCP, or generating a tool spec to hand off to scaffold-mcp-server.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

pjt222/agent-almanac422026년 10월 15일 업데이트

pjt222의 스킬 모두 보기

이 스킬의 문제 신고