hivemind

Hivemind — Ask the Collective Brain

Overview

Orchestrates the twitter CLI (X), rdt CLI (Reddit), gh CLI (GitHub), SearXNG (web), and the OpenAlex/arXiv APIs (papers) into a disciplined evidence search: resolve venues, classify the chain, search scoped, triage by relevance before engagement, deep-read where the knowledge lives, synthesize answer-first with receipts. The collective brain includes what people post (social), build (GitHub), publish (papers), and write (web) — each venue carries an evidence grade, and the brief always says which is which. Social is a weak-evidence surface: good for friction, language, pointers, sentiment; never factual validation. Papers and repo metadata are what validation looks like inside the skill.

Hivemind is read-only. The CLIs can post, like, and reply; this skill never does.

Phase 0 — Preflight (always, before anything else)

Probe every venue the ask might touch. The result is the live venue set — an input to chain classification (Phase 2): never plan a chain over a tool that already failed its probe.

command -v twitter rdt gh
twitter status; rdt status
gh auth status          # SAY which account is active — recipes that
                        # touch specific orgs/repos depend on it
curl -s -m 5 "http://localhost:8888/search?q=test&format=json" -o /dev/null -w "%{http_code}"   # web: expect 200 (403 = json format disabled — see web-playbook)
curl -s -m 5 "https://api.openalex.org/works?search=test&per-page=1" -o /dev/null -w "%{http_code}"  # papers

• Missing/broken tool → offer the 10-second fix FIRST: uv tool install twitter-cli / uv tool install rdt-cli / docker start for SearXNG (web-playbook has the recipe). Ask via AskUserQuestion if interactive. Non-interactive runs: the fix offer leads the reply — it is stated BEFORE any degraded or proxy work is performed, not appended to the result.
• Do not build scraping workarounds (proxies, mirror instances, raw JSON endpoints, search-engine site-scoping as a venue substitute) before the install offer has been made.
• Unauthenticated → point at rdt login / twitter's auth flow.
• A venue dead and user opts not to fix → degradation rules in "Tool failure semantics" below. Degrade, never block — but named venues are never silently substituted.