converse-recheck-premise
Converse's premise re-check and moot/benign visit close-out.
Skill by zookanalytics
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/zookanalytics-converse-recheck-premise
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/converse-recheck-premise
What's inside
- Skill name
converse-recheck-premise- Description
- Converse's premise re-check and moot/benign visit close-out.
- License
- MIT
- Instructions
- 57 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Step 2 — Re-check the premise The condition that justified filing a visit routinely dies before anyone claims it. Test the VISIT's own premise against live state before you prep, and before the rename: a visit that closes here should not have moved the operator's session title. `$CONV`, `$VISIT`, and `$SUBJECT` are resolved in step 1's claim block. Re-read the visit body. Its stated conditions ARE the premise, often bulleted literally — *"no `triage.hold` and no `gc.takeaway` on the root"*, *"its frontier is [...] UNASSIGNED"*. Check each one still holds, on the subject and on whatever bead the premise is about: ```bash gc bd show "$SUBJECT" --json | jq -r '.[0].metadata | "hold=\(.["triage.hold"] // "") takeaway=\(.["gc.takeaway"] // "")"' ``` NON-EMPTY is the test for `triage.hold` — an EMPTY stamp is a CLEARED hold. A `gc.takeaway` dates the last sitting rather than naming a live wait: read what it says, then check whether that wait is still open. Two readings end the visit here, with nothing posted: - **moot** — the premise no longer holds. The frontier was routed, the bead was closed, another visit already settled it. - **benign** — the premise holds but needs no human: the wait is already named by a non-empty `triage.hold` or an open demand bead, or the condition is a known acceptable state. **An open PR awaiting the operator's review is the canonical case** — their own review queue, and handing it back is the bug this step prevents. **A takeaway is never a benign wait on its own**, because nothing clears it. Re-check the ids in the body (`bd show`, and `gc bd list --parent "$SUBJECT" --all`); it is moot only if something is open again. Close it out with `converse-close-out.sh`, which appends the reading to the subject's notes, stamps `gc.outcome=<moot|benign>` on the visit, reads it back, and closes the visit — no takeaway, nothing posted: ```bash VISIT="$VISIT" SUBJECT="$SUBJECT" \ "$CONV/converse-close-out.sh" <moot|benign> "<the premise, and what is true instead>" ``` Once it exits 0, drain (the prompt's **How this thread ends**). **Post nothing** — no framing, no sign-off, not even "this turned out to be fine". Deliberately **no takeaway stamp** either: it is the subject's headline of what it NEEDS, and one for a visit that needs nobody spends the attention this exit saves. The exit is gated on being *named*: if you cannot point at the stamp or state that makes this benign, you hold the sitting. Uncertain is not benign. When the premise still holds and needs a human, this visit earns a sitting: prep it (steps 3–4, the `converse-prep` skill).
From zookanalytics/gc-toolkit, MIT.
More from zookanalytics/gc-toolkit
- 0.620score
review-correctness
zookanalytics
The method for the correctness check, the standing review of whether a change is correct and safe as merged.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
review-arch
zookanalytics
The method for the arch check — the Architect, steward and gatekeeper of the repo's high-level architecture.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
review-triage
zookanalytics
The method for the triage check — a broad, cheap scan that does not judge a change but decides which specialist checks it needs, then records that decision by…
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
learning-distill
zookanalytics
The promotion-judgment rubric for the feedback-learning loop — use when you are the mol-feedback-distiller judging pending feedback observations into…
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
prs
zookanalytics
Use when something has to happen to an open pull request or its anchor bead.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
records
zookanalytics
Use when you need to write down what was decided, what happened, or what a bead needs, so whoever reads it next inherits it.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
review-pm
zookanalytics
The method for the PM check — the product lens on a change, reviewed by a peer to the author rather than an order-taker.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
work
zookanalytics
Use when you have to say that something needs doing, carry out a decision about who does it, or change work already asked for.
SkillAFreshness: A★ 5Claude Code +9 - 0.616score
gc-demo-script
zookanalytics
Generates a demo:capture-format script from a closed Gas City work bead by reading the bead tree, git commits, and PR diff
SkillAFreshness: A★ 5Claude Code +9 - 0.615score
review-demo
zookanalytics
The method for the demo check, the visual review.
SkillAFreshness: A★ 5Claude Code +9 - 0.615score
waits
zookanalytics
Use when something must not go yet because it has to wait for other work to land, or for a person to decide or act.
SkillAFreshness: A★ 5Claude Code +9 - 0.610score
converse-hold
zookanalytics
Converse's demand-gate hold (safety-critical).
SkillAFreshness: A★ 5Claude Code +9
Signals
- Stars
- 5
- Forks
- 1
- Open issues
- 0
- Last commit (this folder)
- Oct 7, 2026 (22 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/zookanalytics/gc-toolkit
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from zookanalytics
- 0.620score
review-correctness
zookanalytics
The method for the correctness check, the standing review of whether a change is correct and safe as merged.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
records
zookanalytics
Use when you need to write down what was decided, what happened, or what a bead needs, so whoever reads it next inherits it.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
prs
zookanalytics
Use when something has to happen to an open pull request or its anchor bead.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
learning-distill
zookanalytics
The promotion-judgment rubric for the feedback-learning loop — use when you are the mol-feedback-distiller judging pending feedback observations into…
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
review-pm
zookanalytics
The method for the PM check — the product lens on a change, reviewed by a peer to the author rather than an order-taker.
SkillAFreshness: A★ 5Claude Code +9 - 0.619score
work
zookanalytics
Use when you have to say that something needs doing, carry out a decision about who does it, or change work already asked for.
SkillAFreshness: A★ 5Claude Code +9
Cite this page
converse-recheck-premise skill. Agent Mart. https://agentmart.dev/skills/zookanalytics-converse-recheck-premise (last updated 2026-10-24)