mcpField
P
partner-risk-due-diligence-review

partner-risk-due-diligence-review

github.com/sylphxaiOther140 installsUpdated today
Repository

About partner-risk-due-diligence-review

A skill for teams assessing partner relationships across data, legal, security, brand, and operational risks. It turns the review into a plan with owners, decision gates, metrics, and exit paths.

Key features

  1. 01Classifies partner relationship types
  2. 02Maps data and dependency risks
  3. 03Defines review evidence and contract terms
  4. 04Creates monitoring and escalation plans
  5. 05Produces decision tables and checklists

Use cases

  1. 01Reviewing a proposed data-sharing integration
  2. 02Assessing reseller or marketplace relationships
  3. 03Planning partner offboarding and customer communication

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill partner-risk-due-diligence-review

After installing, type/partner-risk-due-diligence-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/partner-risk-due-diligence-patterns.md

Details

From the project README

Partner Risk Due Diligence Review

Use this skill to convert a partner risk due diligence, integrations, data sharing, brand fit, incentives, legal/privacy/security exposure, and exit plans question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify partner type, user value, data exchanged, dependency depth, commercial terms, brand exposure, support impact, and exit cost.
  2. Read references/partner-risk-due-diligence-patterns.md.
  3. Classify partner motion: integration, reseller, agency, affiliate, marketplace supply, creator, data partner, AI provider, or co-marketing.
  4. Define risk review, evidence, data boundaries, contract terms, support model, monitoring, incentives, escalation, and termination/exit path.
  5. Produce partner due diligence plan, state machine, decision table, event schema, checklist, and ongoing review cadence.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not integrate or co-market before data-sharing, support, brand, legal, privacy, and security responsibilities are explicit.
  • Do not let revenue upside hide dependency risk, customer confusion, or misaligned incentives.
  • Do not share customer data or leads without consent, minimization, and legal basis.
  • Do not launch a partner dependency without degradation, offboarding, and customer communication paths.

Output format

Partner risk context:
Partner type / data / dependency / brand exposure:

Due diligence plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Evidence, terms, and monitoring:
- <item> -> <policy, metric, edge case, support note>

Exit and escalation policy:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported