← ClaudeAtlas

hivemindlisted

This skill should be used when the user wants to know what the collective brain — social media (X/Twitter and Reddit), GitHub, the web, or research papers — is saying, building, or publishing about a topic — trends, sentiment, hot takes, trending repos, paper-vs-practitioner checks. Also runs recurring sweeps saved as configs. Responds to "ask the hivemind", "what's the hot shit in", "what does social media say", "what does reddit/twitter/X think", "what are people saying about", "check the socials", "--radar", "trending repos and what is X saying about them", "which repos get the most mentions", "what does the research say — and do practitioners agree", "repeat <slug>", "wiederhole den Sweep", "freeze this process", "frier den Prozess ein", or any question whose best answer lives in threads, comments, replies, repos, and preprints rather than articles. NOT for single-item lookups ("find me a paper on X", "search the web for Y") — use search/research skills. Read-only research — never posts.
pyros-projects/limitless · ★ 9 · AI & Automation · score 75
Install: claude install-skill pyros-projects/limitless
# 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. ```bash 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