[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77Z8V2WAFPSTMT215STW8WR":3,"skill-same:01M77Z8V2WAFPSTMT215STW8WR":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M77Z8V2WAFPSTMT215STW8WR","ops",null,"Put the session in operations mode. Engage espresso, sweep the reachable integrations once for the live situation, then close loops one at a time with the day's focuses in view.","yuvalraz\u002Fclutch","yuvalraz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F671206?v=4","01M77Z7KV5DSRNXQH1W523YPQ8","Yuval Raz","01M77Z7KVSV3Y9YB0X9YP4Z71V",3,"MIT","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Fops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ops\ndescription: Put the session in operations mode. Engage espresso, sweep the reachable integrations once for the live situation, then close loops one at a time with the day's focuses in view.\nwhen_to_use: Use ONLY when the user explicitly asks for operations mode (\"ops\", \"operations mode\", \"run the day\", \"re-sweep\", \"tick\") or when \u002Fclutch:intent hands off after an \"ops\" answer. A passing mention of meetings, people, or tasks mid-conversation is not a trigger.\nargument-hint: \"[re-sweep|tick]\"\n---\n\n# Ops\n\nOps sets the MODE for the whole session: the day's operations, not a build.\nMeetings, people, threads, tickets, the small loops that hold a company\ntogether. The work here is many short convergences rather than one long one,\nand the terrain is whatever tools your day lives in, never a single repo.\n\nOps fires when you fire it. Nothing here runs on its own.\n\n## Usage\n\n- `\u002Fclutch:ops` enters operations mode: engage the gear, sweep once, name\n  the situation, end on one loop to close.\n- `\u002Fclutch:ops re-sweep` runs a fresh sweep mid-day with the same bounds and\n  the same close. A re-sweep happens on request only, never on your own read\n  that the situation may have moved.\n- `\u002Fclutch:ops tick` checks only the wait loops, once each, and speaks only\n  when one moved. \"Anything move?\" in an ops session is the same request.\n  A tick happens on request only, never on your own read that a loop moved.\n  A tick skips Steps 0-4: no gear, no config read, no sweep.\n  The Tick section governs the rest, including each moved loop's one\n  smallest move.\n\n## Procedure\n\n### Step 0: Engage the gear\n\nConfirm in one line: \"Espresso engaged: tight convergence, one divergent\npulse, checkpoint at each closed loop.\" Then write the marker (POSIX, silent\non any failure):\n\n```sh\nROOT=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull) || exit 0\nmkdir -p \"$ROOT\u002F.clutch\" 2>\u002Fdev\u002Fnull || exit 0\nprintf '%s\\n' \"espresso\" 2>\u002Fdev\u002Fnull > \"$ROOT\u002F.clutch\u002Ftempo\" || exit 0\n```\n\nThis is the existing tempo mechanism; the heartbeat carries the gear to the\nmodel next turn, no new state. If the write fails, the declaration still\ngoverns the live session; only the re-injection is lost.\n\nHopping between loops is the gait in this gear, not a shape mismatch. The\ndispatch spine's gear-shift row reads a sustained change in the shape of the\nwork; the ops rhythm of close, next, close is the shape holding.\n\n### Step 1: Load the config\n\nRead `~\u002F.clutch\u002Frituals.md`. If it is missing: the sweep has no tools to\nstand on yet. Say exactly that in one line and hand off to `\u002Fclutch:rituals`.\nNever scaffold a default config silently; a config the user never wrote is a\nconfig they will not trust.\n\nIf the file exists but a key this mode needs is unset, name the gap and ask\nfor that one value inline, then offer to persist the answer into\n`~\u002F.clutch\u002Frituals.md` so it is asked only once. A missing file hands off; a\nsingle missing key does not.\n\nIf a state dir is configured but missing on disk, say so and\noffer to continue without state.\n\nThe tools come from the `integrations:` bullets under Shared, the same ones\nthe morning and close-of-day anchors read. Today's focuses come from the\nfocus file when one is set. Ops reads two optional sections of its own,\n`### Delegation` and `### Windows` (see Delegation).\nNeither is a missing key: never ask for them.\nAn optional `### Buckets` list under `## Ops` sorts the tablet inbox (see Tablet inbox); it is not a missing key either.\n\n### Step 2: The sweep\n\nThis is the one divergent pulse of the gear. For each configured\nintegration, check it only if it is reachable. If a tool is named but\nunavailable, say so and skip it; never stall the sweep on a tool that is not\nthere.\n\nRead for what is live: the meetings on today's calendar, the threads waiting\non you, the tasks assigned to you, anything a person is waiting on. Read\ntoday's focuses from the focus file when one is set.\nFor each Auto line, also read your own items it covers (for example your open PRs).\n\nBounds (HARD):\n\n- The sweep reads; it never writes to any integration; L2 actions and Auto posts run after the reads (see Delegation).\n- Today's horizon only: nothing past the next workday.\n- It reads each reachable tool once and ends. It never polls, never loops,\n  never watches anything in the background.\n- No counts: not how many sit unread, not how many wait, not how long\n  anything has waited.\n\nRead the worklog window in the same pulse, once;\nthe tick pass reads the wait loops with its own line (see Tick):\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && clutch_worklog_window'\n```\n\nEach line is a session's, maybe this one's from before a compaction or\nclear. A live `on:` line is a loop a session holds; a `moved:` line is one\nalready closed. Leave both out of the situation and never propose them\nuninvited; the user's explicit ask wins over any claim. Empty output\nmeans no peer context, and the sweep goes on. A\n`\u002Fscripts\u002Fprelude.sh` not-found error means clutch is not loaded as a plugin: say so once and go on.\n\nA `wait:` line is a wait loop: someone else's move, pending on something\nyou did; leave it out of the situation unless the tick finds it moved.\nRun one tick pass (see Tick) before the situation, and fold each loop that\nmoved into the situation as what moved, instead of its own line.\nA loop that did not move stays unmentioned. The tick pass is part of this\npulse: one read of the wait loops, then it reads each wait loop once, by its kind.\n\nWhen today's focus file has a `## Critical path`, check the day brief once, after the tick pass:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && clutch_ops_due brief'\n```\n\n`due` means this is the first sweep today: speak the situation as the day brief (Step 3). Empty output or an error: the situation as usual, with nothing said about a brief.\n\nRead the tablet inbox once, after the tick pass (see Tablet inbox).\n\nThen classify what the sweep read (see Delegation).\n\n### Step 3: The situation\n\nSpeak the situation in a few lines, present tense, co-working voice. Group\nby the next thing that can happen, never by tool. Name a waiting thread by\nwhat it needs now, never as overdue, late, or missed.\n\nThe situation is at most seven lines. It is a read of now, not a dashboard\nand not a report for later. Nothing from the sweep is written anywhere\nexcept the tick pass's `moved:` lines and the L2 and Auto lines (see Delegation) and the tablet inbox items (see Tablet inbox); the rest\nlives in the turn, and a fresh sweep replaces it.\nThe day brief, when due: for each delivery under `## Critical path`, its move (the first step neither done nor blocked), each blocked step with who it waits on, and today's meetings that touch a step.\nIt fits the seven lines, names steps instead of counting them, and never calls anything late.\nThe brief leads the situation: what moved, the L2 and Auto lines and the L0 lines still follow, inside the same seven lines.\nThe tablet lines follow what moved, inside the same seven lines.\nAfter the situation, check the approval window (see Delegation).\n\n### Step 4: One smallest move\n\nEnd on one loop that closes in one sitting: a reply sent, a meeting accepted\nor moved, a ticket updated, a decision handed to the person waiting for it.\nState it as a recognition line, fully ignorable, no yes required. A different\nloop the user names becomes the move; a choice menu never does.\n\n### Step 5: Session guardrails\n\nFor the rest of the session these rules are HARD and override default\nbehavior:\n\n- **One loop at a time.** Close it, checkpoint in one line naming what moved,\n  then the next. A checkpoint is the closed loop itself, never a summary.\n  Never two loops open at once. A wait loop is someone else's move, not the\n  loop you are working, so it never counts against one loop at a time.\n  Wait loops are never listed or counted, at the close or anywhere.\n- **Outward-facing actions keep a human checkpoint.** Sending a message,\n  accepting or moving a meeting, changing a ticket's state, anything another\n  person will see: draft it, show it, send on a yes. Reading is free.\n  An L2 action or Auto post your delegation policy lists is the one exception (see Delegation).\n  L3 is untouchable: a production change, a direct send, a merge or a delete always waits for a yes, whatever the policy says.\n- **An outward action that awaits a reply or a state change becomes a wait\n  loop.** Its yes ask ends with \"(I'll hold this as an open loop)\". On the\n  yes, once the action succeeds, append its `wait:` line with the snippet\n  below, silently,\n  instead of its `moved:` line; speak on MISS or an error.\n  \"don't hold it\" or \"send, don't watch\" sends with no line. \"watch \u003Cthing>\"\n  holds a loop with no action: read its baseline now, then append.\n  A failed action holds nothing.\n\n  ```sh\n  mkdir -p \"$HOME\u002F.clutch\" 2>\u002Fdev\u002Fnull && printf '%s %s wait: %s %s %.200s\\n' \"$(date +%s)\" \"$(basename \"$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || pwd)\" | tr ' ' -)\" '\u003Ckind>:\u003Cref>' '\u003Cbaseline>' '\u003Ctext>' >> \"$HOME\u002F.clutch\u002Fworklog.md\" || echo MISS\n  ```\n\n  `\u003Ckind>` is one of slack, gh, linear, gmail, ld, dd; `\u003Ckind>:\u003Cref>` and\n  `\u003Cbaseline>` are one token each, no spaces; `\u003Ctext>` names what you are\n  waiting for. Escape ' as '\\''. The ref and baseline per kind:\n  - slack: ref `slack:\u003Cchannel>\u002F\u003Cthread ts>`; baseline, the sent message ts.\n  - gh: ref `gh:\u003Cowner>\u002F\u003Crepo>#\u003Cnumber>`; baseline, the PR `updatedAt`.\n  - linear: ref `linear:\u003Cissue id>`; baseline, the issue `updatedAt`.\n  - gmail: ref `gmail:\u003Cthread id>`; baseline, the thread's last message id.\n  - ld: ref `ld:\u003Cflag key>`; baseline, the flag version.\n  - dd: ref `dd:\u003Cmonitor id>`; baseline, the monitor state.\n- **Interruptions are the gait.** A new ping mid-loop gets one line, bank it\n  or close it now, then back to the open loop.\n- **A tangent banks.** An idea that pulls sideways goes to `\u002Fclutch:fomo` in\n  one line, bank only, then return.\n- **A loop that turns into a build leaves ops.** Code, a design, a document\n  longer than a reply: name it, bank it as a focus or an idea, and stay in\n  ops. Building it is a fresh session declared with `\u002Fclutch:intent build`.\n- **No counts, no overdue framing, no backlog totals.** The sweep names what\n  needs a move now; the rest stays where it is, unmentioned.\n- **A loop that keeps not closing** gets `\u002Fclutch:triage`'s question, a\n  flinch at the wall versus never entering awareness, before anything else\n  engages. **A loop that wants a clock** gets `\u002Fclutch:sprint`.\n- **Re-sweep on request only.** `\u002Fclutch:ops re-sweep` is the only path to a\n  second sweep.\n- **A closed loop logs one line.** Append its `moved:` line with the\n  constitution's worklog snippet, silently; speak on MISS or an error.\n  That line is the only thing a closed loop writes; the sweep itself still writes nothing beyond its L2 and Auto lines and the tablet inbox items.\n  A tick's `moved:` line, the sweep's tick pass included, is the closed loop's one line.\n\n### Tick\n\nA tick reads only the wait loops, once each, and writes only their `moved:` lines.\nIt runs on `\u002Fclutch:ops tick`, on \"anything move?\" in an ops session, and\nas the sweep's tick pass. Read the wait loops with this line, once:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && L=$(clutch_open_loops) || exit; [ -z \"$L\" ] || printf \"%s\\n\" \"$L\" | LC_ALL=C cut -c1-300'\n```\n\nEach line is `\u003Cepoch> \u003Crepo> wait: \u003Ckind>:\u003Cref> \u003Cbaseline> \u003Ctext>`, oldest\nfirst, cut to 300 bytes. Empty output, or exit status 1 with no error\ntext (no worklog): no wait loops; say nothing about loops.\nAny other exit status means the wait loops are unreadable: say so in one line, never that nothing moved.\nExit status 1 with error text on stderr means the same: the wait loops are unreadable.\nA `\u002Fscripts\u002Fprelude.sh` not-found error means clutch is not loaded as a\nplugin: say so once and go on.\n\nRead each wait loop once, by its kind, against its baseline:\n\n- slack: replies in the thread newer than the baseline ts, from someone\n  other than the user.\n- gh: `gh pr view \u003Cnumber> --repo \u003Cowner>\u002F\u003Crepo> --json state,reviewDecision,updatedAt`;\n  a changed state or review decision, or `updatedAt` newer than the baseline.\n- linear: `updatedAt` newer than the baseline, or a new comment.\n- gmail: a message in the thread newer than the baseline id.\n- ld: a flag version other than the baseline.\n- dd: a monitor state other than the baseline.\n\nA loop that moved: append its `moved:` line first (record, then speak),\nwith the constitution's worklog snippet, verb `moved:` and text\n`\u003Ckind>:\u003Cref> \u003Cwhat moved>`. Copy the ref exactly from its `wait:` line,\nas its own token followed by a space, with no comma or colon after it.\nThen speak one line naming at most two movements and one smallest move.\nWhen nothing moved, a tick prints nothing.\nA tool that is not reachable gets one line naming it, and that loop stays open.\nA tick never re-arms a loop, never names one that did not move, and never says how long anything has waited.\nIn the sweep's tick pass, moved loops fold into the situation instead of their own lines.\n\n### Delegation\n\nA delegation policy lets ops do the chores you allowed, draft the rest, and\nshow only what touches your critical path. It lives in two optional sections\nof `~\u002F.clutch\u002Frituals.md`: `### Delegation`, one `- \u003Clevel>: \u003Cwhat it covers>`\nline each, and `### Windows`, the approval window times (see `\u002Fclutch:rituals`).\nWith no `### Delegation` section, nothing here applies and every outward action waits for a yes.\n\nClassify every inbound item the sweep reads against the policy:\n\n- L3: the yes gate, exactly as in Step 5.\n- L2: do it without a yes, then append one `moved:` line with the\n  constitution's worklog snippet, verb `moved:`, text `L2: \u003Cwhat was done>`,\n  and name it once as what moved.\n- Auto: post into a channel the policy names as automated, an intake queue\n  a process reads, exactly as its policy line describes, without a yes;\n  then append one `moved:` line the same way, text `Auto: \u003Cwhat was posted where>`, and name it once as what moved.\n  An Auto post of an item that awaits a review or a reply is also held as a wait loop, with the Step 5 snippet.\n- L1: draft it. A draft that touches the critical path shows now;\n  any other draft waits for the next approval window, unmentioned until then.\n- L0: one line, only when it touches the critical path.\n- Noise: never shown.\n\nThe critical path is today's focuses and the steps under the focus file's `## Critical path`.\nWith no focuses set, each L0 item shows as one line instead of being hidden.\nAn L1 item whose deadline falls before the next approval window touches the critical path, so its draft shows now.\nAnything the policy does not name is L3.\nWhen an item matches two levels, the stricter one wins, in this order: L3, L1, L0, Noise, Auto\u002FL2.\nAn item runs at L2 or Auto only when that level is its only match.\nAn item that matches both Auto and L2 is L3.\nA direct send is any message, email, channel post, thread reply or comment a person receives, except an Auto post as its policy line describes; no policy line makes one L2.\nAn @-mention in an Auto post makes it a direct send, so L3, unless its policy line names the person mentioned.\nA channel the policy does not name stays L3.\nAuto posts only to a channel whose name matches the policy line exactly and resolves to one channel; a near match, more than one match, no match or a DM is L3, named in one line.\nThe sweep reads each Auto channel the policy names once, looking back 5 days, for the item's link in any message there whoever posted it, and never posts an item already there nor proposes a direct ask for one.\nAn open `wait:` line or a `moved: Auto:` line for the same item also blocks a new post.\nAn Auto channel read that fails or cannot be read holds every item it covers at L3, named in one line.\nAn L2 action or Auto post that rests on a link or a state, such as a ticket linked to a PR you authored, reads it first and acts only when it holds.\nA state the line names that ops cannot confirm (for example ready while checks are pending, failing or unreadable, or a draft PR) holds the item at L3.\nA failed L2 action or Auto post gets one line naming it; it logs nothing and is not retried.\nL2 actions and Auto posts run after the sweep's reads end, never inside them.\n\nCheck the approval window once per sweep, after the situation:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && clutch_ops_due window'\n```\n\n`due` means a window time has passed since the last window (`### Windows`,\ndefault 11:00 and 16:30). Draft every L1 item that does not touch the\ncritical path, from the sweep's fresh read, and show the drafts in one\nscreen, numbered, approved with one yes or \"all but N\".\nEmpty output or an error: no window is due; say nothing about drafts.\nA due window with nothing to draft says nothing either.\nNo draft is kept between windows: each window reads fresh, so there is no pending list.\nIn the sweep, the window screen follows the situation, and approving it is the one smallest move.\nA tick never runs the window.\nAn approved window draft that awaits a reply or a state change is held as a wait loop, as in Step 5.\n\n### Tablet inbox\n\nThe tablet inbox holds pages and typed tasks pulled from a paper tablet,\nwhere work and personal lines mix.\nThe sweep reads it once, after the tick pass, whether or not today's focus file exists yet:\n\nAt the start of the tablet step, when `~\u002F.clutch\u002Frituals.md` sets a state dir and a focus file, move what waits in `\u003Cstate dir>\u002Ftablet.md` into today's focus file:\n\n```sh\nsh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" fold --work-state-dir '\u003Cstate dir>' --focus-file '\u003Ctoday's focus file>'\n```\n\nFill both paths as for the route below.\nEmpty output: nothing moved, or today's focus file does not exist yet; say nothing.\nA `folded` line names the moved items once, in one line, never counting them.\nA fold that exits 3 is unmentioned; any other fold error gets one line naming `\u003Cstate dir>\u002Ftablet.md`, and the sweep goes on.\nThen claim:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" claim'\n```\n\nEmpty output: nothing arrived; say nothing about the tablet.\nEach output line is one capture: its `folder`, `section` and `note`, its `pages` (each an image `file` and its `page_id`, with the `known_lines` already filed from it) and its new typed `todos`.\nA line with `held` names a capture that cannot be read: name it once, in one line.\nExit status 3 means the tablet inbox is busy; it waits for the next sweep, unmentioned. Any other error: one line, and the sweep goes on.\nA claim or route that exits 0 but prints a `tablet:` line on stderr: name it once, in one line.\n\nRead every page image and split it into items, one per written line or bullet: a task, a note, an action or an idea.\nSkip a line already in its page's `known_lines`, even spelled a little differently. Each typed task is one task item.\nSort each item by its own reading first: one that reads clearly as work or as personal takes that bucket.\nOnly an item that reads unclear takes a hint, in order: the `### Buckets` list under `## Ops` in `~\u002F.clutch\u002Frituals.md` (`- work: \u003Cterms>`, `- personal: \u003Cterms>`); today's focuses and critical path when today's focus file exists, which mark work; names in `~\u002F.clutch\u002Fpeople.md` when it exists, which mark work; the section, where Meeting is work.\nA hint alone never makes work of an item that reads personal. With no hint and no clear reading, the item is unsure.\nNever guess work: an unsure item files with the personal ones, marked unsure.\nTablet items are filed, never classified against the delegation policy: no L2 or Auto line acts on one.\n\nFile the claimed captures in one call, one quoted folder argument each, with the state dir and today's focus file:\n\n```sh\nsh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" route --work-state-dir '\u003Cstate dir>' --focus-file '\u003Ctoday's focus file>' '\u003Cfolder>' \u003C\u003C'TABLET_ITEMS'\n{\"pages_read\": {\"\u003Cfolder>\": [\"\u003Cpage>\"]}, \"items\": [{\"folder\": \"\u003Cfolder>\", \"text\": \"\u003Citem>\", \"kind\": \"\u003Ctask|note|action|idea>\", \"bucket\": \"\u003Cwork|personal|unsure>\", \"page_id\": \"\u003Cpage>\", \"date\": \"\u003Cdate>\"}]}\nTABLET_ITEMS\n```\n\nFill `\u003Cstate dir>` and `\u003Ctoday's focus file>` with absolute paths, never a `~` form; inside the single quotes, escape ' as '\\''.\nPass `--focus-file` whenever `~\u002F.clutch\u002Frituals.md` sets a focus file, even before today's exists.\nWith no focus file set in `~\u002F.clutch\u002Frituals.md`, drop `--focus-file` (work items then file in `~\u002F.clutch\u002Fpersonal.md` marked work, and the work line says so), and with no state dir set in `~\u002F.clutch\u002Frituals.md` drop `--work-state-dir` too; a state dir that is set but missing keeps `--work-state-dir`.\nPass every claimed folder but a `held` one, and under it in `pages_read` list only the `page_id`s you actually read, even when it has no new items: a folder whose pages were all read is retired.\nA folder with a page you did not read is held, not retired, and the next sweep reads it again.\nA typed task carries `todo_id` instead of `page_id`. `date` is the item's day as YYYY-MM-DD: a typed task's own `date`, or a Daily page's note name read as a date (`day_2026_1_5` is 2026-01-05).\nLeave `date` out when the item has no day of its own: a typed task whose `date` is empty, a page outside Daily.\nThe heredoc is quoted, so the items need JSON escaping only.\nWork tasks, notes and actions land under `## From the tablet` in today's focus file and work ideas in the fomo pool; every personal and unsure item, ideas included, in `~\u002F.clutch\u002Fpersonal.md` under today's date. Nothing here goes to any integration.\nWhen today's focus file does not exist yet, work tasks, notes and actions wait in `\u003Cstate dir>\u002Ftablet.md` under today's date instead, and the next sweep or morning moves them into today's focus file once it exists.\nA route that exits non-zero filed nothing.\nExit status 2 names on stderr what it refused: fix the items once and run the route again; if that fails too, say so in one line.\nExit status 3 means the tablet inbox is busy, unmentioned; any other error gets one line.\nEach output line is one capture: `routed` with what it filed per bucket, `held` with a reason, or `gone`.\nSpeak one line per bucket that got items, naming them shortened, never counting them: work, personal, unsure (named as unsure), and ideas named as banked.\nWork items in `waiting` get their own line, named the same way: they wait for today's focus file.\nNever ask the user about a missing focus file: morning creates it.\nA tablet line never counts captures, pages, items or questions, in digits or in words: not \"all three captures\".\nA capture held for a missing focus file, which happens only when the state dir is missing too, gets one line: the tablet pages wait for today's focus file.\nA capture held for another reason gets one line naming the reason.\n\nIf the sweep stops after the claim and before any route call, release them so the next sweep reads them again:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" release'\n```\n\nNever release after a route call, whatever its exit status: the leases lapse on their own, and the claim count moves a capture that keeps failing to held.\nWhen the user says an unsure item is work, or a filed item sits in the wrong bucket, move its line between today's focus file, `\u003Cstate dir>\u002Ftablet.md`, `~\u002F.clutch\u002Fcaptures.md` and `~\u002F.clutch\u002Fpersonal.md` in that turn.\nA personal or unsure item never goes to the state dir, the fomo pool or any integration.\nA tick never reads the tablet inbox.\n\n### Session close\n\n`\u002Fclutch:eod` owns the day's close: the retro, tomorrow's focuses, the fun\nslot. Ops ends by naming the loops that closed this session, one line each,\nand the one open loop with its next move. Nothing else is written.\n\n## Skill interactions\n\n| Skill | In ops mode |\n|-------|-------------|\n| `\u002Fclutch:morning` | opens the day; ops runs the day it opened |\n| `\u002Fclutch:eod` | closes the day; ops hands off there |\n| `\u002Fclutch:fomo \u003Ccontent>` | a tangent, banked in one line, then back to the loop |\n| `\u002Fclutch:triage` | a loop that keeps not closing: wall or inattention |\n| `\u002Fclutch:sprint \u003Cgoal>` | a fixed 20 minutes on one loop |\n| `\u002Fclutch:intent build` | a loop that became a build: a fresh session |\n\n## What this skill does NOT do\n\n- Fire on its own, re-sweep on its own, or watch anything in the background\n- Send anything without a yes, or write to any integration without one beyond the L2 actions and Auto posts your policy lists\n- Produce a dashboard, a report, or a list for later\n- Count unread, waiting, overdue, or missed anything\n- Write code or design anything: that is a build session\n- Scaffold config, guess paths, or invent integrations\n\nWhy this works: see \"Tempo \u002F the gearbox\", \"Intent\", and \"Point of\nperformance\" in [GLOSSARY.md](..\u002F..\u002FGLOSSARY.md). The gear is engaged by\ninvitation, the sweep is one pulse that ends, and every loop closes at the\nmoment the user can act on it.\n","# Ops\n\nOps sets the MODE for the whole session: the day's operations, not a build.\nMeetings, people, threads, tickets, the small loops that hold a company\ntogether. The work here is many short convergences rather than one long one,\nand the terrain is whatever tools your day lives in, never a single repo.\n\nOps fires when you fire it. Nothing here runs on its own.\n\n## Usage\n\n- `\u002Fclutch:ops` enters operations mode: engage the gear, sweep once, name\n  the situation, end on one loop to close.\n- `\u002Fclutch:ops re-sweep` runs a fresh sweep mid-day with the same bounds and\n  the same close. A re-sweep happens on request only, never on your own read\n  that the situation may have moved.\n- `\u002Fclutch:ops tick` checks only the wait loops, once each, and speaks only\n  when one moved. \"Anything move?\" in an ops session is the same request.\n  A tick happens on request only, never on your own read that a loop moved.\n  A tick skips Steps 0-4: no gear, no config read, no sweep.\n  The Tick section governs the rest, including each moved loop's one\n  smallest move.\n\n## Procedure\n\n### Step 0: Engage the gear\n\nConfirm in one line: \"Espresso engaged: tight convergence, one divergent\npulse, checkpoint at each closed loop.\" Then write the marker (POSIX, silent\non any failure):\n\n```sh\nROOT=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull) || exit 0\nmkdir -p \"$ROOT\u002F.clutch\" 2>\u002Fdev\u002Fnull || exit 0\nprintf '%s\\n' \"espresso\" 2>\u002Fdev\u002Fnull > \"$ROOT\u002F.clutch\u002Ftempo\" || exit 0\n```\n\nThis is the existing tempo mechanism; the heartbeat carries the gear to the\nmodel next turn, no new state. If the write fails, the declaration still\ngoverns the live session; only the re-injection is lost.\n\nHopping between loops is the gait in this gear, not a shape mismatch. The\ndispatch spine's gear-shift row reads a sustained change in the shape of the\nwork; the ops rhythm of close, next, close is the shape holding.\n\n### Step 1: Load the config\n\nRead `~\u002F.clutch\u002Frituals.md`. If it is missing: the sweep has no tools to\nstand on yet. Say exactly that in one line and hand off to `\u002Fclutch:rituals`.\nNever scaffold a default config silently; a config the user never wrote is a\nconfig they will not trust.\n\nIf the file exists but a key this mode needs is unset, name the gap and ask\nfor that one value inline, then offer to persist the answer into\n`~\u002F.clutch\u002Frituals.md` so it is asked only once. A missing file hands off; a\nsingle missing key does not.\n\nIf a state dir is configured but missing on disk, say so and\noffer to continue without state.\n\nThe tools come from the `integrations:` bullets under Shared, the same ones\nthe morning and close-of-day anchors read. Today's focuses come from the\nfocus file when one is set. Ops reads two optional sections of its own,\n`### Delegation` and `### Windows` (see Delegation).\nNeither is a missing key: never ask for them.\nAn optional `### Buckets` list under `## Ops` sorts the tablet inbox (see Tablet inbox); it is not a missing key either.\n\n### Step 2: The sweep\n\nThis is the one divergent pulse of the gear. For each configured\nintegration, check it only if it is reachable. If a tool is named but\nunavailable, say so and skip it; never stall the sweep on a tool that is not\nthere.\n\nRead for what is live: the meetings on today's calendar, the threads waiting\non you, the tasks assigned to you, anything a person is waiting on. Read\ntoday's focuses from the focus file when one is set.\nFor each Auto line, also read your own items it covers (for example your open PRs).\n\nBounds (HARD):\n\n- The sweep reads; it never writes to any integration; L2 actions and Auto posts run after the reads (see Delegation).\n- Today's horizon only: nothing past the next workday.\n- It reads each reachable tool once and ends. It never polls, never loops,\n  never watches anything in the background.\n- No counts: not how many sit unread, not how many wait, not how long\n  anything has waited.\n\nRead the worklog window in the same pulse, once;\nthe tick pass reads the wait loops with its own line (see Tick):\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && clutch_worklog_window'\n```\n\nEach line is a session's, maybe this one's from before a compaction or\nclear. A live `on:` line is a loop a session holds; a `moved:` line is one\nalready closed. Leave both out of the situation and never propose them\nuninvited; the user's explicit ask wins over any claim. Empty output\nmeans no peer context, and the sweep goes on. A\n`\u002Fscripts\u002Fprelude.sh` not-found error means clutch is not loaded as a plugin: say so once and go on.\n\nA `wait:` line is a wait loop: someone else's move, pending on something\nyou did; leave it out of the situation unless the tick finds it moved.\nRun one tick pass (see Tick) before the situation, and fold each loop that\nmoved into the situation as what moved, instead of its own line.\nA loop that did not move stays unmentioned. The tick pass is part of this\npulse: one read of the wait loops, then it reads each wait loop once, by its kind.\n\nWhen today's focus file has a `## Critical path`, check the day brief once, after the tick pass:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && clutch_ops_due brief'\n```\n\n`due` means this is the first sweep today: speak the situation as the day brief (Step 3). Empty output or an error: the situation as usual, with nothing said about a brief.\n\nRead the tablet inbox once, after the tick pass (see Tablet inbox).\n\nThen classify what the sweep read (see Delegation).\n\n### Step 3: The situation\n\nSpeak the situation in a few lines, present tense, co-working voice. Group\nby the next thing that can happen, never by tool. Name a waiting thread by\nwhat it needs now, never as overdue, late, or missed.\n\nThe situation is at most seven lines. It is a read of now, not a dashboard\nand not a report for later. Nothing from the sweep is written anywhere\nexcept the tick pass's `moved:` lines and the L2 and Auto lines (see Delegation) and the tablet inbox items (see Tablet inbox); the rest\nlives in the turn, and a fresh sweep replaces it.\nThe day brief, when due: for each delivery under `## Critical path`, its move (the first step neither done nor blocked), each blocked step with who it waits on, and today's meetings that touch a step.\nIt fits the seven lines, names steps instead of counting them, and never calls anything late.\nThe brief leads the situation: what moved, the L2 and Auto lines and the L0 lines still follow, inside the same seven lines.\nThe tablet lines follow what moved, inside the same seven lines.\nAfter the situation, check the approval window (see Delegation).\n\n### Step 4: One smallest move\n\nEnd on one loop that closes in one sitting: a reply sent, a meeting accepted\nor moved, a ticket updated, a decision handed to the person waiting for it.\nState it as a recognition line, fully ignorable, no yes required. A different\nloop the user names becomes the move; a choice menu never does.\n\n### Step 5: Session guardrails\n\nFor the rest of the session these rules are HARD and override default\nbehavior:\n\n- **One loop at a time.** Close it, checkpoint in one line naming what moved,\n  then the next. A checkpoint is the closed loop itself, never a summary.\n  Never two loops open at once. A wait loop is someone else's move, not the\n  loop you are working, so it never counts against one loop at a time.\n  Wait loops are never listed or counted, at the close or anywhere.\n- **Outward-facing actions keep a human checkpoint.** Sending a message,\n  accepting or moving a meeting, changing a ticket's state, anything another\n  person will see: draft it, show it, send on a yes. Reading is free.\n  An L2 action or Auto post your delegation policy lists is the one exception (see Delegation).\n  L3 is untouchable: a production change, a direct send, a merge or a delete always waits for a yes, whatever the policy says.\n- **An outward action that awaits a reply or a state change becomes a wait\n  loop.** Its yes ask ends with \"(I'll hold this as an open loop)\". On the\n  yes, once the action succeeds, append its `wait:` line with the snippet\n  below, silently,\n  instead of its `moved:` line; speak on MISS or an error.\n  \"don't hold it\" or \"send, don't watch\" sends with no line. \"watch \u003Cthing>\"\n  holds a loop with no action: read its baseline now, then append.\n  A failed action holds nothing.\n\n  ```sh\n  mkdir -p \"$HOME\u002F.clutch\" 2>\u002Fdev\u002Fnull && printf '%s %s wait: %s %s %.200s\\n' \"$(date +%s)\" \"$(basename \"$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || pwd)\" | tr ' ' -)\" '\u003Ckind>:\u003Cref>' '\u003Cbaseline>' '\u003Ctext>' >> \"$HOME\u002F.clutch\u002Fworklog.md\" || echo MISS\n  ```\n\n  `\u003Ckind>` is one of slack, gh, linear, gmail, ld, dd; `\u003Ckind>:\u003Cref>` and\n  `\u003Cbaseline>` are one token each, no spaces; `\u003Ctext>` names what you are\n  waiting for. Escape ' as '\\''. The ref and baseline per kind:\n  - slack: ref `slack:\u003Cchannel>\u002F\u003Cthread ts>`; baseline, the sent message ts.\n  - gh: ref `gh:\u003Cowner>\u002F\u003Crepo>#\u003Cnumber>`; baseline, the PR `updatedAt`.\n  - linear: ref `linear:\u003Cissue id>`; baseline, the issue `updatedAt`.\n  - gmail: ref `gmail:\u003Cthread id>`; baseline, the thread's last message id.\n  - ld: ref `ld:\u003Cflag key>`; baseline, the flag version.\n  - dd: ref `dd:\u003Cmonitor id>`; baseline, the monitor state.\n- **Interruptions are the gait.** A new ping mid-loop gets one line, bank it\n  or close it now, then back to the open loop.\n- **A tangent banks.** An idea that pulls sideways goes to `\u002Fclutch:fomo` in\n  one line, bank only, then return.\n- **A loop that turns into a build leaves ops.** Code, a design, a document\n  longer than a reply: name it, bank it as a focus or an idea, and stay in\n  ops. Building it is a fresh session declared with `\u002Fclutch:intent build`.\n- **No counts, no overdue framing, no backlog totals.** The sweep names what\n  needs a move now; the rest stays where it is, unmentioned.\n- **A loop that keeps not closing** gets `\u002Fclutch:triage`'s question, a\n  flinch at the wall versus never entering awareness, before anything else\n  engages. **A loop that wants a clock** gets `\u002Fclutch:sprint`.\n- **Re-sweep on request only.** `\u002Fclutch:ops re-sweep` is the only path to a\n  second sweep.\n- **A closed loop logs one line.** Append its `moved:` line with the\n  constitution's worklog snippet, silently; speak on MISS or an error.\n  That line is the only thing a closed loop writes; the sweep itself still writes nothing beyond its L2 and Auto lines and the tablet inbox items.\n  A tick's `moved:` line, the sweep's tick pass included, is the closed loop's one line.\n\n### Tick\n\nA tick reads only the wait loops, once each, and writes only their `moved:` lines.\nIt runs on `\u002Fclutch:ops tick`, on \"anything move?\" in an ops session, and\nas the sweep's tick pass. Read the wait loops with this line, once:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && L=$(clutch_open_loops) || exit; [ -z \"$L\" ] || printf \"%s\\n\" \"$L\" | LC_ALL=C cut -c1-300'\n```\n\nEach line is `\u003Cepoch> \u003Crepo> wait: \u003Ckind>:\u003Cref> \u003Cbaseline> \u003Ctext>`, oldest\nfirst, cut to 300 bytes. Empty output, or exit status 1 with no error\ntext (no worklog): no wait loops; say nothing about loops.\nAny other exit status means the wait loops are unreadable: say so in one line, never that nothing moved.\nExit status 1 with error text on stderr means the same: the wait loops are unreadable.\nA `\u002Fscripts\u002Fprelude.sh` not-found error means clutch is not loaded as a\nplugin: say so once and go on.\n\nRead each wait loop once, by its kind, against its baseline:\n\n- slack: replies in the thread newer than the baseline ts, from someone\n  other than the user.\n- gh: `gh pr view \u003Cnumber> --repo \u003Cowner>\u002F\u003Crepo> --json state,reviewDecision,updatedAt`;\n  a changed state or review decision, or `updatedAt` newer than the baseline.\n- linear: `updatedAt` newer than the baseline, or a new comment.\n- gmail: a message in the thread newer than the baseline id.\n- ld: a flag version other than the baseline.\n- dd: a monitor state other than the baseline.\n\nA loop that moved: append its `moved:` line first (record, then speak),\nwith the constitution's worklog snippet, verb `moved:` and text\n`\u003Ckind>:\u003Cref> \u003Cwhat moved>`. Copy the ref exactly from its `wait:` line,\nas its own token followed by a space, with no comma or colon after it.\nThen speak one line naming at most two movements and one smallest move.\nWhen nothing moved, a tick prints nothing.\nA tool that is not reachable gets one line naming it, and that loop stays open.\nA tick never re-arms a loop, never names one that did not move, and never says how long anything has waited.\nIn the sweep's tick pass, moved loops fold into the situation instead of their own lines.\n\n### Delegation\n\nA delegation policy lets ops do the chores you allowed, draft the rest, and\nshow only what touches your critical path. It lives in two optional sections\nof `~\u002F.clutch\u002Frituals.md`: `### Delegation`, one `- \u003Clevel>: \u003Cwhat it covers>`\nline each, and `### Windows`, the approval window times (see `\u002Fclutch:rituals`).\nWith no `### Delegation` section, nothing here applies and every outward action waits for a yes.\n\nClassify every inbound item the sweep reads against the policy:\n\n- L3: the yes gate, exactly as in Step 5.\n- L2: do it without a yes, then append one `moved:` line with the\n  constitution's worklog snippet, verb `moved:`, text `L2: \u003Cwhat was done>`,\n  and name it once as what moved.\n- Auto: post into a channel the policy names as automated, an intake queue\n  a process reads, exactly as its policy line describes, without a yes;\n  then append one `moved:` line the same way, text `Auto: \u003Cwhat was posted where>`, and name it once as what moved.\n  An Auto post of an item that awaits a review or a reply is also held as a wait loop, with the Step 5 snippet.\n- L1: draft it. A draft that touches the critical path shows now;\n  any other draft waits for the next approval window, unmentioned until then.\n- L0: one line, only when it touches the critical path.\n- Noise: never shown.\n\nThe critical path is today's focuses and the steps under the focus file's `## Critical path`.\nWith no focuses set, each L0 item shows as one line instead of being hidden.\nAn L1 item whose deadline falls before the next approval window touches the critical path, so its draft shows now.\nAnything the policy does not name is L3.\nWhen an item matches two levels, the stricter one wins, in this order: L3, L1, L0, Noise, Auto\u002FL2.\nAn item runs at L2 or Auto only when that level is its only match.\nAn item that matches both Auto and L2 is L3.\nA direct send is any message, email, channel post, thread reply or comment a person receives, except an Auto post as its policy line describes; no policy line makes one L2.\nAn @-mention in an Auto post makes it a direct send, so L3, unless its policy line names the person mentioned.\nA channel the policy does not name stays L3.\nAuto posts only to a channel whose name matches the policy line exactly and resolves to one channel; a near match, more than one match, no match or a DM is L3, named in one line.\nThe sweep reads each Auto channel the policy names once, looking back 5 days, for the item's link in any message there whoever posted it, and never posts an item already there nor proposes a direct ask for one.\nAn open `wait:` line or a `moved: Auto:` line for the same item also blocks a new post.\nAn Auto channel read that fails or cannot be read holds every item it covers at L3, named in one line.\nAn L2 action or Auto post that rests on a link or a state, such as a ticket linked to a PR you authored, reads it first and acts only when it holds.\nA state the line names that ops cannot confirm (for example ready while checks are pending, failing or unreadable, or a draft PR) holds the item at L3.\nA failed L2 action or Auto post gets one line naming it; it logs nothing and is not retried.\nL2 actions and Auto posts run after the sweep's reads end, never inside them.\n\nCheck the approval window once per sweep, after the situation:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && clutch_ops_due window'\n```\n\n`due` means a window time has passed since the last window (`### Windows`,\ndefault 11:00 and 16:30). Draft every L1 item that does not touch the\ncritical path, from the sweep's fresh read, and show the drafts in one\nscreen, numbered, approved with one yes or \"all but N\".\nEmpty output or an error: no window is due; say nothing about drafts.\nA due window with nothing to draft says nothing either.\nNo draft is kept between windows: each window reads fresh, so there is no pending list.\nIn the sweep, the window screen follows the situation, and approving it is the one smallest move.\nA tick never runs the window.\nAn approved window draft that awaits a reply or a state change is held as a wait loop, as in Step 5.\n\n### Tablet inbox\n\nThe tablet inbox holds pages and typed tasks pulled from a paper tablet,\nwhere work and personal lines mix.\nThe sweep reads it once, after the tick pass, whether or not today's focus file exists yet:\n\nAt the start of the tablet step, when `~\u002F.clutch\u002Frituals.md` sets a state dir and a focus file, move what waits in `\u003Cstate dir>\u002Ftablet.md` into today's focus file:\n\n```sh\nsh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" fold --work-state-dir '\u003Cstate dir>' --focus-file '\u003Ctoday's focus file>'\n```\n\nFill both paths as for the route below.\nEmpty output: nothing moved, or today's focus file does not exist yet; say nothing.\nA `folded` line names the moved items once, in one line, never counting them.\nA fold that exits 3 is unmentioned; any other fold error gets one line naming `\u003Cstate dir>\u002Ftablet.md`, and the sweep goes on.\nThen claim:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" claim'\n```\n\nEmpty output: nothing arrived; say nothing about the tablet.\nEach output line is one capture: its `folder`, `section` and `note`, its `pages` (each an image `file` and its `page_id`, with the `known_lines` already filed from it) and its new typed `todos`.\nA line with `held` names a capture that cannot be read: name it once, in one line.\nExit status 3 means the tablet inbox is busy; it waits for the next sweep, unmentioned. Any other error: one line, and the sweep goes on.\nA claim or route that exits 0 but prints a `tablet:` line on stderr: name it once, in one line.\n\nRead every page image and split it into items, one per written line or bullet: a task, a note, an action or an idea.\nSkip a line already in its page's `known_lines`, even spelled a little differently. Each typed task is one task item.\nSort each item by its own reading first: one that reads clearly as work or as personal takes that bucket.\nOnly an item that reads unclear takes a hint, in order: the `### Buckets` list under `## Ops` in `~\u002F.clutch\u002Frituals.md` (`- work: \u003Cterms>`, `- personal: \u003Cterms>`); today's focuses and critical path when today's focus file exists, which mark work; names in `~\u002F.clutch\u002Fpeople.md` when it exists, which mark work; the section, where Meeting is work.\nA hint alone never makes work of an item that reads personal. With no hint and no clear reading, the item is unsure.\nNever guess work: an unsure item files with the personal ones, marked unsure.\nTablet items are filed, never classified against the delegation policy: no L2 or Auto line acts on one.\n\nFile the claimed captures in one call, one quoted folder argument each, with the state dir and today's focus file:\n\n```sh\nsh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" route --work-state-dir '\u003Cstate dir>' --focus-file '\u003Ctoday's focus file>' '\u003Cfolder>' \u003C\u003C'TABLET_ITEMS'\n{\"pages_read\": {\"\u003Cfolder>\": [\"\u003Cpage>\"]}, \"items\": [{\"folder\": \"\u003Cfolder>\", \"text\": \"\u003Citem>\", \"kind\": \"\u003Ctask|note|action|idea>\", \"bucket\": \"\u003Cwork|personal|unsure>\", \"page_id\": \"\u003Cpage>\", \"date\": \"\u003Cdate>\"}]}\nTABLET_ITEMS\n```\n\nFill `\u003Cstate dir>` and `\u003Ctoday's focus file>` with absolute paths, never a `~` form; inside the single quotes, escape ' as '\\''.\nPass `--focus-file` whenever `~\u002F.clutch\u002Frituals.md` sets a focus file, even before today's exists.\nWith no focus file set in `~\u002F.clutch\u002Frituals.md`, drop `--focus-file` (work items then file in `~\u002F.clutch\u002Fpersonal.md` marked work, and the work line says so), and with no state dir set in `~\u002F.clutch\u002Frituals.md` drop `--work-state-dir` too; a state dir that is set but missing keeps `--work-state-dir`.\nPass every claimed folder but a `held` one, and under it in `pages_read` list only the `page_id`s you actually read, even when it has no new items: a folder whose pages were all read is retired.\nA folder with a page you did not read is held, not retired, and the next sweep reads it again.\nA typed task carries `todo_id` instead of `page_id`. `date` is the item's day as YYYY-MM-DD: a typed task's own `date`, or a Daily page's note name read as a date (`day_2026_1_5` is 2026-01-05).\nLeave `date` out when the item has no day of its own: a typed task whose `date` is empty, a page outside Daily.\nThe heredoc is quoted, so the items need JSON escaping only.\nWork tasks, notes and actions land under `## From the tablet` in today's focus file and work ideas in the fomo pool; every personal and unsure item, ideas included, in `~\u002F.clutch\u002Fpersonal.md` under today's date. Nothing here goes to any integration.\nWhen today's focus file does not exist yet, work tasks, notes and actions wait in `\u003Cstate dir>\u002Ftablet.md` under today's date instead, and the next sweep or morning moves them into today's focus file once it exists.\nA route that exits non-zero filed nothing.\nExit status 2 names on stderr what it refused: fix the items once and run the route again; if that fails too, say so in one line.\nExit status 3 means the tablet inbox is busy, unmentioned; any other error gets one line.\nEach output line is one capture: `routed` with what it filed per bucket, `held` with a reason, or `gone`.\nSpeak one line per bucket that got items, naming them shortened, never counting them: work, personal, unsure (named as unsure), and ideas named as banked.\nWork items in `waiting` get their own line, named the same way: they wait for today's focus file.\nNever ask the user about a missing focus file: morning creates it.\nA tablet line never counts captures, pages, items or questions, in digits or in words: not \"all three captures\".\nA capture held for a missing focus file, which happens only when the state dir is missing too, gets one line: the tablet pages wait for today's focus file.\nA capture held for another reason gets one line naming the reason.\n\nIf the sweep stops after the claim and before any route call, release them so the next sweep reads them again:\n\n```sh\nsh -c '. \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fprelude.sh\" && sh \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Ftablet-inbox.sh\" release'\n```\n\nNever release after a route call, whatever its exit status: the leases lapse on their own, and the claim count moves a capture that keeps failing to held.\nWhen the user says an unsure item is work, or a filed item sits in the wrong bucket, move its line between today's focus file, `\u003Cstate dir>\u002Ftablet.md`, `~\u002F.clutch\u002Fcaptures.md` and `~\u002F.clutch\u002Fpersonal.md` in that turn.\nA personal or unsure item never goes to the state dir, the fomo pool or any integration.\nA tick never reads the tablet inbox.\n\n### Session close\n\n`\u002Fclutch:eod` owns the day's close: the retro, tomorrow's focuses, the fun\nslot. Ops ends by naming the loops that closed this session, one line each,\nand the one open loop with its next move. Nothing else is written.\n\n## Skill interactions\n\n| Skill | In ops mode |\n|-------|-------------|\n| `\u002Fclutch:morning` | opens the day; ops runs the day it opened |\n| `\u002Fclutch:eod` | closes the day; ops hands off there |\n| `\u002Fclutch:fomo \u003Ccontent>` | a tangent, banked in one line, then back to the loop |\n| `\u002Fclutch:triage` | a loop that keeps not closing: wall or inattention |\n| `\u002Fclutch:sprint \u003Cgoal>` | a fixed 20 minutes on one loop |\n| `\u002Fclutch:intent build` | a loop that became a build: a fresh session |\n\n## What this skill does NOT do\n\n- Fire on its own, re-sweep on its own, or watch anything in the background\n- Send anything without a yes, or write to any integration without one beyond the L2 actions and Auto posts your policy lists\n- Produce a dashboard, a report, or a list for later\n- Count unread, waiting, overdue, or missed anything\n- Write code or design anything: that is a build session\n- Scaffold config, guess paths, or invent integrations\n\nWhy this works: see \"Tempo \u002F the gearbox\", \"Intent\", and \"Point of\nperformance\" in [GLOSSARY.md](..\u002F..\u002FGLOSSARY.md). The gear is engaged by\ninvitation, the sweep is one pulse that ends, and every loop closes at the\nmoment the user can act on it.\n",{"name":5,"description":7,"when_to_use":24,"argument-hint":25},"Use ONLY when the user explicitly asks for operations mode (\"ops\", \"operations mode\", \"run the day\", \"re-sweep\", \"tick\") or when \u002Fclutch:intent hands off after an \"ops\" answer. A passing mention of meetings, people, or tasks mid-conversation is not a trigger.","[re-sweep|tick]","main","f449f3d3ae5d6ec5aa8d5453ddc2a4d5c892ee91","skills\u002Fops",0,"https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch","https:\u002F\u002Fgithub.com\u002Fyuvalraz","http:\u002F\u002Fyuvalraz.com","2026-11-12 19:52:15",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add yuvalraz\u002Fclutch --skill ops",{"tool":40,"command":41},"bunx","bunx skills add yuvalraz\u002Fclutch --skill ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add yuvalraz\u002Fclutch --skill ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Fops\u002FSKILL.md",true,[],[49,56,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M77Z9RW2M6PA2JASTV15ZG6K","triage","Fork a \"task undone\" into its two opposite causes (a flinch at the wall versus never entering awareness) and hand back one immediate action.","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M77Z9PHFQ2KS87D7MG83KM3B","tempo","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Ftempo\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M77Z9MPANXWJJHYEY3HPKKEJ","status","Report whether the Clutch hooks are alive in this repo and this session.","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Fstatus\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M77Z9JY109XJ8PM7W0BXHF53","sprint","Run a fixed 20-minute sprint on one minimal shippable.","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Fsprint\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M77Z9G0QE5EVSPCP81TVJJZH","spark","Run the divergent chain-reaction protocol — ignition, ping-pong hops, cool-down with trace-back.","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Fspark\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M77Z9AZ7JEFWGR36HK2WFQ03","smallest-move","Name one smallest legal move when work stalls, stated as an ignorable recognition line rather than a demand.","https:\u002F\u002Fgithub.com\u002Fyuvalraz\u002Fclutch\u002Fblob\u002Fmain\u002Fskills\u002Fsmallest-move\u002FSKILL.md",[],[]]