Before asserting a causal or mechanism claim about tool/system behavior, OR a factual claim about what a CURRENT artifact (spec/doc/config/rule) says, requires, or contradicts, OR changing behavior to conform to a remembered criterion, OR a casual claim about what a task/artifact IS/DOES/its status/scope — list the factual premises the claim rests on, identify the cheapest falsifier first, and check it (read the installed source / query the system's own record / re-read the live, AUTHORITATIVE artifact — not a stale local cache) before asserting or acting. Use when about to explain WHY something happened, WHAT a tool will do, WHAT a spec/doc says or requires, or WHAT a task/artifact is/does/its status is, based on an assumed or remembered claim.
Before asserting a causal or mechanism claim about tool/system behavior, OR a factual claim about what a CURRENT artifact (spec/doc/config/rule) says, requires, or contradicts, OR changing behavior to conform to a remembered criterion, OR a casual claim about what a task/artifact IS/DOES/its status/scope — list the factual premises the claim rests on, identify the cheapest falsifier first, and check it (read the installed source / query the system's own record / re-read the live, AUTHORITATIVE artifact — not a stale local cache) before asserting or acting. Use when about to explain WHY something happened, WHAT a tool will do, WHAT a spec/doc says or requires, or WHAT a task/artifact is/does/its status is, based on an assumed or remembered claim.
Review hook-calibration JSONL logs and, for any log past its review threshold, false-positive-classify the matched records and emit ONE operator-routed Ask with the FP rate plus a flip/tune/keep recommendation — then advance the watermark. Use when running the periodic calibration sweep (scheduled or manual), or when asked to "review the calibration data" for the causal-premise / retrospective-trigger detector hooks.
Review hook-calibration JSONL logs and, for any log past its review threshold, false-positive-classify the matched records and emit ONE operator-routed Ask with the FP rate plus a flip/tune/keep recommendation — then advance the watermark. Use when running the periodic calibration sweep (scheduled or manual), or when asked to "review the calibration data" for the causal-premise / retrospective-trigger detector hooks.
Full implementation lifecycle for a Minsky task: read spec, plan, code, test, verify, commit, create PR, and drive to merge. All work happens in session workspaces with absolute paths. Use when implementing a task, starting development, or beginning work in a session.
Writing engineering essays, position papers, technical blog posts, and architecture memos intended for external or semi-external readers. Use when drafting or revising long-form argumentative prose — Notion position papers, public blog posts, shared design docs meant to persuade, RFCs with argumentative structure. Provides structural patterns (lead with position, justify after), section-heading heuristics (sentence case, specific, opinionated), an AI-voice-tells checklist (cadence uniformity, reveal- signposting, contrast sentences and rule of three, vocabulary, heading patterns), and a revision workflow. Skip for task specs (use create-task), rule files (use create-rule), code comments, or short internal-only docs.
Writing engineering essays, position papers, technical blog posts, and architecture memos intended for external or semi-external readers. Use when drafting or revising long-form argumentative prose — Notion position papers, public blog posts, shared design docs meant to persuade, RFCs with argumentative structure. Provides structural patterns (lead with position, justify after), section-heading heuristics (sentence case, specific, opinionated), an AI-voice-tells checklist (cadence uniformity, reveal- signposting, contrast sentences and rule of three, vocabulary, heading patterns), and a revision workflow. Skip for task specs (use create-task), rule files (use create-rule), code comments, or short internal-only docs.
Main-agent skill for coordinating the merge of a PR after the canonical `minsky-reviewer[bot]` review. Covers: gathering bot review status, running the local smoke test, reading posted review prose before retriggering, diagnosing reviewer-bot silence, and bypass-merging bot-authored PRs.