Integration Partners Skill: What It Does and How to Install It

Helps a SaaS company choose which technology partners to integrate with and how deep to go with each.

Installs: 9.7K; on skills.sh
Stars: 9; on GitHub
Files: 3; besides SKILL.md
Updated: Nov 2026; last repo commit

integration-partnership-strategy makes Claude act as a technology-partnerships strategist who treats partners as one portfolio. It works in six steps: a demand-data scorecard, a referral-to-OEM depth ladder, joint-roadmap governance, certification joins with renewals budgeted, pipeline attribution, and where the function sits in the org.

It loads when you mention integration partners, ISV alliances, partner tiers, certification programs or partner-pipeline attribution. It asks seven interview questions and brainstorms before committing. It is strategy only and bundles two reference files and no scripts.

Good for

Partnerships leads picking which integrations to go deep on
Teams deciding whether to certify on a big platform
Finance-minded partner managers rebuilding attribution

Install integration-partnership-strategy

Claude Code

Copy this prompt.

Install the integration-partnership-strategy skill in Claude Code. Run this command:

/plugin marketplace add samber/developer-platform-skills
/plugin install developer-platform-skills@developer-platform-skills

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

The README installs every skill in the repo (61 skills/*/SKILL.md in the git tree), because skills here reference each other. integration-partnership-strategy is one of them. Pick one route, not both.

From the project README. Source.

What's in the skill

When it loads

Select which technology partners a B2B SaaS vendor integrates with and how deep each partnership goes - demand-data partner prioritization (deal-attached revenue, retention lift, competitive necessity), the referral-to-OEM depth ladder with graduation gates, joint-roadmap and co-build governance, certification-program joins with budgeted renewals, sourced-vs-influenced pipeline attribution, and where the technology-partnerships function reports. Use whenever the user mentions integration partners, ISV alliances, technology partnerships, partner tiers, certification programs, or partner-pipeline attribution - even if they never say "partnership strategy". Strategy layer only. Do NOT use for ETL-platform listings - use samber/developer-platform-skills@etl-connector-strategy instead.

Sections in SKILL.md

Interview
Brainstorm before committing
Workflow
1. Prioritize partners with data, not relationships
2. Place each partner on the depth ladder
3. Govern the deep rungs like a product
4. Join certifications with renewals budgeted
5. Wire attribution before scaling
6. Place the function in the org
Failure modes
Measurement
Invocation examples
References

Key facts

Author: Samuel Berthe
Repo: samber/developer-platform-skills, which holds 61 skills
License: MIT (LICENSE, README, plugin.json and SKILL.md all say MIT)
Version in SKILL.md: 1.0.5
Installs on skills.sh: 9,690 (Nov 2, 2026)
GitHub stars (repo): 9 (Nov 2, 2026)
Last commit (repo): Nov 1, 2026
What installs: 4 files including SKILL.md: 2 reference files and evals/evals.json; no scripts
Needs: The other skills in the repo; the README says to install all of them
Works in: Claude.ai, Claude Code, Codex, Cursor, Gemini CLI, and tools that read skills.sh installs

What it includes

Asks seven questions, then brainstorms before committing.
Try: “Salesforce is pushing us to certify on their platform. Should we join, and what does it really cost us per year?”
Interview
Builds a scorecard from deal-attached revenue, retention lift and competitive necessity.
1. Prioritize partners with data
Places each partner on a referral-to-OEM ladder with graduation gates.
2. Place partners on the depth ladder
Sets joint-roadmap and co-build governance.
3. Govern the deep rungs
Decides certification joins with renewals budgeted.
4. Join certifications
Sets up sourced versus influenced pipeline attribution before the program scales.
5. Wire attribution
Decides where technology partnerships reports.
6. Place the function in the org

From the official docs

Permissions

Low risk

This skill writes design advice and bundles no scripts, so the main thing to watch is where your agent saves notes.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It may save notes to developer-platform-context.md
SKILL.md says that when your agent keeps memory in a file, it should consider using this file name. Our advice: keep it out of commits if it holds company plans. github.com

Technical details

Scopes	Asks you interview questions and writes a design document from your answers

Questions

How do I install integration-partnership-strategy?

Use the install box at the top of this page. The README says to install every skill in samber/developer-platform-skills, not one, because the skills hand work to each other. Pick one route per agent.

Does integration-partnership-strategy work in Claude, Codex and Cursor?

The README documents install routes for Claude.ai (plugin marketplace), Claude Code, Codex, Cursor, Gemini CLI and the skills.sh CLI. The install box lists each one.

What does it ask me before it designs anything?

SKILL.md lists seven questions to ask first, and the answers change the later steps. Have your current setup and constraints ready.

Does it run scripts or need an API key?

It bundles no scripts. The folder holds SKILL.md, reference Markdown files and an evals file, and the skill works by asking you questions and writing advice.

Is integration-partnership-strategy safe to install?

It bundles no scripts, so installing it adds instructions and reference files rather than programs. SKILL.md also suggests that, if your agent keeps notes in a file, it uses developer-platform-context.md. Our advice: keep that file out of public commits if it holds company plans, and check any figures the skill cites against their sources before quoting them to customers.

Is this for ETL-platform listings?

No. SKILL.md is strategy only and points ETL-platform listings to etl-connector-strategy.

Information

updated Nov 2, 2026

Repository: samber/developer-platform-skills
Folder: skills/integration-partnership-strategy

samber/developer-platform-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2

samber/developer-platform-skills README · github.com
integration-partnership-strategy SKILL.md · github.com