Token导航 LogoToken导航

Agent Skill · 研究检索

partnership-bd(合伙企业)

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

partnership-bd 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 44,490。

总安装 912周安装 38GitHub Stars 3下载 304核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

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

来源仓库内路径:skills/partnership-bd

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oldwinter/skills --skill partnership-bd;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

partnership-bd 怎么安装?

在终端执行 npx skills add https://github.com/oldwinter/skills --skill partnership-bd。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

partnership-bd 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

partnership-bd 需要什么权限?

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

partnership-bd 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

partnership-bd 用的人多吗?

公开数据是累计安装 912 次,近一周安装 38 次,下载 304 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

partnership-bd 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
partnership-bd

合伙企业 · 本页

9123需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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