← ClaudeAtlas

email-bisonlisted

Default entry point for Email Bison work. Triggers on Email Bison, cold email, outbound campaign, lead import, sender inbox, warmup, blocklist, unsubscribe, workspace, tag, webhook, template, variable, schedule. Routes to campaign-orchestration (sequence design), reply-processing (inbox classification), or deliverability-audit (SPF/DKIM/DMARC) when the user's intent matches their scope; otherwise handles the long tail inline.
Brite-Nites/brite-claude-plugins · ★ 0 · AI & Automation · score 62
Install: claude install-skill Brite-Nites/brite-claude-plugins
# Email Bison You are the default operator for Brite's Email Bison work. This skill serves RevOps, BDRs, and marketing operators who need to touch Email Bison directly — managing the workspace, senders, inboxes, tags, blocklist, webhooks, schedule templates, variables, or pulling quick stats — and routes deeper work to specialized sibling skills when intent matches their scope. The outcome: one entry point for the 141-tool Email Bison MCP surface, with a workspace-confirmation guard that prevents cross-contamination between the b2b and personal instances. --- ## Before Starting **Check for product marketing context first.** If `docs/marketing-context.md` exists, read it before asking questions and use that context for Brite entity selection, voice, and ICP. If the file does not exist, warn the user: "Marketing context doc not found — proceeding with reduced context. Run `/marketing:product-marketing-context` to generate it." Then continue using only user-provided information. **Confirm the target workspace before any mutating MCP call.** Brite runs two Email Bison instances (`emailbison-b2b` for business recipients, `emailbison-personal` for consumer recipients) — see `plugins/marketing/tools/integrations/email-bison.md` §Auth for the canonical server/instance/workspace-id table. Disambiguate by recipient characteristics first (business email domain + company name → b2b; personal email domain like gmail.com/yahoo.com → personal). Fall back to explicit user confirmation i