Partner Onboarding Skill: What It Does and How to Install It
Helps a platform design the journey a partner developer takes from signup to their first submitted app.
- Installs
- 9.7K
- on skills.sh
- Stars
- 9
- on GitHub
- Files
- 3
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
partner-app-onboarding makes Claude act as a platform-program designer for partner developers. It works in seven steps: map the journey stages, choose the entry gate, design sandbox provisioning, set the education and certification posture, build a support-channel ladder, sequence commercial decisions late, and instrument the funnel.
It loads when you mention partner developer onboarding, a developer program, application-gated versus self-service registration, partner sandbox tenancy or time to first submitted app. It asks nine interview questions. It is journey design only and bundles two reference files and no scripts.
Good for
- Platform teams launching a developer program
- Partner managers whose signups never submit an app
- Leads choosing application-reviewed versus self-service registration
Install partner-app-onboarding
Claude Code
- 1
Copy this prompt.
Install the partner-app-onboarding 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. partner-app-onboarding is one of them. Pick one route, not both.
From the project README. Source.
What's in the skill
When it loads
Design the partner-developer onboarding journey on a B2B SaaS platform - from partner signup through dev-account and sandbox provisioning, docs, education and certification posture, and support channels, to the first submitted app. Use whenever the user mentions partner developer onboarding, developer program entry, self-service vs application-gated registration, sandbox tenancy for partners, certification gating submission, partner support channels, or time-to-first-submitted-app - even if they never say "onboarding". Journey design only. Do NOT use for review-gate mechanics (samber/developer-platform-skills@app-marketplace-review) or sandbox isolation architecture (samber/developer-platform-skills@api-test-mode-design).
Sections in SKILL.md
- Interview
- Workflow
- 1. Map the journey
- 2. Entry gate
- 3. Provisioning
- 4. Education and certification posture
- 5. Support channels
- 6. Sequence commercial decisions late
- 7. Instrument the funnel
- Failure modes
- Invocation examples
- References
Key facts
- Author
- Samuel Berthe
- Version in SKILL.md
- 1.0.2
- Installs on skills.sh
- 9,683 (Nov 2, 2026)
- GitHub stars (repo)
- 9 (Nov 2, 2026)
- Last commit (repo)
- Nov 1, 2026
What it includes
Asks nine questions, validating each choice before the next step.
Try: “Partners sign up but never submit anything. Audit our onboarding: where are they stalling and what do we fix first?”
InterviewPicks a stage model for the journey.
1. Map the journeyChooses the entry gate.
2. Entry gateDesigns sandbox tenancy and credentials.
3. ProvisioningSets the education and certification posture.
4. Education and certificationBuilds the support-channel ladder.
5. Support channelsSequences commercial decisions late in the journey.
6. Commercial decisions lateSets funnel checkpoints and metrics.
7. Instrument the funnel
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 |
|
|---|
Questions
How do I install partner-app-onboarding?
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 partner-app-onboarding 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 nine 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 partner-app-onboarding 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.
Where do review rules and sandbox design go?
SKILL.md says not to use this for review-gate mechanics, which belong to app-marketplace-review, or sandbox isolation architecture, which belongs to api-test-mode-design.
Information
updated Nov 2, 2026
- Repository
- samber/developer-platform-skills
- Folder
skills/partner-app-onboarding
Sources
Docs, issue trackers and discussions this page is built from.
Show all 2Hide
- samber/developer-platform-skills README · github.com
- partner-app-onboarding SKILL.md · github.com