partnership-proposal

Build a partnership proposal that defines shared objective, audience or customer value, scope, contributions, economics, responsibilities, success measures, governance, risks, and next-step validation.

Jump to install

Repository: Dadmin88/hermes-agency
Last source activity: August 16, 2026 at 06:25
Detected SKILL.md language: English
Stars: 8
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Dadmin88/hermes-agency --skill partnership-proposal

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Partnership Proposal

Use when a qualified potential partnership needs a concrete structure for evaluation.

Procedure

State the shared problem or opportunity and why the two organizations together can create value neither side captures as effectively alone.

Define target customers or members, proposed experience, scope, exclusions, and the customer journey across both organizations.

Specify each party's contributions: product, distribution, content, data, engineering, support, brand, funding, operations, or other resources.

Define commercial terms or economic model at the level appropriate for proposal stage and identify assumptions requiring finance or legal review.

Map ownership, integration or operational dependencies, support, communications, data handling, security, and escalation responsibilities.

Define measurable success, reporting cadence, pilot or launch stages, and conditions for expansion, change, or exit.

Surface risks, conflicts of interest, brand or customer experience concerns, and dependencies before they become negotiation surprises.

End with decisions required from each side and a practical path to pilot, diligence, or formal agreement.

Decision rules

A partnership proposal should make mutual value and reciprocal contribution explicit.

Do not promise legal, security, data, or technical commitments before their owners review them.

Pilot scope can reduce uncertainty before long-term commitment.

Customer experience should not disappear behind partner economics.

Quality gate

The proposal is decision-ready when mutual value, scope, contributions, ownership, economics, customer experience, risks, success measures, and next decisions are clear enough for both sides to evaluate the same collaboration rather than different imagined versions.