Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

partnership-bd合伙企业

Agent Skill

partnership-bd 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

912

周安装

38

GitHub Stars

3

下载量

304
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:partnership-bd(合伙企业)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/partnership-bd
安装命令:
npx skills add https://github.com/oldwinter/skills --skill partnership-bd
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill partnership-bd

简介

用于查找、检索和筛选相关信息,支持关键词和任务场景定位。

  • 适合在 Codex、Claude 等宿主中快速获取候选结果。
  • 可结合来源仓库 README 核验具体用法和权限范围。
  • 安装前建议确认是否会触发联网或文件读写操作。
  • partnership-bd 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Partnership & BD

Scope

Covers

  • Defining partnership goals and selecting the right partnership type (platform, integration, channel, referral, co-marketing)
  • Building a prioritized partner target list with a scoring model and “finger-on-the-button” decision-maker mapping
  • Crafting a clear value exchange (why them / why us / why now), including alpha/beta + case-study angles
  • Designing an outreach + relationship system (warm intros + ethical cold outreach + lightweight content plan)
  • Aligning internally on a scalable partner offer (avoid bespoke one-off deals; define negotiation parameters)
  • Negotiation prep (guardrails, walk-away, patience) and a simple deal process (MAP + pilot)
  • Partner launch + operating cadence (enablement, metrics, check-ins)

When to use

  • “Create a partnership strategy and a target partner list.”
  • “We need an integration/platform partnership—draft a pitch and outreach sequence.”
  • “Design a channel/referral partner program for distribution.”
  • “Help me negotiate partnership terms and define what’s negotiable vs standard.”
  • “We signed a partner—build a launch plan + operating cadence.”

When NOT to use

  • You need to define the product/ICP/positioning from scratch (do that first; then return here)
  • You want high-volume spam outreach or anything deceptive/manipulative
  • You need legal advice or contract language (use this skill for non-legal term framing only; involve counsel)
  • You’re doing M&A, fundraising, or procurement/vendor selection (different motion)

Inputs

Minimum required

  • Partnership objective(s) + success metric(s) (e.g., qualified pipeline, revenue, distribution, integrations shipped)
  • Product summary + differentiation (1–2 sentences) and what you can offer partners (API/integration, audience, revenue share, credibility, data)
  • Target customer/market and the partner archetype(s) you want (platform, integration, channel, referral, strategic)
  • Constraints: timeline, geo/segment focus, compliance/regulatory constraints, exclusivity appetite, budget
  • Internal capacity: BD owner, engineering bandwidth (if integration), marketing bandwidth (if co-marketing)

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md.
  • If key data is missing, proceed with explicit assumptions and include an Assumptions & unknowns section.
  • For high-stakes commitments (exclusivity, data sharing, regulated claims), require human review and document a safe default.

Outputs (deliverables)

Produce a Partnership & BD Execution Pack (Markdown):

  1. Context snapshot (objective, constraints, current baseline)
  2. Partnership thesis (why partner, why now, partner types, non-goals)
  3. Partner target list + scoring (top 10–30) + decision-maker + intro path
  4. Partner pitch kit (1-page pitch + case-study/alpha angle + outreach templates)
  5. Scalable offer + negotiation parameters (tiers, what’s standard vs bespoke, guardrails)
  6. Deal process plan (MAP/pilot definition, stakeholders, timeline, “walk-away”)
  7. Launch + operating cadence (enablement, co-marketing plan, metrics, check-ins)
  8. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md

Workflow (7 steps)

1) Intake + choose the partnership motion

  • Inputs: User context; references/INTAKE.md.
  • Actions: Clarify the objective and pick the partnership type(s): platform/integration, channel/referral, strategic/co-marketing. Identify whether the motion is network-dependent (regulated or concentrated buyer markets) and what “success” looks like in 30/60/90 days.
  • Outputs: Context snapshot + partnership thesis draft + assumptions.
  • Checks: Objective is measurable; non-goals and constraints are explicit.

