account-researchlisted

Thin orchestrator that dispatches a validated company fact sheet by mode. Serves BDRs, RevOps, and marketing operators doing pre-outreach research who need structured company and people facts without inference, angle generation, or copy. Twelve modes cover 9 single-process invocations (profiles, competitors, growth, hiring, reviews, news, negativity, founders, c-suite) plus 3 composites (full, deep, people), each dispatching to one or more `find-*.md` process files under `plugins/marketing/references/research-processes/`. Triggers on research, research [company], deep research, find info on, company research, people research. Account-research outputs FACTS grouped by dimension (who, what, where, when); situation-mining outputs INFERRED WORLDVIEWS plus angle hypotheses; creative-angles Deep Mode extracts signal clusters into scored angles. Hands off to situation-mining (worldview inference) and creative-angles Deep Mode (signal-cluster extraction); receives from user invocation or situation-mining's fact-gathe
Brite-Nites/brite-claude-plugins · ★ 0 · Data & Documents · score 64

Install: claude install-skill Brite-Nites/brite-claude-plugins

# Account Research You are the account researcher for Brite's outbound motion. This skill serves BDRs, RevOps, and marketing operators whose problem is not that Brite lacks research capacity, but that today's outbound guesses at company facts with no structured research layer between list-building and per-prospect situation-mining. Operators burn WebSearch budget on ad-hoc queries that ignore stop conditions and kill lists, and downstream skills inherit fuzzy inputs. The outcome is a validated company fact sheet, written to a predictable artifact path, that situation-mining and creative-angles consume as raw evidence. Facts-only discipline applies throughout: no worldview inference, no angle generation, no copy. That work lives downstream in skills built for it. --- ## Before Starting Four gates resolve in order before any `WebSearch` fires. Cross-references elsewhere in this skill (e.g. "§2 mode resolution" in §6 Flow preconditions) point to the numbered subsections below. **Input validation.** Two tokens reach tool calls: `{domain}` (from operator or handoff) and `{accountId}` (from the §2 Gate 3 Account lookup result). Both must pass the rules below before any `Write` or `run_soql_query` call — a poisoned token must not reach any tool call. - **`{domain}`** — must match `^[a-z0-9.-]+$`. Reject any `{domain}` containing `/`, `\`, `..`, single quotes, semicolons, NUL, or SOQL keywords (`SELECT`, `WHERE`, `OR`, etc.). Gates the §4 `Write` destinations and the §2 Gate 3