Triage a daily app-ideas brief into three buckets so the user only feasibility-tests the ones that survive eye-test. Reads an `ideas.md` produced by the daily-brief workflow and outputs one verdict per idea — OBVIOUS NO / WORTH FEASIBILITY / NEEDS INFO — with a five-word reason. Use whenever the user says "triage today's brief", "which ideas should I feasibility-test", "kill the noise in this brief", "/brief-triage", or pastes an ideas.md file and asks which to pursue. Research-only: do not write code, PRDs, or follow-up briefs from this skill. The output is a one-shot kill/keep table that gates which ideas move to `app-idea-feasibility`.
Maintain a CSV ledger of every app idea the daily-brief pipeline has ever surfaced, along with its fate (triaged, feasibility-tested, validated, building, shipped, abandoned). Prevents the user re-litigating the same idea three weeks later when it surfaces again from a different seed. Use whenever the user says "log this idea", "have I seen this idea before", "what did we kill last month", "show the ledger", "/idea-ledger", or mentions tracking ideas across briefs. The ledger is the source of truth for "what's the status of idea X" — the GitHub PR history is too noisy. Research/data-only: do not synthesize new ideas or make build decisions from this skill.
Audit `topics.yml` seeds against the rolling 30-day batch pool on the `data` branch. Reports which seeds produced zero surviving clusters, which produced only low-engagement noise, and recommends specific swaps. Use whenever the user says "audit my seeds", "which topics.yml seeds are dead", "is topics.yml pulling its weight", "swap weak seeds", "/seed-audit", or asks for a topics.yml refresh. Research-only: do not modify `topics.yml` automatically — produce a swap recommendation the user reviews.
Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web.