Review an LP's redline of a GP's form side letter against the GP's form, the LPA excerpts, internal side letter policy, placement agreement, and precedent executed letters to produce a negotiation-ready analysis memorandum focused on issue spotting, cross-referencing, and recommended counter-positions.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill analyze-counterparty-markup-of-side-letter --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Analyze Counterparty Markup Of Side Letter?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-analyze-counterparty-markup-of-side-letter)More formats (shields.io, HTML) on the badges page.
---
name: analyze-counterparty-markup-of-side-letter
task_id: funds-asset-management/analyze-counterparty-markup-of-side-letter
description: Review an LP's redline of a GP's form side letter against the GP's form, the LPA excerpts, internal side letter policy, placement agreement, and precedent executed letters to produce a negotiation-ready analysis memorandum focused on issue spotting, cross-referencing, and recommended counter-positions.
activates_for: [planner, solver, checker]
---
# Skill: Analyze Counterparty Markup of Side Letter
## 1. Subject-matter triage (only if applicable)
- Confirm the side letter is the operative document under review and identify the governing source stack before analysis: GP form, LPA excerpts, internal policy, placement/commitment documents, partner instructions, and precedent executed letters.
- Identify whether the counterparty markup is single-LP only or whether it may affect other LPs through MFN or similar election mechanics; if only one LP is in scope, state that expressly.
- Treat the LPA as the controlling baseline for any deviation analysis, then test the markup against internal policy and fundraising commitments.
- If the task includes preparing a memo only, preserve the analysis focus; do not drift into drafting a new side letter unless expressly instructed.
## 2. Failure modes the skill is correcting
- Not explaining most-favored-nation cascade risk, including how a concession to one LP can be elected by other eligible LPs and expand the economic effect beyond the immediate investor.
- Not identifying when a change in preferred-return compounding frequency increases the effective annual economic burden on the fund.
- Not flagging bespoke waterfall mechanics as both operationally difficult and likely inconsistent with uniform distribution provisions in the governing agreement.
- Not cross-referencing the relevant LPA, policy, and placement-document provisions for each deviation.
- Not distinguishing between legal conflict, policy conflict, and market-practice discomfort.
- Not stating the client consequence for each issue, leaving the memo descriptive rather than negotiation-ready.
- Not distinguishing a concession that is limited by commitment tier from one that is broadly electable.
## 3. Legal frameworks / domain conventions that apply
**Source hierarchy and document control**
- The LPA governs fund mechanics unless a side letter validly carves out a permitted deviation.
- Internal side letter policy constrains what the GP may accept even where an LP requests it.
- Placement or commitment documents may limit what the GP represented during fundraising and may inform negotiated position.
**MFN and election mechanics**
- A most-favored-nation clause may allow an LP to elect more favorable provisions granted to others, subject to scope, tier, and election conditions.
- Where a requested concession is within MFN scope, analyze whether other LPs may elect it and whether the concession becomes a fund-wide economic issue.
- Commitment-tier limitations matter; smaller investors may not be entitled to elect concessions reserved for larger commitments.
**Economic terms**
- Changes to compounding frequency, fee timing, or carry thresholds can alter the effective economics even if nominal language appears similar.
- Gross-of-tax clawback formulations can shift post-tax economic risk back to the GP and require careful comparison to market and baseline terms.
- Any concession affecting economics should be tested against the governing fee, distribution, and clawback provisions in the LPA.
**Governance and control**
- Key person, removal, suspension, cure, and consent mechanics must be measured against the governing agreement’s trigger thresholds and approval standards.
- Automatic suspension mechanics should be distinguished from notice-and-vote mechanics and assessed for consistency with the LPA.
**Operational and confidentiality issues**
- Side-letter provisions requiring special reporting, bespoke waterfalls, or nonstandard data handling may create administrative burden and confidentiality risk.
- Public-records provisions for public pension investors should be tested for notice, protective-relief timing, and cost allocation.
- Inadvertent-disclosure protections should be assessed for whether they improperly shift all leakage risk to the GP.
**Policy constraints**
- Any ESG, exclusion, or portfolio-restriction request must be tested against the GP’s policy limits and strategy tolerance.
- A requested exclusion that would materially alter the fund’s investable universe is ordinarily outside a routine side-letter accommodation.
## 4. Analytical scaffolds
1. Read the governing documents in this order: form side letter, internal policy, LPA excerpts, placement/commitment materials, then precedent letters.
2. Build an issue list by provision, not by theme, so each requested change is assessed against the correct controlling source.
3. For each proposed change, identify:
- the exact requested deviation,
- the baseline form position,
- the controlling LPA or policy provision,
- any MFN or election risk,
- the operational or economic consequence to the client.
4. Where the requested provision is economic, state whether the effect is de minimis, material, or fund-wide in relation to the relevant commitment, exposure, or distribution mechanics drawn from the source documents.
5. Where the requested provision is governancesensitive, compare the trigger or threshold to the LPA baseline and explain whether it lowers a protection, expands investor control, or creates a unilateral remedy.
6. Where the request concerns confidentiality or public disclosure, identify the notice window, the protective-relief opportunity, and any cost-shifting or indemnity allocation.
7. Where the request concerns reporting or data access, separate ordinary reporting from bespoke data extraction, and assess whether the request is operationally scalable.
8. When a provision could be elected by others, complete the MFN analysis after identifying all LP-specific concessions.
9. State the downstream consequence for the fund or GP in every issue: economic dilution, administrative burden, disclosure risk, governance dilution, or litigation exposure.
10. Assign each issue a severity level using a consistent ordinal scale defined once at the top of the memo.
11. Close each issue with a recommended counter-position tied to the controlling document and the negotiating objective.
12. If the source documents provide a deadline or notice period, use it; otherwise, anchor timing to the relevant signing, closing, election, or disclosure milestone.
## 5. Vertical / structural / temporal relationships
- The GP’s form side letter is the baseline; the counterparty markup is evaluated as a proposed deviation from that baseline.
- The LPA is senior to the side letter unless a side-letter carve-out is clearly permitted; any conflict should be treated as a negotiation risk and, if accepted, a drafting exception.
- Internal policy should be applied before finalizing the recommended position so the analysis reflects what the GP can actually concede.
- MFN analysis must come after the universe of requested concessions is mapped, because election risk depends on the full set of LP-specific terms.
- Temporal mechanics matter: notice periods, cure periods, election windows, and public-records response windows should be compared as written, not in abstract.
- If a provision changes a continuing process, identify whether the effect is immediate, recurring, or triggered only upon a specified event.
## 6. Output structure conventions
- Produce a negotiation-ready analysis memorandum, not a pure markup or a legal opinion.
- Use an executive summary that states the overall posture, the main economic and governance pressure points, and the recommended negotiation stance.
- Define a severity scale once at the top and apply it uniformly to each issue.
- Organize the body by issue type in conventional memo form, such as economics, governance, operational matters, confidentiality, and document-control conflicts.
- For each issue, include: severity, the requested change, the baseline term, the controlling source reference, MFN or cross-document interaction, practical consequence, and recommended counter-position.
- Cite controlling authority or governing document references by name and section whenever a legal or contractual proposition is stated.
- If the memo discusses multiple provisions or alternative treatments, enumerate the relevant provisions first and analyze each separately rather than collapsing them into one combined treatment.
- End with a Recommended Actions section that uses imperative verbs, identifies the responsible role, and anchors timing to the applicable milestone or deadline.
- Keep the prose concise and negotiation-facing; do not reproduce long verbatim excerpts unless needed for pinpointing the controlling language.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!