2) Define a scalable partner offer (avoid bespoke deals)

  • Inputs: Product capabilities; engineering/marketing constraints.
  • Actions: Draft the “partner package”: what you can reliably offer (integration tier, enablement, support, co-marketing) and what you will not do. Define negotiation parameters and pre-approved ranges to increase deal velocity.
  • Outputs: Offer tiers + negotiation parameters sheet.
  • Checks: A teammate could run a partner conversation without inventing bespoke promises.

3) Build the partner universe + score + pick the first wedge

  • Inputs: Target market; competitor/adjacent ecosystem; any existing relationships.
  • Actions: List plausible partners, then score and shortlist based on mutual value, reach, feasibility, and decision velocity. For each top candidate, identify the “finger-on-the-button” decision-maker and the lowest-social-capital intro path.
  • Outputs: Partner list table + scoring model + top wedge recommendation.
  • Checks: Each top partner has a clear “why them” and a specific next action (intro, email, event, content hook).

4) Craft the value exchange + pitch narrative (case study / alpha angle)

  • Inputs: Offer tiers; proof points; partner incentives.
  • Actions: Write a 1-page pitch that shows how *your* success helps *their* goals. For major platforms, propose an alpha/beta or “flagship case study” angle. Keep the ask crisp and low-friction.
  • Outputs: 1-page pitch + talk track + proof points.
  • Checks: The pitch answers: “Why now?”, “Why us?”, “What do you want?”, “What’s in it for them?”

5) Outreach + relationship system (warm first, ethical cold second)

  • Inputs: Target list; pitch; available channels.
  • Actions: Build outreach sequences (warm intro asks, cold emails/DMs, follow-ups) and a lightweight content plan to build credibility. Track outreach as experiments: message → meetings → iteration.
  • Outputs: Outreach kit + 2–4 week execution plan.
  • Checks: Messages are specific, respectful, and permissioned; each has a single clear ask.

6) Deal process + negotiation (patience + guardrails)

  • Inputs: Negotiation parameters; partner priorities; risk constraints.
  • Actions: Define a deal path (discovery → pilot → term sheet → launch). Use strategic patience when leverage is asymmetric; be willing to say “not yet” to improve terms. Document walk-away conditions and any exclusivity logic.
  • Outputs: Mutual action plan (MAP) + pilot definition + key terms outline.
  • Checks: You can explain what you will trade (and won’t) in one minute; the next step is scheduled and owned.

7) Launch + operate + quality gate

  • Inputs: Draft pack; references/CHECKLISTS.md; references/RUBRIC.md.
  • Actions: Produce a launch plan (enablement + co-marketing + measurement) and an operating cadence (weekly/biweekly check-ins, QBR). Run the checklist and score the rubric. Always add Risks / Open questions / Next steps.
  • Outputs: Final Partnership & BD Execution Pack.
  • Checks: The plan is executable this week and includes a learning loop.

Quality gate (required)

Examples

Example 1 (platform/integration partnership): “Use partnership-bd. We’re a B2B SaaS analytics tool. Goal: 3 co-sell integrations that each drive 5 qualified leads/month by end of Q2. Targets: HubSpot + Snowflake ecosystem partners. Constraints: 1 engineer half-time. Output: a Partnership & BD Execution Pack with partner scoring, an integration-tier offer, outreach sequences, and a launch cadence.”

Example 2 (regulated, network-dependent BD): “Use partnership-bd. We’re selling into healthcare and need payer/provider partnerships. We have one warm connector but intros are expensive. Output: a prioritized partner list, crisp use-case one-pager, intro asks, and a deal process with walk-away conditions.”

Boundary example: “Write a generic cold email that works for anyone and send 10,000 messages.” Response: refuse spam; ask for a defined partner archetype and a small, ethical outreach experiment plan. If the goal is broad demand gen, use a marketing/content skill instead.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.6%
按下载量换算102

Claude

28.84%
按下载量换算88

Cursor

21.57%
按下载量换算66

Gemini CLI

9.1%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills