skills/capital/analyzing-key-person-event-provisions/SKILL.md
Evaluates key person clause triggers, consequences, and cure mechanics in partnership documentation. Use when analyzing key person provisions, assessing management stability risk, or structuring departure protections.
npx skillsauth add casemark/skills analyzing-key-person-event-provisionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Identify all key person designations — Extract the named individuals and any classification tiers. Note whether the provision uses an "all of" or "any X of Y" trigger structure. Flag if the key person list is static or subject to GP modification.
Map trigger events — Catalog each defined triggering event (death, disability, departure, cause, conviction, regulatory bar, bankruptcy). Assess whether "departure" includes voluntary resignation, involuntary removal, or reduction below a time threshold. Note any carve-outs (e.g., permitted board service, successor fund activity). [VERIFY] whether disability definition cross-references a specific standard (e.g., ADA, insurance policy definition, or number of consecutive days).
Analyze consequence mechanics — Determine the immediate consequence of a key person event:
Evaluate cure and reinstatement provisions — Determine whether the GP has a cure period (typically 60–180 days). Identify what constitutes a valid cure: appointment of a replacement approved by LPAC or LP vote, reinstatement of the departed key person, or other specified remedies. Assess whether the investment period resumes automatically upon cure or requires affirmative LP consent.
Review replacement approval mechanics — Identify who approves replacement key persons (LPAC, LP majority, supermajority). Note whether the GP can propose replacements or whether LPs have nomination rights. Flag any veto rights held by specific anchor LPs via side letters.
Assess practical adequacy — Evaluate concentration risk: a fund with two key persons under an "all of" trigger is more exposed than one with an "any two of four" structure. Consider whether devotion-of-time language is enforceable and monitorable. Flag provisions that are unusually GP-friendly (long cure periods, GP-controlled replacement, no automatic suspension) or LP-friendly (hair-trigger events, no cure, automatic termination).
Produce a structured analysis report containing:
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.