tool-triagelisted

# Tool-triage — decide how a discovered thing enters the stack Discovery skills (ai-radar, creative-hunt, sparks, daydream) FIND candidates. This one DECIDES what to do with one: **port it, plug it in, watch it, or pass** — for a named target, with the standing cost counted. Run it on any repo / tool / skill / paper / idea. Every verdict lands in a ledger so the setup compounds and never re-litigates. Sibling of ai-radar's Trial protocol; reuses its adopt/mine/skip vocabulary as **ADOPT / PORT / WATCH / PASS**. ## Two phases — PROPOSE (default), then EXECUTE (only on the user's OK) This skill does NOT auto-integrate. By default it runs **Phase 1 only**: assess, decide, design the smallest proving experiment, write the *proposed* ledger entry, and **stop with a review summary** — nothing built, nothing installed, nothing committed to a real repo. The user reviews the disposition + plan and says go (or redirects). Only then does **Phase 2** run: execute the approved plan and report back. The gate is deliberate — adding tooling is easy to do and hard to undo, so the call gets human eyes before any code or dependency lands. (If the user explicitly says "just do it" / "port it now," run both phases in one pass.) ## The core bias: PORT beats plug-in There is such a thing as too much tooling, and it's the default failure mode, not a rare one. Every tool you **ADOPT** is a *standing tax*: a dep to update, maybe an MCP server loaded every session, tokens per turn, an auth secret,