Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Analyzing Key Person Event Provisions

ASecurity

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.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
businessgodocumentation

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill analyzing-key-person-event-provisions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyzing Key Person Event Provisions?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Analyzing Key Person Event Provisions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-analyzing-key-person-event-provisions/badge)](https://www.skillsdirectory.com/skills/lev-os-analyzing-key-person-event-provisions)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: analyzing-key-person-event-provisions
description: 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.
tags:
  - analysis
  - fund-formation-and-structuring
  - risk
metadata:
  author: casemark
  practice_areas:
    - Fund Formation
    - Fund Structuring
    - Partnership Law
  document_types:
    - Analysis Report
  skill_modes:
    - Analysis
---
# Analyzing Key Person Event Provisions

## When To Use

- Reviewing or drafting key person clauses in LPA, side letter, or GP agreement contexts
- Assessing management concentration risk during fund due diligence
- Evaluating whether a proposed GP personnel change triggers a key person event
- Structuring departure protections or cure mechanics for a new fund formation
- Advising LPs on the adequacy of key person protections in existing fund documentation

## Inputs To Gather

- **Partnership agreement (LPA)** — full executed version including all amendments and side letters modifying key person provisions
- **Key person list** — named individuals designated as key persons, including any tiered classifications (e.g., "Category A" vs. "Category B" key persons)
- **Devotion-of-time requirements** — minimum time commitment thresholds (e.g., "substantially all business time," specific percentage thresholds, or exclusivity requirements)
- **Trigger event definitions** — death, disability, departure, cause termination, bankruptcy, regulatory disqualification, or other specified events
- **Current GP personnel status** — whether any key person has departed, reduced involvement, or is subject to pending investigation or health issues
- **Side letter provisions** — any LP-specific key person modifications, additional named persons, or enhanced trigger rights
- **LPAC composition and role** — whether the LP advisory committee has authority over cure, waiver, or replacement approvals

## Workflow

1. **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.

2. **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).

3. **Analyze consequence mechanics** — Determine the immediate consequence of a key person event:
   - **Investment period suspension** — new investments halted; follow-on investments may or may not be permitted
   - **Investment period termination** — permanent end to new deployment
   - **GP removal right** — LP vote to remove GP triggered
   - **Fund termination right** — LP vote to wind down the fund
   - Note whether consequences are automatic or require LP vote, and the applicable voting threshold (simple majority, supermajority, LPAC approval)

4. **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.

5. **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.

6. **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).

## Output

Produce a structured analysis report containing:

- **Key Person Roster** — table listing each named key person, their classification tier, role, and time commitment requirement
- **Trigger Event Matrix** — grid mapping each key person to each trigger type, noting whether the event applies and any carve-outs
- **Consequence Summary** — description of what happens upon trigger, including whether consequences are automatic or vote-dependent, with applicable thresholds
- **Cure Mechanics** — cure period duration, permissible cure actions, approval requirements for replacements, and reinstatement terms
- **Risk Assessment** — concentration risk rating (high/medium/low), identification of GP-favorable or LP-favorable deviations from market terms, and flagged gaps or ambiguities
- **Side Letter Overlay** — any LP-specific modifications that alter the base key person framework
- **Recommendations** — specific suggested revisions, additional protections, or negotiation points depending on whether the client is GP-side or LP-side

## Quality Checks

- Confirm every named key person in the LPA is accounted for in the roster, including side letter additions
- Verify trigger definitions are quoted or closely paraphrased — do not paraphrase loosely enough to change meaning
- Cross-check cure period lengths against market norms (typically 90–180 days for institutional funds) and flag outliers
- Ensure consequence mechanics distinguish between suspension and termination of the investment period — these have materially different economic impacts
- Confirm voting thresholds are accurately stated, including whether they are measured by commitments, interests, or headcount
- [VERIFY] applicable state partnership law default rules that may fill gaps where the LPA is silent on key person mechanics
- Flag any circular or internally inconsistent provisions (e.g., a cure requiring LPAC approval when the LPAC composition itself depends on the departed key person)

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Solution Architect

Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

192 votes

Akorchak:Venture Assessment

Generate a comprehensive VC investment assessment report for a company

72 votes

Stock Analysis

Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management (create, add, remove assets), crypto analysis (Top 20 by market cap), and periodic performance reports (daily/weekly/monthly/quarterly/yearly). 8 analysis dimensions for stocks, 3 for crypto. Use for stock analysis, portfolio tracking, earnings reactions, or crypto monitoring.

6511 votes

Just Fucking Cancel

Find and cancel unwanted subscriptions by analyzing bank transactions. Detects recurring charges, calculates annual waste, and helps you cancel with direct URLs and browser automation. Use when: 'cancel subscriptions', 'audit subscriptions', 'find recurring charges', 'what am I paying for', 'save money', 'subscription cleanup', 'stop wasting money'. Supports CSV import (Apple Card, Chase, Amex, Citi, Bank of America, Capital One, Mint, Copilot) OR Plaid API for automatic transaction pull. Out...

6511 votes

Telegram Compose

Compose rich, readable Telegram messages using HTML formatting via direct Telegram API. Use when: (1) Sending any Telegram message beyond a simple one-line reply, (2) Creating structured messages with sections, lists, or status updates, (3) Need formatting unavailable via Clawdbot's Markdown conversion (underline, spoilers, expandable blockquotes, user mentions by ID), (4) Sending alerts, reports, summaries, or notifications to Telegram, (5) Want professional, scannable message formatting wit...

6511 votes
View all in business →