sales-company-research

作成者: openai

明示的なセールスワークフローで、スケジュールまたはインデックスルーティングによる企業調査を行い、耐久性のある内部リソースを見つけ、信頼性の高いSalesプラグインメモリを保存します…

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
コミットされたバージョンを更新して Symphony リリースを切り、それをコミットし、マージされたコミットにタグを付け、Burrito リリースワークフローを確認します。求められた際に使用します…
signing-entitlements
openai
macOSアプリの署名、権限、ハード化されたランタイム、Gatekeeperの問題を検査します。コード署名の失敗や権限の欠落などの診断を求められた際に使用します。
building-ai-agent-on-cloudflare
openai
Cloudflare上でAgents SDKを使用してAIエージェントを構築し、状態管理、リアルタイムWebSocket、スケジュールタスク、ツール統合、チャットなどを実現します。
epigraphdb-skill
openai
オントロジー、文献、MR、遺伝子-薬剤、サポートパスエビデンスに関するコンパクトなEpiGraphDB APIリクエストを送信します。ユーザーが簡潔なEpiGraphDBサマリーを希望する場合に使用します。
runtime-behavior-probe
openai
一時的なプローブスクリプト、検証マトリックス、状態制御、および発見事項優先のレポートを用いて、ランタイム動作調査を計画・実行します。以下の場合にのみ使用してください…
deep-security-scan
openai
ユーザーがリポジトリ全体またはスコープ指定パスに対する深く網羅的な、マルチパスまたはバリアンス低減型のCodexセキュリティスキャンを求めた場合に使用します。独立した反復実行を複数回行います…
define-security-policy
openai
リポジトリまたはコンポーネントのSECURITY.mdガイダンスを定義、レビュー、または更新します。ユーザーがCodex Securityがレビューすべき内容、対象外の内容を明確にしたい場合に使用します。
validation
openai
Codexがセキュリティスキャンの検証段階にすでにある場合、またはユーザーが1つ以上の候補となるセキュリティ findings が…かどうかを判断するよう明示的に求めた場合に使用します。