briesearchlisted

Research questions external to the codebase across library docs (Context7), the web (Tavily), local code through semantic source search, GitHub examples (gh), and the repo wiki (hallouminate), then synthesize with explicit confidence. Use whenever the user asks to research, look up, compare, or investigate something — phrases like "research X", "look up the API for Y", "compare libraries", "what does the doc say about Z", "find examples of how to do W", "is this library maintained", or "before I implement, what's the right approach". Use even when the user only mentions a library name without saying "research". Do NOT use for a single obvious file lookup or when the user already has enough evidence.
paulnsorensen/easy-cheese · ★ 12 · Code & Development · score 75

Install: claude install-skill paulnsorensen/easy-cheese

# /briesearch `/briesearch` runs in two contexts: - **User-invoked (default).** The user asked for research; produce the full report per `## Output` below. - **Internal-mode tier-2 caller.** `/cheese`'s tier-2 escalation (see `skills/cheese/SKILL.md` § Escalation) invokes `/briesearch` silently to fill missing external context when the cook-fast-path clarity check fails on the raw input. The synthesis returned to the caller is a one-liner suitable for the mini-spec's `## Provenance` section, but **the full cited research still gets written to disk** at the durable corpus's `research/<slug>/<slug>.md` per `## Output` below, with the slug derived from the parent's mini-spec slug. The mini-spec's `## Provenance` line links the artifact path so the citations are preserved and we never re-research later. Skip the durable write only when no source was actually fetched (e.g., the question was answered from local code patterns alone). Not for a single obvious file lookup or when the user already has enough evidence. ## Inputs Accept the whole user prompt as the research question. If version, framework, repo scope, or decision criteria are missing and would change the source plan, ask one clarifying question through the shared transport in [`../cheese/references/ask-user-question.md`](../cheese/references/ask-user-question.md); otherwise proceed with stated assumptions. ## Flow 1. **Classify** — library docs, current web facts, codebase pattern, GitHub example, comparison, or b