Sales Company Research

Run deep company-context research that finds durable, non-obvious resources future Sales workflows should reuse. This skill owns the research workflow: dynamic source discovery, source mapping, candidate ranking, save-versus-review decisions, focused follow-up questions, and the final research response. It uses sales:user-context for preflight, memory write policy, state-file structure, and readback.

Use this skill only when it is explicitly invoked, routed by the Sales index, or launched by the Sales Company Research automation. It is not an implicit catch-all for ordinary internal-source lookup, customer question routing, or one-off source finding; those usually belong to find-key-internal-sources or the focused Sales workflow that needs the source.

Skill Configuration

User Context

Mandatory pre-answer gate:

• Invoke sales:user-context in preflight mode by loading [$sales:user-context](../user-context/SKILL.md) and running its preflight script before searching connectors, retrieving evidence, saving memory, or drafting output. Do not look for a callable MCP tool named sales:user-context.
• Use the returned sales_preflight envelope as authoritative for saved context, source-category mapping, final obligations, and conditional guidance.
• Apply hard final_obligations unless the response is clarification-only. In scheduled research mode, do not append onboarding reminders or onboarding CTAs to the completed research response; this pinned research thread should end with the research result and any Where you can help questions. If an onboarding obligation matters, leave it to the onboarding thread or fold the underlying source gap into a research question only when it would improve future Sales research.
• Apply context_gap_note only when missing setup or inaccessible sources materially limits the research result.

Audience And Language