# Analyze Counterparty Markup Of Administrative Settlement Agreement > Guides section-by-section redline analysis of an administrative settlement agreement by anchoring each markup to the applicable environmental liability allocation framework, settlement authority, cleanup-program compliance requirements, and agency policy constraints rather than treating redlined changes as isolated contract edits. - Skill: `finchipaiorg/analyze-counterparty-markup-of-administrative-settlement-agr` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/analyze-counterparty-markup-of-administrative-settlement-agr` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/analyze-counterparty-markup-of-administrative-settlement-agr/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-of-administrative-settlement-agr --- # Skill: Analyze Counterparty Markup of Administrative Settlement Agreement — Redline Analysis Memorandum ## 1. Subject-matter triage - Treat the marked-up administrative settlement as a negotiated public-law instrument, not a generic commercial contract. - Identify at the outset whether the markup affects liability allocation, covenant scope, performance obligations, compliance mechanics, penalty architecture, or remedial timing. - If multiple parties, properties, operable units, work phases, or related instruments are in play, enumerate them before analysis and keep the treatment separate for each. - Read the redline against the draft and supporting documents as a single record; do not evaluate a clause in isolation from the settlement framework it implements. ## 2. Failure modes the skill is correcting - Treating redlines as isolated drafting edits without mapping each change to statutory, regulatory, or policy consequences. - Missing how a small textual edit can shift settlement scope, contribution protection, reopener risk, or enforcement leverage. - Failing to connect the markup to cost estimates, allocation summaries, reporting obligations, or other supporting materials that control the practical effect. - Accepting overbroad liability limitation, force majeure, or cure language that is inconsistent with administrative settlement practice. - Describing issues without stating severity, source-doc support, and a concrete negotiating response. - Writing conclusions without naming the controlling legal or policy authority for the proposition relied on. ## 3. Legal frameworks / domain conventions that apply - Environmental liability framework: identify the liable parties, the allocation structure, and how the markup shifts exposure among settling and non-settling parties. - Administrative settlement authority: assess the scope of the settlement, the basis for covenant relief, and any reservation-of-rights or reopener language. - Contribution protection: confirm that protection tracks the settlement scope and is conditioned on performance and compliance milestones. - Cleanup-program compliance requirements: compare proposed work, reporting, documentation, and cost-recovery mechanics against applicable cleanup-program standards and reasonableness expectations. - Financial assurance: evaluate whether the proposed mechanism satisfies the relevant agency criteria for strength, liquidity, and enforceability. - Stipulated penalties: assess whether any rates, triggers, grace periods, or caps preserve meaningful compliance incentives and enforceability. - Force majeure and excuse provisions: compare proposed triggers against settlement-appropriate categories and exclude purely commercial hardship unless the agreement clearly permits it. - Use the controlling authority that supports each legal proposition, whether statutory, regulatory, or policy-based, and name it explicitly in the analysis. ## 4. Analytical scaffolds - Work through the redline in section order and analyze every substantive change, even if the edit appears minor. - For each issue, state: the provision affected, what changed, the controlling authority or policy basis, the client impact, and the recommended negotiating posture. - Tie every material concern to the relevant source documents, including any cost estimate, allocation summary, technical report, compliance schedule, or governance document that the markup affects. - For allocation or exposure changes, describe the direction of shift and the affected pool or phase; do not reduce the analysis to generic “more risk” language. - For covenant, release, or contribution-protection edits, test whether the scope, conditions, and carveouts align with the settlement’s actual remedial footprint. - For reopener or reservation-of-rights changes, test whether any deletion or narrowing is consistent with mandatory agency practice and enforcement flexibility. - For financial assurance edits, test the sufficiency of the proposed form, timing, and enforcement mechanics against the governing requirements. - For timeline edits, trace cascading effects across downstream milestones, approvals, reporting dates, and completion obligations. - For penalty edits, assess whether the structure creates a genuine compliance incentive and preserves practical enforcement leverage. - Close each issue with three elements: the scale or threshold implicated by the source materials, the related clause or document interaction, and the downstream consequence for the client. - If the source materials contain a single relevant party, period, or scenario, state that expressly; otherwise analyze each separately rather than collapsing them. ## 5. Vertical / structural / temporal relationships - Map how changes affect the relative obligations of each settling and non-settling party, including contribution exposure and orphan-share risk. - Track whether one party’s revised language shifts residual liability or performance burden to another party. - Trace sequential milestone changes through later reporting, access, remedy, approval, or certification obligations. - Compare the markup against any parallel or prior consent decree, administrative order, side agreement, or related settlement so conflicts are visible. - Where the redline alters a defined term, apply the change consistently through every downstream use of that term. ## 6. Output structure conventions - Produce a formal redline analysis memorandum, not a generic comment list. - Use conventional sections: Executive Summary, Section-by-Section Analysis, Consolidated Issues Table, and Recommendations. - Executive Summary: give the overall risk profile, the mix of critical versus significant versus minor issues, and the main negotiating priorities. - Section-by-Section Analysis: for each redlined provision, state the markup, the legal or policy concern, the client impact, and the recommended response. - Consolidated Issues Table: include one row per issue with provision reference, issue category, severity, and recommended action. - Use an ordinal severity scale defined once and apply it uniformly, such as Critical / Significant / Minor. - In every entry, include a severity label, a short rationale, the governing authority, the document interaction, and the client consequence. - End with a Recommended Actions block that assigns an imperative action, the responsible role, and a timing anchor tied to the transaction or regulatory milestone. - When drafting any markup language for the analysis, make every substantive edit identifiable in plain text as well as by formatting, using explicit textual change markers and a brief rationale. - Keep the file name exactly as instructed: redline-analysis-memorandum.docx.