Agent skill

Partnership Outreach

by shawnpang in shawnpang/startup-founder-skills

When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals.

MITAuto-check passedSales & Support

Install Partnership Outreach

skills CLI
$ npx skills add shawnpang/startup-founder-skills --skill partnership-outreach -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shawnpang/startup-founder-skills partnership-outreach --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/partnership-outreach .claude/skills/partnership-outreach && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
partnership-outreach
GitHub stars
343
Token cost
~2.7k tokens
SKILL.md length
1,412 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals.

  • Works in 7 steps: Gather context — Read startup-context if… → Identify partner fit — Use the Partner… → Map the win-win — Define what each side… → …
  • Mentions partnerships
  • SKILL.md covers When to Use, Context Required, Workflow and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Partnership Outreach is an agent skill from shawnpang/startup-founder-skills. When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Proposals and quotes. The repository describes itself as: AI agent skills for tech startup founders — fundraising, sales, product, recruiting, engineering, legal, ops, and growth. Works with Claude Code, Cursor, Codex, and any Agent… The licence is MIT.

When your agent uses it

  • Mentions partnerships
  • Business development
  • Integration proposals
  • Channel partnerships

Example prompts

  • “/partnership-outreach”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Gather context — Read startup-context if available. Understand the product, traction, and partnership goals.
  2. Identify partner fit — Use the Partner Evaluation Framework to assess whether this is a strong partnership opportunity.
  3. Map the win-win — Define what each side gets from the partnership. If you cannot articulate both sides, the proposal will fail.
  4. Find the right contact — Identify the BD, partnerships, or product person at the target company. Avoid generic inboxes.
  5. Draft the outreach — Write the partnership email or LinkedIn message using the frameworks below.
  6. Prepare the proposal — If the initial outreach gets a response, draft a lightweight partnership proposal (1-2 pages).
  7. Define success metrics — Propose how both sides will measure whether the partnership is working.

What it can do on your machine

Read from SKILL.md and the folder at commit 4ad31b4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Partnership Outreach loads about 2.7k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 1,412 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shawnpang/startup-founder-skills at commit 4ad31b4, republished under its MIT licence (© shawnpang). 1,412 words, ~2,664 tokens.

