Marketing Os
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Write a B2B partnership proposal or business case. An agent skill from mohitagw15856/pm-claude-skills.
Install Partnership Proposal
$ npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills partnership-proposal --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/partnership-proposal .claude/skills/partnership-proposal && rm -rf skills-srcUse ~/.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/
Install the "partnership-proposal" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposal into .claude/skills/partnership-proposal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnership-proposal", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposalType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills partnership-proposal --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/partnership-proposal .agents/skills/partnership-proposal && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "partnership-proposal" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposal into .agents/skills/partnership-proposal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnership-proposal", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills partnership-proposal --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/partnership-proposal .cursor/skills/partnership-proposal && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "partnership-proposal" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposal into .cursor/skills/partnership-proposal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnership-proposal", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/partnership-proposal--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills partnership-proposal --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/partnership-proposal .gemini/skills/partnership-proposal && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "partnership-proposal" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposal into .gemini/skills/partnership-proposal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnership-proposal", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills partnership-proposalInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/partnership-proposal .github/skills/partnership-proposal && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "partnership-proposal" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposal into .github/skills/partnership-proposal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnership-proposal", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills partnership-proposal --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/partnership-proposal .opencode/skills/partnership-proposal && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "partnership-proposal" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/partnership-proposal into .opencode/skills/partnership-proposal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "partnership-proposal", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
partnership-proposal- GitHub stars
- 1.4k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,387 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a B2B partnership proposal or business case. An agent skill from mohitagw15856/pm-claude-skills.
- Works in 9 steps: The Opportunity → What We're Proposing → Value Proposition — What Each Party Gets → …
- Asked to write a partnership proposal
- SKILL.md covers Required Inputs, Output Structure, Executive Summary and 1. The Opportunity, plus 11 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Partnership Proposal is an agent skill from mohitagw15856/pm-claude-skills. Write a B2B partnership proposal or business case. Use when asked to write a partnership proposal, draft a partnership brief, structure a co-marketing proposal, or create a business case for a strategic partnership. Produces a structured proposal with value proposition, partnership model, commercial terms, and mutual commitments.
Its SKILL.md is about 2.9k 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 Marketing & SEO, covering Positioning and messaging. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a partnership proposal
- Draft a partnership brief
- Structure a co-marketing proposal
- Create a business case for a strategic partnership
Example prompts
- “/partnership-proposal”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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 Proposal loads about 2.9k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,387 words of instructions outside code blocks.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,387 words, ~2,870 tokens.
Download SKILL.mdSave it as
.claude/skills/partnership-proposal/SKILL.md (or your agent's skills folder).- name
- partnership-proposal
- description
- Write a B2B partnership proposal or business case. Use when asked to write a partnership proposal, draft a partnership brief, structure a co-marketing proposal, or create a business case for a strategic partnership. Produces a structured proposal with value proposition, partnership model, commercial terms, and mutual commitments.
Partnership Proposal Skill
This skill produces a complete B2B partnership proposal covering the partnership rationale, mutual value, partnership model, commercial terms, governance, and a joint go-to-market plan. Output is ready to share with a prospective partner or use as the basis for a business case to internal stakeholders.
Required Inputs
Ask the user for these if not provided:
- Your company — name, what you do, and the audience you serve
- Prospective partner — name, what they do, and their audience
- Partnership type — technology integration / co-marketing / reseller / referral / strategic alliance / OEM
- Partnership goal — what does each party get? (new customers / revenue / product capability / market reach)
- Proposed commercial model — revenue share, referral fee, licensing, co-investment?
- Urgency or context — is there a specific event, product launch, or competitive reason for this partnership?
Output Structure
Partnership Proposal: [Your Company] × [Partner Company]
Prepared by: [Name, Role at Your Company] Date: [Date] Partnership type: [Technology / Co-marketing / Reseller / Referral / Strategic Alliance] Proposal status: [Initial proposal / For negotiation / Final]
Executive Summary
[3–5 sentences. Answer: what are we proposing, why now, and what does each party stand to gain? Write this so a busy executive can understand the proposal in 60 seconds without reading further.]
Headline value for [Partner]:
[One sentence — the most compelling thing this partnership does for them]
Headline value for [Your Company]:
[One sentence — the most compelling thing this partnership does for you]
1. The Opportunity
Market context: [Why does this partnership make sense now? What's happening in the market that creates a window for this to work?]
Shared customer: [Describe the customer both organisations serve — the overlap that makes this logical. Include size of the shared addressable market if you have it.]
Problem neither of us solves alone: [What can't either party do for the shared customer independently that the partnership would enable?]
2. What We're Proposing
Partnership model:
| Element | Description |
|---|---|
| Type | [Technology integration / Co-marketing / Reseller / Referral / OEM] |
| Scope | [What specifically are we partnering on? — product features, joint campaigns, distribution, etc.] |
| Exclusivity | [Exclusive in [region/segment] / Non-exclusive / Right of first refusal] |
| Duration | [Initial term — e.g. 12 months, renewable] |
| Geographic scope | [UK / EMEA / Global / Specific markets] |
What this looks like in practice:
[3–5 bullet points describing what the partnership actually means day-to-day. Make it concrete and operational — not abstract. e.g.:]
- [Our product will natively integrate with [Partner's product] — the integration will be live in [timeframe]]
- [We will co-market to each other's customer bases — joint webinar, co-authored content, shared newsletter placement]
- [Each company will train a dedicated partnership contact who manages the relationship]
- [[Partner] will list [Your product] in their marketplace / app directory / referral programme]
3. Value Proposition — What Each Party Gets
For [Partner]
| Value | Evidence / Basis |
|---|---|
| [New customer reach] | [e.g. Access to [Your Company]'s [X,000] [role] customers — [X%] of whom have expressed interest in [Partner's category]] |
| [Product capability] | [e.g. [Partner]'s product gains [capability] that [X%] of their customers have requested — based on [source]] |
| [Revenue opportunity] | [e.g. Estimated [£/$/€ X] in referral revenue in Year 1 based on [X%] conversion from shared pipeline] |
| [Market differentiation] | [e.g. The integration creates a meaningful competitive moat vs [Competitor] who lacks this capability] |
For [Your Company]
| Value | Evidence / Basis |
|---|---|
| [Distribution] | [e.g. Access to [Partner]'s [X,000] customers in [segment] — a segment where we currently have [X] customers] |
| [Credibility] | [e.g. Association with [Partner]'s brand accelerates enterprise sales cycles — [Partner] is trusted by [X] of the Fortune 500] |
| [Revenue] | [e.g. Target [X] referral customers in Year 1 at average ACV of [£X] = [£X ARR]] |
| [Product] | [e.g. [Partner]'s data / capability enhances [specific part of our product] — improving [user outcome]] |
4. Commercial Model
Proposed commercial terms:
| Term | Proposal | Notes |
|---|---|---|
| Revenue share | [e.g. [X%] of ARR from customers referred by [Partner]] | [Standard in this category: [X–Y%] range] |
| Referral fee | [e.g. £[X] per qualified lead that converts] | [Or: flat fee per introduction vs % of closed deal] |
| Licensing / access | [e.g. [Partner] provides API access at no cost in exchange for integration and co-marketing] | [...] |
| Co-marketing investment | [e.g. Each party commits [£X] to joint marketing activities per quarter] | [...] |
| Minimum commitment | [e.g. [X] qualified referrals per quarter / [£X] GMV per year] | [Optional — only if there's a meaningful minimum that makes sense] |
Payment terms: [Monthly / Quarterly in arrears / Annual true-up]
What we're not proposing: [Be explicit about what's off the table — e.g. equity / exclusivity in all markets / upfront payment]
5. Joint Go-to-Market Plan
Phase 1: Foundation (Months 1–2)
| Activity | Owner | Timeline |
|---|---|---|
| Technical integration scoped and resourced | [Engineering at both companies] | [Month 1] |
| Partnership launch announcement drafted | [Marketing at both companies] | [Month 1] |
| Joint customer case study identified | [CSM at both companies] | [Month 2] |
| Partner enablement — each team trained on the other's product | [Partnership lead, both sides] | [Month 2] |
Phase 2: Launch (Month 3)
| Activity | Owner | Timeline |
|---|---|---|
| Integration live in both products / marketplace | [Engineering] | [Month 3] |
| Joint press release / blog post / email announcement | [Marketing] | [Month 3] |
| First joint webinar | [Both companies] | [Month 3] |
| First joint pipeline reviewed | [Partnership leads] | [Month 3] |
Phase 3: Scale (Months 4–12)
| Activity | Owner | Cadence |
|---|---|---|
| Co-sell on named accounts | [AE at both companies] | [Monthly] |
| Joint content (blog, webinar, case study) | [Marketing] | [Quarterly] |
| Pipeline and revenue review | [Partnership leads] | [Monthly] |
| Partnership QBR | [VP level, both companies] | [Quarterly] |
Show full SKILL.md (545 more words)Show less
6. Success Metrics
How we'll know the partnership is working:
| Metric | Year 1 target | Measurement |
|---|---|---|
| Customers referred (each direction) | [X] | [CRM tracking — tagged as partner-sourced] |
| Revenue from partnership | [£/$/€ X ARR] | [CRM + finance reporting] |
| Integration adoption | [X% of mutual customers using integration] | [Product analytics] |
| Customer satisfaction with integration | [NPS ≥ X] | [Post-integration survey] |
| Joint pipeline generated | [£X] | [Quarterly pipeline review] |
Review cadence: Monthly partnership lead check-in + Quarterly business review at VP level
7. Governance & Operations
Partnership contacts:
| Role | [Your Company] | [Partner] |
|---|---|---|
| Partnership lead (day-to-day) | [Name, email] | [TBC] |
| Executive sponsor | [Name, title] | [TBC] |
| Technical lead | [Name] | [TBC] |
| Marketing lead | [Name] | [TBC] |
Decision-making:
- Day-to-day partnership operations: partnership leads
- Commercial term changes: VP-level approval from both parties
- Partnership termination: CEO/MD sign-off + [X days] written notice
Legal framework:
- Partnership agreement / MOU to be drafted by [Company]'s legal team
- Data processing agreement (if personal data is shared)
- NDAs: [already in place / to be signed before detailed discussions]
- IP ownership: [Clarify who owns jointly developed materials, integrations, content]
8. Risks & Mitigations
| Risk | Likelihood | Mitigation |
|---|---|---|
| Partnership champion leaves [Partner] | M | Ensure VP-level sponsorship; build multiple relationships |
| Integration takes longer than planned | M | Scope technical work in Phase 1; set realistic launch commitment |
| Low adoption of the integration | M | Include in onboarding for both products; co-market to existing customers not just new |
| Partner signs with our competitor | L | Discuss exclusivity options; prioritise quick launch to create switching costs |
| Commercial model becomes imbalanced | L | Quarterly review with clear exit terms if targets are consistently missed |
9. Proposed Next Steps
| # | Action | Owner | By when |
|---|---|---|---|
| 1 | [Partner] reviews this proposal and provides feedback | [[Partner name]] | [Date] |
| 2 | Both parties sign NDA (if not already in place) | [Legal, both sides] | [Before next meeting] |
| 3 | Technical discovery call — assess integration feasibility | [Engineering leads] | [Date] |
| 4 | Commercial terms negotiation | [Partnership leads / VP] | [Date] |
| 5 | MOU / partnership agreement drafted and signed | [Legal] | [Date] |
| 6 | Integration and launch planning begins | [Both teams] | [Date] |
Quality Checks
- Value proposition for the partner is written from their perspective — not yours
- Commercial model includes specific numbers, not just structure
- "What we're not proposing" section prevents misaligned expectations
- Go-to-market plan has named owners and dates, not "TBD"
- Success metrics are agreed bilaterally — not set unilaterally
- Risks section includes the most uncomfortable risk (partner signs with a competitor)
Example Trigger Phrases
- "Write a partnership proposal for [Company] to partner with [Partner]"
- "Draft a co-marketing partnership brief between us and [Partner]"
- "Create a reseller partnership proposal for [Company]"
- "Build the business case for a strategic partnership with [Partner]"
- "Structure a technology integration partnership proposal"
Anti-Patterns
- Do not write the value proposition from your own perspective — the "For Partner" section must be written from the partner's point of view, in the language of their goals and their customers
- Do not leave commercial terms as structure without numbers — a proposal that says "revenue share" without stating the percentage is not a proposal, it is a conversation opener
- Do not omit the "What we're not proposing" section — leaving unstated assumptions creates misaligned expectations that derail negotiations later
- Do not set success metrics unilaterally — metrics that only your company controls or cares about will not earn partner commitment
- Do not write a go-to-market plan with "TBD" owners — every activity must have a named owner on at least one side before the proposal goes out
© mohitagw15856, 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-proposal of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Partnership Proposal 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Partnership Proposal this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Positioningferdinandobons/startup-skill | 1.2k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Stanley Druckenmiller Investmenttradermonty/claude-trading-skills | 3k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| B2b Playbookweilun88313/B2B-Playbook | 203 | — | ~3.1k | Automated safety check: Pass | Proprietary |
Similar skills
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Startup Positioning
ferdinandobons/startup-skill
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test.
Stanley Druckenmiller Investment
tradermonty/claude-trading-skills
Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…
B2b Playbook
weilun88313/B2B-Playbook
Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance.
Research Brand
onvoyage-ai/gtm-engineer-skills
Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Partnership Proposal
What does Partnership Proposal do?
Write a B2B partnership proposal or business case. An agent skill from mohitagw15856/pm-claude-skills. Partnership Proposal is an agent skill from mohitagw15856/pm-claude-skills. Write a B2B partnership proposal or business case.
When should I use Partnership Proposal?
Partnership Proposal fits situations like: asked to write a partnership proposal; draft a partnership brief; structure a co-marketing proposal; create a business case for a strategic partnership.
How do I install Partnership Proposal in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a claude-code`. Or copy the skill folder (skills/partnership-proposal in mohitagw15856/pm-claude-skills) into .claude/skills/partnership-proposal in your project. Claude Code loads it when a task matches its description.
How do I install Partnership Proposal in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill partnership-proposal -a codex`. Or copy the skill folder (skills/partnership-proposal in mohitagw15856/pm-claude-skills) into .agents/skills/partnership-proposal in your project. Codex loads it when a task matches its description.
Can I use Partnership Proposal 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 mohitagw15856/pm-claude-skills --skill partnership-proposal -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-proposal, .gemini/skills/partnership-proposal, .github/skills/partnership-proposal and .opencode/skills/partnership-proposal in your project.
What does Partnership Proposal need to run?
SKILL.md names no scripts, command-line tools or credentials: Partnership Proposal is instructions for the agent only.
Does Partnership Proposal 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 Proposal 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 Proposal use?
Partnership Proposal 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 Proposal use?
About 2.9k 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 Proposal?
Skills that share tags, products or a category with Partnership Proposal: Marketing Os (Yuzzyuk/marketing-os, 540 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Positioning (ferdinandobons/startup-skill, 1.2k stars) and Stanley Druckenmiller Investment (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Partnership Proposal?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.