← ClaudeAtlas

openloopslisted

Answer "what is being done, and what needs my attention?" across every coding session and every repository, by running the `ol` command and synthesising its answers rather than pasting them. Use when the user asks what needs their attention, what their agents have been doing or left unfinished, what they missed while they were away, what they still owe an agent, what is blocked or waiting on another repo, or what quietly became unblocked and nobody noticed. Triggers on: 'what needs my attention', 'anything waiting on me', 'catch me up', 'what did I miss', 'where are we', 'status across my sessions', 'what are my agents doing', 'what did my sessions leave open', 'what do I owe', 'what am I blocked on', 'what can I start now', 'give me the overview', 'morning briefing', 'what should I look at first', 'is anything stuck'. Also use before planning a day's work, so the plan starts from what is outstanding rather than from memory. Read-only: it never closes, reopens or relabels anything.
thorwhalen/openloops · ★ 0 · Data & Documents · score 71
Install: claude install-skill thorwhalen/openloops
# openloops: what is being done, and what needs your attention An **open loop** is a commitment that outlived the session that made it and that nothing is watching. The `ol` command finds them and re-checks them. **Gathering the facts is its job. The synthesis is yours** — and a raw paste of three command outputs is a failure of this skill, not a use of it. If `ol` is not on the PATH, say so and stop rather than guessing: `pip install openloops`. Two of the three commands also need the GitHub CLI (`gh`) logged in. ## The three commands, and which question each one answers | The user is asking | Run | It reads | Cost | |---|---|---|---| | what were my sessions doing / what did they leave open? | `ol` | this machine's session transcripts | a second or two | | what do I still owe my agents? | `ol owed` | open `manual-task` issues, **re-running each one's check** | tens of seconds | | what is waiting on another repo — and what is not any more? | `ol blocked` | GitHub `blocked_by` edges, resolved | tens of seconds | **`ol owed` and `ol blocked` are slow on purpose.** They are not listing a cache; they are asking the world again, one shell predicate or one API call per row. That is the entire reason to prefer them over a `gh search issues` one-liner — and the reason not to run them reflexively. So: **match the command to the question.** - "what were my sessions doing", "catch me up on yesterday" → `ol` alone answers what was *done*. Do not spend a minute on `owed` and `blo