drain
/drain
Apply when asked to drain, work through or clear this repository's follow-ups, or when nothing else is asked and the repository's own instructions put its follow-ups next. Takes the open follow-ups one at a time through the follow-up tools, does each through the repository's own change loop, ticks it or hands it back, and stops when none is left or the list stops shrinking.
- Author
- Esposter ↗
- Repository
- Esposter ↗
- Licence
- Apache-2.0
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Apply when asked to drain, work through or clear this repository's follow-ups, or when nothing else is asked and the repository's own instructions put its follow-ups next. Takes the open follow-ups one at a time through the follow-up tools, does each through the repository's own change loop, ticks it or hands it back, and stops when none is left or the list stops shrinking.
Original author description
Apply when asked to drain, work through or clear this repository's follow-ups, or when nothing else is asked and the repository's own instructions put its follow-ups next. Takes the open follow-ups one at a time through the follow-up tools, does each through the repository's own change loop, ticks it or hands it back, and stops when none is left or the list stops shrinking.
How it works
- The loop
- Stopping
SKILL.md preview
--- name: drain description: Apply when asked to drain, work through or clear this repository's follow-ups, or when nothing else is asked and the repository's own instructions put its follow-ups next. Takes the open follow-ups one at a time through the follow-up tools, does each through the repository's own change loop, ticks it or hands it back, and stops when none is left or the list stops shrinking. --- # Drain Takes this repository's open follow-ups one at a time and does each through the repository's own change loop, until none is left. The values the tools take — the list id, the repository, the session id and the time zone — are in this session's context under "Follow-ups", passed unchanged. ## The loop 1. **Set the checkpoint.** Read `todoList_readFollowUps` and note how many are open. 2. **Read again every turn.** Call `todoList_readFollowUps` before each follow-up, never reusing an earlier answer: the owner ticks, deletes and reorders in the browser while a drain runs. None left: stop and report what was done. 3. **Check convergence.** Once as many follow-ups have been taken as the checkpoint counted, compare the open count with it. Not lower: stop and report that the list is not converging, leaving everything open for the owner. Lower: that count becomes the checkpoint. 4. **Take the first** — the list's order is the owner's, so the first is what goes first. 5. **Hand it back or do it.** Call `todoList_handBackFollowUp` with the reason when doing it would need a design decision or a choice between readings its notes leave open; anything spent outside the repository's review queue, such as opening a pull request, pushing a protected branch, a paid service or a destructive change to shared infrastructure; or more than one change. Otherwise do it exactly as the repository says any change is done — its checks, its commit, its push — and capture any new follow-up found along the way (the `capture` skill). 6. **Tick it** with `todoList_completeFollowUp` only once its commit exists, with a line naming the commit, then go back to step 2. ## Stopping The drain stops in exactly two cases: nothing is left, or the list is not shrinking. Each pass should close more than it opens; one that captures follow-ups as fast as it closes them will not converge however long it runs, and the owner reads the list before it goes on. It adds no approval step of its own. Its changes are the same kind a session makes when asked directly, so they rely on the repository's own safety net, such as a review queue, rather than on the drain.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Esposter/Esposter | 90 | Apache-2.0 |
| harmix/open-stanley | 85 | MIT |
Database snapshot: 13.11.2026 · package version 4099fe641708 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 84work-loop
Drain the work-item backlog as a self-paced autonomous loop, launched via /loop: each cycle triages raw intake, admits items through the fail-closed work-class gate, runs them through /work-items:work under an adaptive cap, and checks the drain exit. Authors PRs, never merges.… - 90esp32-open-drain-bus-planning
Use when designing, reviewing, debugging or validating open drain bus planning for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release. - 100merge-queue
Inspect and drain the local deferred-merge queue — worktree merges /finish deferred on a transient block, which a launchd drainer retries until they land. `list` (default), `drain`, or one issue id. Use when the user says 'merge queue', 'what merges are pending', 'drain the… - 100drain-labeled-backlog
This skill should be used when draining a labeled issue backlog (deferred-scope-out, code-review, type/security) in one cleanup PR. Groups by code area and delegates to soleur:one-shot. - 100gh-create-issue
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format. - 100speclink-apply
Use when a change's tasks are ready to implement, or when resuming one left half-done — works through the task list, marking each checkbox as it lands.