Download SKILL.mdSave it as .claude/skills/partnership-outreach/SKILL.md (or your agent's skills folder).
name
partnership-outreach
description
When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances.
related
cold-outreach, proposal-generation
reads
startup-context

Partnership Outreach

When to Use

Activate when a founder needs to identify and reach out to potential partners, write partnership emails, propose integrations, or create co-marketing proposals. Also use when the user says "I want to partner with X," "help me write a BD email," "how do I propose an integration," "co-marketing opportunity," or "I need a channel partner strategy."

Context Required

From startup-context or the user:

  • Your product and positioning — What you do and who you serve
  • Partnership goal — Integration, co-marketing, reseller/channel, referral, or strategic alliance
  • Target partner — Company name, relevant product/team, why they are a good fit
  • Shared audience — The overlapping customer segment you both serve
  • Your leverage — What you bring to the table (users, distribution, technology, content, brand)
  • Current traction — Metrics that demonstrate your value as a partner (users, revenue, growth rate)

Workflow

  1. Gather context — Read startup-context if available. Understand the product, traction, and partnership goals.
  2. Identify partner fit — Use the Partner Evaluation Framework to assess whether this is a strong partnership opportunity.
  3. Map the win-win — Define what each side gets from the partnership. If you cannot articulate both sides, the proposal will fail.
  4. Find the right contact — Identify the BD, partnerships, or product person at the target company. Avoid generic inboxes.
  5. Draft the outreach — Write the partnership email or LinkedIn message using the frameworks below.
  6. Prepare the proposal — If the initial outreach gets a response, draft a lightweight partnership proposal (1-2 pages).
  7. Define success metrics — Propose how both sides will measure whether the partnership is working.

Output Format

Deliver the appropriate materials based on the partnership stage:

  • Partner evaluation — Fit assessment using the evaluation framework
  • Initial outreach email/message — The first touch to the target partner
  • Follow-up sequence — 2-3 follow-ups with different angles
  • Partnership proposal — 1-2 page document outlining the partnership structure, mutual benefits, and next steps

Frameworks & Best Practices

Partner Evaluation Framework

Before reaching out, score the potential partner on these dimensions:

DimensionStrong SignalWeak Signal
Audience overlapYou share the same ICP but do not competeMarginal audience overlap or direct competition
Complementary valueYour products are better together than apartNice-to-have integration with limited user benefit
Stage alignmentSimilar company stage or the larger partner has an active partner programMassive stage mismatch with no partner program
Distribution leveragePartner has distribution you lack (or vice versa)Neither side brings meaningful new distribution
Strategic timingPartner is expanding into your space or just launched relevant featuresNo clear strategic reason for them to partner now

Score each dimension 1-5. A score of 20+ suggests a strong partnership opportunity. Below 15, reconsider whether it is worth pursuing.

Partnership Types and When to Use Each
TypeWhat It IsBest ForTypical Structure
IntegrationBuild a technical connection between productsComplementary SaaS toolsJoint engineering effort, shared docs, marketplace listing
Co-marketingJoint content, webinars, or campaignsCompanies with overlapping audiencesShared leads, co-branded content, cross-promotion
ReferralInformal lead sharingTrusted companies in adjacent spacesReferral fees or reciprocal introductions
Reseller/ChannelPartner sells your productAgencies, consultants, system integratorsRevenue share, tiered pricing, enablement materials
Strategic allianceDeep collaboration on product or GTMCompanies with highly aligned visionJoint roadmap, executive sponsorship, shared metrics
Outreach Email Framework

Partnership emails differ from sales emails. You are proposing a collaboration, not selling a product. The tone should be peer-to-peer and the value proposition must be bilateral.

Structure: Shared Audience - Mutual Benefit - Proof - Lightweight Ask

  1. Open with the shared audience — Show you understand who they serve and that you serve the same people
  2. Name the mutual benefit — Be specific about what each side gains. Vague "synergies" get ignored.
  3. Provide proof of your value — Traction metrics, shared customers, or a specific integration use case
  4. Make a lightweight ask — Request a 20-minute call, not a signed partnership agreement
Email Principles for Partnership Outreach
  • Lead with what you bring, not what you want. Partners care about your distribution, your users, and your brand — not your desire to partner.
  • Be specific about the opportunity. "We should partner" means nothing. "30% of our 2,000 customers also use your product and have asked for an integration" means everything.
  • Quantify when possible. Numbers make the opportunity tangible: user count, shared customers, potential revenue, audience size.
  • Reference existing overlap. If you share customers, mention it. If their users have requested your product, say so. Evidence of demand is the strongest argument.
  • Keep it short. 100-150 words for the initial email. The goal is to start a conversation, not close the deal.
Co-Marketing Proposal Structure

When proposing a co-marketing initiative, include:

  1. Audience overlap analysis — Who you both serve and the size of the opportunity
  2. Proposed initiative — Specific campaign: joint webinar, co-authored content, shared case study, cross-email promotion
  3. Responsibilities — Who does what (be prepared to do more than half as the initiating party)
  4. Lead sharing agreement — How captured leads will be distributed
  5. Timeline — Proposed dates and milestones
  6. Success metrics — How you will measure results (leads generated, registrations, content downloads)
Show full SKILL.md (575 more words)Show less
Integration Pitch Framework

When proposing a product integration:

  1. User demand signal — "X% of our users also use your product" or "We get asked about this integration Y times per month"
  2. Technical feasibility — "Your API supports this and we have built similar integrations with Z"
  3. User benefit — The specific workflow that becomes possible or better
  4. Your investment — "We will build and maintain the integration on our side"
  5. Their investment — "We would need API access and a technical contact for questions"
  6. Distribution — "We will promote this to our X users and list on your marketplace"
Warm Introduction Strategy

Cold partnership emails work, but warm intros convert 3-5x better. Before going cold, check for shared investors, advisor connections, shared customers who could intro, or conference overlap. Engage with their content on LinkedIn before reaching out.

Follow-Up Sequence for Partnership Outreach
TouchTimingAngle
1Day 0Primary partnership pitch with mutual benefit
2Day 5Share a specific data point or customer anecdote that reinforces the opportunity
3Day 12Reference a market trend or competitor partnership that creates urgency
4Day 20Brief breakup: "Want to respect your time — should I circle back next quarter?"
What to Avoid
  • Vague partnership pitches. "We should explore synergies" gets deleted. Be specific about the opportunity.
  • One-sided proposals. If your proposal mostly benefits you, the partner will see through it.
  • Reaching out too early. If you have no traction, users, or distribution, you have nothing to bring to the table. Build first.
  • Going to the wrong person. BD and partnership teams exist at most companies. Do not pitch the CEO of a 500-person company on a co-marketing webinar.
  • Over-engineering the first conversation. The goal of the email is a 20-minute call. Do not send a 10-page partnership proposal as the first touch.
  • Ignoring stage mismatch. A 5-person startup proposing a "strategic alliance" with a public company will not be taken seriously. Match your ask to your stage.
  • cold-outreach — use for the underlying outreach mechanics (email structure, subject lines, follow-up cadence)
  • proposal-generation — use when the partnership conversation advances to a formal proposal or agreement

Examples

Example prompt: "I want to reach out to Segment about building an integration. We are a customer data quality tool with 800 users. About 40% of our users also use Segment."

Good outreach email output:

Subject: segment integration — 320 shared users

Hi [Name],

We build [Product], a data quality tool used by about 800 companies. Roughly 40% of our users also use Segment, and "Segment integration" is our most-requested feature.

The integration would let shared customers automatically validate and clean data flowing through Segment before it hits downstream destinations — fewer bad records in warehouses and analytics tools.

We would build and maintain the integration on our end. We would need access to your partner API docs and a technical point of contact for a few questions.

Worth a 20-minute call to see if this makes sense?

Good partner evaluation output snippet:

Partner Fit: Segment
  • Audience overlap: 5/5 — 40% of our users are Segment customers
  • Complementary value: 5/5 — Data quality is a known pain point for Segment users; our products are better together
  • Stage alignment: 3/5 — They are much larger, but they have an active partner/integration program
  • Distribution leverage: 4/5 — Their marketplace and integrations page would give us significant visibility
  • Strategic timing: 4/5 — They recently launched their new Protocols product, which aligns with data quality
  • Total: 21/25 — Strong partnership opportunity

© shawnpang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/partnership-outreach of shawnpang/startup-founder-skills.

Open the folder on GitHubat commit 4ad31b4

Compare with similar skills

Partnership Outreach next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Partnership Outreach compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Partnership Outreach this skillshawnpang/startup-founder-skills343—~2.7kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19540 repos~3.2kAutomated safety check: PassMIT
Audit Onboarding Proposalhoangnb24/repository-harness1.2k—~4kAutomated safety check: PassMIT
No Negative EchoLB623/no-negative-echo900—~965Automated safety check: PassMIT
GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude11k—~3kAutomated safety check: NotesMIT
Architectural ProposalsFritzAndFriends/SharpSite1452 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed
  • Audit Onboarding Proposal

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $audit-onboarding-proposal.

    1.2k GitHub stars~4k tokensUpdated 7 days ago
    Sales & SupportAuto-check passed
  • No Negative Echo

    LB623/no-negative-echo

    Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.

    900 GitHub stars~965 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • GEO Service Proposal Generator

    zubair-trabzada/geo-seo-claude

    Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.

    11k GitHub stars~3k tokensUpdated yesterday
    Sales & SupportAuto-check: notes
  • Architectural Proposals

    FritzAndFriends/SharpSite

    How to write comprehensive architectural proposals that drive alignment before code is written

    145 GitHub starsUsed in 2 repos~1.6k tokens
    Sales & SupportAuto-check passed
  • Counter Proposal Generator

    zubair-trabzada/ai-legal-claude

    Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

    1.8k GitHub stars~2.4k tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed

More from shawnpang/startup-founder-skills

All 50 skills in this repo
  • Accelerator Application

    shawnpang/startup-founder-skills

    When the user wants to apply to startup accelerators, incubators, or fellowship programs.

    343 GitHub stars~2.7k tokensUpdated 6 mo ago
    Auto-check passed
  • Architecture Design

    shawnpang/startup-founder-skills

    When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis.

    343 GitHub stars~2.1k tokensUpdated 6 mo ago
    Auto-check passed
  • Board Update

    shawnpang/startup-founder-skills

    When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.

    343 GitHub stars~2.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Churn Analysis

    shawnpang/startup-founder-skills

    When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.

    343 GitHub stars~2.3k tokensUpdated 6 mo ago
    Auto-check passed
  • Cicd Setup

    shawnpang/startup-founder-skills

    When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".

    343 GitHub stars~1.7k tokensUpdated 6 mo ago
    Auto-check passed
  • Code Review

    shawnpang/startup-founder-skills

    When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".

    343 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Partnership Outreach

What does Partnership Outreach do?

When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Partnership Outreach is an agent skill from shawnpang/startup-founder-skills. When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals.

When should I use Partnership Outreach?

Partnership Outreach fits situations like: mentions partnerships; business development; integration proposals; channel partnerships.

How do I install Partnership Outreach in Claude Code?

Run `npx skills add shawnpang/startup-founder-skills --skill partnership-outreach -a claude-code`. Or copy the skill folder (skills/partnership-outreach in shawnpang/startup-founder-skills) into .claude/skills/partnership-outreach in your project. Claude Code loads it when a task matches its description.

How do I install Partnership Outreach in Codex?

Run `npx skills add shawnpang/startup-founder-skills --skill partnership-outreach -a codex`. Or copy the skill folder (skills/partnership-outreach in shawnpang/startup-founder-skills) into .agents/skills/partnership-outreach in your project. Codex loads it when a task matches its description.

Can I use Partnership Outreach in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shawnpang/startup-founder-skills --skill partnership-outreach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/partnership-outreach, .gemini/skills/partnership-outreach, .github/skills/partnership-outreach and .opencode/skills/partnership-outreach in your project.

What does Partnership Outreach need to run?

SKILL.md names no scripts, command-line tools or credentials: Partnership Outreach is instructions for the agent only.

Does Partnership Outreach access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Partnership Outreach safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Partnership Outreach use?

Partnership Outreach is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Partnership Outreach use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Partnership Outreach?

Skills that share tags, products or a category with Partnership Outreach: Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars), No Negative Echo (LB623/no-negative-echo, 900 stars) and GEO Service Proposal Generator (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Partnership Outreach?

shawnpang (a GitHub user) maintains it in shawnpang/startup-founder-skills, which has 343 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on March 16, 2026.

Source: shawnpang/startup-founder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.