sales-company-research

작성자: openai

예약된 또는 인덱스 기반 회사 조사를 위한 명시적 전용 영업 워크플로우로, 지속적인 내부 리소스를 찾고 신뢰도 높은 영업 플러그인 메모리를 저장합니다...

npx skills add https://github.com/openai/role-specific-plugins --skill sales-company-research

Sales Company Research

Turn external company or partner research into a grounded, draft-only outreach approach. This skill owns research-to-outreach work: company or partner context, fit hypotheses, likely motion, and message drafts. It does not own data-first prospect-list enrichment, internal source-of-truth lookup, sending messages, or CRM writes.

Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.

Key Dependency Categories

  • ~~Sales Intelligence for company, contact, partner, firmographic, similarity, and external-signal context
  • ~~CRM for existing account, ownership, lifecycle, opportunity, and prior-engagement truth
  • ~~Knowledge & Files for approved positioning, proof points, partner criteria, and outreach guardrails
  • Public research for company-controlled facts, reputation, partner programs, and current market context

Use the user-provided company, domain, partner type, product, or offer as the anchor. If a material anchor is missing, ask only for the smallest input that changes the research path; otherwise proceed with clearly labeled assumptions.

Workflow

  1. Resolve the research target and commercial purpose: company fit, partner fit, referral landscape, reputation, or outreach approach.
  2. Gather the narrowest useful evidence from authoritative sources first. Keep sourced company or partner facts distinct from inferred fit, likely buyer need, and recommended motion.
  3. Explain why the target or partner type is promising, uncertain, or a poor fit. Name material evidence gaps instead of filling them with generic claims.
  4. Draft only the outreach artifact the user asked for, such as an approach, short email, message, connection request, or partner script. Do not send, post, create a draft in an external system, or update CRM.

Routing Boundaries

  • Use enrich-company-and-contact-data when the primary output is a list, missing fields, contact discovery, segmentation, qualification, or firmographic comparison.
  • Use find-key-internal-sources when the primary question is which internal owner, document, channel, approver, or source of truth to use.
  • Use plan-deal-strategy when the primary job is advancing a defined sale, negotiation, renewal, buying process, or initial sales motion rather than researching a target to shape outreach.

Next Step Options

After the first output, offer the most relevant follow-up from the options below. Offer one clear transition, not a menu. Suggest ONLY these unless you are very confident another option is more useful:

  • Improve the fit hypothesis, audience, angle, or sequencing using the user's guidance.
  • Draft an alternate outreach version for a different stakeholder or channel.
  • Hand the target to meeting prep or deal strategy when an active conversation or motion exists.
  • Create a concise research brief or internal account-team note after the content is reviewed.
  • Close the smallest material evidence gap that would change the outreach approach.

Next steps to avoid:

  • Sending outreach, creating external drafts, or writing CRM without a separate explicit request.

Output

Return a compact research-to-outreach package:

# Sales Research: [Target or Partner Segment]

## Sourced Context
- [Fact + source]

## Fit And Motion
- **Fit hypothesis:** [Inference and confidence]
- **Likely need or partner angle:** [Inference and evidence basis]
- **Risks / gaps:** [What remains unknown]

## Recommended Outreach Approach
- [Audience, angle, sequencing, and safe next step]

## Draft Outreach
> [Draft-only message]

No message was sent and no CRM record was changed.

---

{Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}

{Follow the instructions and output format/conditions in [Next Steps](../index/SKILL.md#4-next-steps)}

Rules

  • Cite material sourced claims with useful links when available.
  • Label inference clearly; do not invent company facts, partner terms, contacts, reputation claims, or fit evidence.
  • Keep outreach draft-only. Never send, post, create external drafts, or write CRM in this workflow.

openai의 다른 스킬

release
openai
커밋된 버전을 올리고, 이를 반영하고, 병합된 커밋에 태그를 단 후, Burrito 릴리스 워크플로우를 검증하여 Symphony 릴리스를 진행합니다. 다음과 같이 요청받았을 때 사용합니다…
signing-entitlements
openai
macOS 앱의 서명, 자격, 강화된 런타임 및 Gatekeeper 문제를 검사합니다. 코드 서명 실패, 누락된 자격 등을 진단하라는 요청을 받을 때 사용하세요.
building-ai-agent-on-cloudflare
openai
Cloudflare에서 Agents SDK를 사용하여 상태 관리, 실시간 WebSockets, 예약 작업, 도구 통합, 채팅을 통해 AI 에이전트를 구축합니다…
epigraphdb-skill
openai
온톨로지, 문헌, MR, 유전자-약물 및 지원 경로 증거에 대한 간결한 EpiGraphDB API 요청을 제출합니다. 사용자가 간결한 EpiGraphDB 요약을 원할 때 사용하세요.
runtime-behavior-probe
openai
런타임 동작 조사를 계획하고 실행하며, 임시 프로브 스크립트, 검증 매트릭스, 상태 제어, 결과 우선 보고서를 사용합니다. 다음 경우에만 사용하세요…
deep-security-scan
openai
사용자가 심층적이고, 철저하며, 다중 패스 또는 변동성을 줄이는 저장소 전체 또는 범위가 지정된 경로의 Codex Security 스캔을 요청할 때 사용합니다. 반복적으로 독립적인…
define-security-policy
openai
저장소 또는 구성 요소에 대한 SECURITY.md 지침을 정의, 검토 또는 업데이트합니다. 사용자가 Codex Security가 검토해야 할 대상과 범위를 벗어나는 항목을 명확히 하려 할 때 사용합니다…
validation
openai
Codex가 보안 스캔의 검증 단계에 이미 있거나 사용자가 하나 이상의 후보 보안 결과를 판별하도록 명시적으로 요청할 때 사용합니다…