# Analyze Counterparty Markup Contract Amendment > Redline deviation analysis of a counterparty-marked contract amendment against the executed baseline agreement and internal contracting policies. Focus on procedural comparison, issue spotting, and documenting how the amendment changes rights, obligations, and risk exposure. - Skill: `finchipaiorg/analyze-counterparty-markup-contract-amendment` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/analyze-counterparty-markup-contract-amendment` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/analyze-counterparty-markup-contract-amendment/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/analyze-counterparty-markup-contract-amendment --- # Skill: Analyze Counterparty Markup of Contract Amendment ## 1. Subject-matter triage - Confirm the operative baseline: the executed master agreement controls unless the amendment clearly replaces or supersedes a provision. - Identify the amendment’s amendment scope before analyzing text: which provisions, schedules, exhibits, or defined terms are actually being changed. - Read the transmittal email, cover note, and any negotiation correspondence together with the redline; treat them as part of the record for materiality and intent. - If more than one provision, term, rate, cap, notice window, or risk allocation is in play, enumerate each item first and analyze each separately rather than collapsing them into a single general assessment. - If only one issue is truly in scope, say so expressly and explain why the rest of the document is unchanged or immaterial. ## 2. Failure modes the skill is correcting - Comparing the markup to a prior draft instead of the executed baseline agreement, which can hide preexisting concessions or settled language. - Treating a clause-level edit as isolated when the real effect depends on linked provisions elsewhere in the amendment, MSA, or policies. - Missing material changes that are described differently in correspondence than in the markup, or vice versa. - Describing edits as stylistic rather than translating them into economic, operational, compliance, or litigation consequences. - Failing to distinguish between a textual cleanup and a change that alters rights, obligations, timing, or risk allocation. - Writing a narrative review that does not classify each deviation by severity and does not end with a concrete response. ## 3. Legal frameworks / domain conventions that apply - Amendments are construed against the operative contract package, including the executed baseline, incorporated schedules, and any policy constraints that govern acceptable deviation. - Liability-allocation clauses should be read as a system: exclusions, carve-outs, caps, baskets, indemnities, and remedy limitations may interact and should not be assessed in isolation. - Performance-credit, rebate, or service-credit mechanics must be reviewed as to both trigger mechanics and any aggregate limitation; either element can change practical enforceability. - Renewal, extension, and termination provisions should be traced through notice mechanics and post-renewal lock-in to determine forward commitment exposure. - Price-adjustment language must be assessed for both formula mechanics and timing, because a small textual change can create a compounding cost shift over the remaining term. - Compliance, audit, reporting, and recordkeeping provisions can alter the practical ability to enforce the contract and should be mapped against internal policy thresholds. - The redline and the cover correspondence together form the negotiation record; understated or omitted changes in the cover note should be flagged as a separate concern. - Any legal conclusion in the report should be tied to the governing contract language, internal policy, or cited authority reflected in the source set; avoid unsupported conclusions. ## 4. Analytical scaffolds - Establish the baseline package: identify the executed agreement, the amendment, the policies, and the correspondence that govern the comparison. - Build an issue inventory by provision, defined term, schedule, and correspondence point; keep each entry discrete and traceable. - For each issue, identify: what changed, where it sits in the agreement stack, whether it narrows or expands obligations, and whether the change is direct or indirect. - For each issue, state the practical magnitude using the source documents’ own scale where available, such as term length, notice period, cap structure, billing cycle, or remaining contractual horizon. - Cross-reference each issue to interacting clauses, schedules, exhibits, policy rules, or correspondence statements that affect the same risk. - Translate the deviation into downstream consequences for the client: economic, operational, compliance, dispute, or transaction-management impact. - Classify the issue by severity using one consistent ordinal scale defined once at the top of the report. - Where the markup changes multiple linked provisions, assess whether the combined effect is greater than the sum of the edits taken alone. - For each substantive textual change in the markup, preserve a plain-text-readable change marker so the deviation remains legible outside of formatting. - For each deviation, include a short rationale that explains why the change matters and what response is recommended. - When a provision is removed, inserted, or substituted, make the change explicit in the analysis rather than relying on styling alone. - Compare the cover correspondence against the markup line by line for omissions, understatement, or side-channel requests that alter the deal economics or risk posture. ## 5. Vertical / structural / temporal relationships - Track how changes propagate across the contract hierarchy: amendment language may override the MSA, but only to the extent expressly stated. - Watch for temporal effects: immediate changes, delayed effectiveness, survival language, renewal mechanics, and post-termination obligations. - If the amendment changes a date, deadline, notice period, or renewal window, map the new timing against the existing contract calendar and any remaining term. - If the amendment alters a cap, threshold, credit, fee, or escalation mechanic, assess the effect over the remaining contractual duration, not just at signature. - If the amendment touches a defined term, determine whether the same term appears elsewhere and whether the change propagates through the document set. - If the correspondence suggests a negotiated compromise, verify whether the redline actually implements that compromise or shifts more broadly. ## 6. Output structure conventions - Start with a short executive summary that states the overall risk posture and the main deviations in plain English. - Define the severity scale once at the top and use it uniformly for every issue entry. - Provide an issue-by-issue analysis table or equivalent structured list with, for each entry: provision reference, severity, deviation description, directional impact, cross-reference, practical consequence, and recommended response. - Make each issue self-contained and complete; do not leave any entry at the level of description only. - Include a dedicated section comparing the cover correspondence or transmittal notes to the redline and flagging any mismatch or omission. - Include a short section for policy alignment or compliance implications where the internal contracting policies matter. - Preserve plain-text-readable markup conventions in the analysis for any substantive deletion, insertion, or substitution so the deviation can be recovered after export. - End with a Recommended Actions section that uses imperatives, assigns the responsible role where the source documents identify one, and ties each action to a specific timing anchor or a clear relative urgency. - Close with a prioritized list of counter-positions or next steps ranked by severity or deal impact.