researcherlisted

Evidence acquisition and validation for open questions: search, multi-angle or single-agent research, contradiction handling, synthesis, confidence, and judge validation. Always outputs canonical `research-state.json`; produces a verification-first `research-report.md` when the selected mode or user request requires a human-readable report. Use when users ask to research, investigate, verify, discover, analyze a market, assess technical feasibility, or fill factual gaps. Responsibility boundary: does not turn validated findings into a teaching/decision guide and does not render PDF; hand those outputs to `research-to-guide`, then `guide-pdf`.
createusernam/setup_project · ★ 0 · Data & Documents · score 62

Install: claude install-skill createusernam/setup_project

# /researcher — Multi-Agent Research Flow General-purpose research skill. Multiple agents explore in parallel, reach consensus, synthesize. General-purpose across domains — market research, technical feasibility, competitive analysis, user behavior, domain knowledge, any open question. Domain-specific applications extend it via `--mode custom` rather than a dedicated mode. **Cost posture**: free-first by default. Retrieval ladder starts with local/no-API-key tools; paid APIs only on explicit user request. Research cache with TTL avoids repeat searches. Bounded swarm size — many agents are for context-hygiene and broad sampling, not quality-through-quantity. ## Usage ``` /researcher [--mode market|technical|user|domain|custom] [--question "research question"] [--angles "angle1, angle2, angle3"] [--context "relevant background"] [--baseline <path>] # additive mode: research EXTENDS an existing doc ``` **Mode descriptions:** | Mode | Purpose | Worker types | |---|---|---| | `market` | Market landscape, sizing, competitors | domain + competitive | | `technical` | Technical feasibility, tools, approaches | technical | | `user` | User behavior, pain points, workarounds | user-behavior | | `domain` | Domain knowledge, concepts, terminology | domain | | `custom` | Free-form: user specifies angles and worker types explicitly | as specified in `--angles` | Without args: orchestrator decomposes the question automatically, infers