# Draft Markup Of Administrative Settlement Agreement > Guides preparation of a buyer-side redline markup of an administrative settlement agreement for a prospective purchaser of a contaminated industrial site by focusing edits on liability protections, covenant scope, reopener limitations, and financial assurance adequacy. - Skill: `finchipaiorg/draft-markup-of-administrative-settlement-agreement` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-markup-of-administrative-settlement-agreement` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-markup-of-administrative-settlement-agreement/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/draft-markup-of-administrative-settlement-agreement --- # Skill: Draft Redline Markup with Comment Annotations of Administrative Settlement Agreement for Prospective Purchaser ## 1. Subject-matter triage (only if applicable) - Confirm the agreement is being reviewed from the prospective purchaser’s side and that the site is an environmentally impacted industrial property. - Inventory the source set before drafting: proposed settlement/order, technical diligence, regulatory correspondence, cleanup status materials, title/transaction documents, and any attachment schedules. - If more than one site parcel, operable unit, contaminant class, or remediation phase is implicated, separate them before analysis; do not blend distinct obligations into one pass. - If the proposed settlement purports to coordinate state and federal liability protection, identify whether separate federal action is contemplated or needed. ## 2. Failure modes the skill is correcting - Baseline produces a generic contract redline without applying the environmental liability and cleanup-program framework that governs what an administrative settlement agreement can and cannot provide a prospective purchaser. - Baseline does not test covenant-not-to-sue language against known site conditions, remaining data gaps, and cleanup obligations disclosed in diligence materials. - Baseline misses provisions that are inconsistent with governing environmental authority or cleanup-program requirements and therefore ineffective, overbroad, or hard to enforce. - Baseline fails to preserve mandatory reopeners for unknown conditions, changed circumstances, or later-discovered contamination. - Baseline underreviews financial assurance, performance milestones, and objective completion criteria, leaving the buyer with open-ended or unmeasurable obligations. - Baseline omits the prioritized cover summary and negotiation roadmap that should accompany the markup. - Baseline uses styling-only edits; the reader cannot reliably identify changes from exported text alone. - Baseline gives issue descriptions without a clear severity judgment, source cross-reference, and client consequence. - Baseline states legal conclusions without naming the governing authority supporting the point. ## 3. Legal frameworks / domain conventions that apply - Prospective purchaser protections: evaluate the agreement against the applicable federal and state liability-protection framework for purchasers of contaminated property; confirm the drafting matches the intended cleanup posture and any conditions for protection. - State cleanup order authority: assess the scope and mechanics of the state environmental settlement or consent order; confirm how it interacts with any federal liability or cleanup protection that may also be needed. - Covenant not to sue: check whether the covenant is site-specific, tied to performance of required work, and appropriately limited by known and unknown conditions and statutory reservation rights. - Reopener language: preserve mandatory reopeners for unknown conditions, new information, changed site conditions, nonperformance, and future legal or regulatory developments. - Financial assurance: review whether the selected assurance mechanism is reasonably tied to the expected remediation obligations and to the form of security typically accepted for environmental performance commitments. - Response action obligations: identify what the purchaser must perform under the agreement; test whether scope of work, milestones, and completion criteria are clear, objective, and administrable. - Contribution protection: confirm the extent and conditions of any contribution protection tied to the settlement and whether that protection is appropriately limited to the addressed site or operable area. - Cleanup-program compliance: identify whether cost recovery, reimbursement, reporting, access, sampling, institutional controls, or performance provisions are conditioned on compliance with the applicable cleanup standards and procedural requirements. - Authority citation discipline: when a drafting point depends on a legal rule, cite the rule by name and section, regulation, part, or recognized authority rather than stating the conclusion bare. ## 4. Analytical scaffolds - Review each provision of the proposed agreement in order from the prospective purchaser’s perspective. - For liability provisions: assess whether the agreement provides adequate protection against environmental liability given the site conditions in the diligence materials. - For covenant-not-to-sue provisions: verify scope, conditionality, and limits on unknown conditions; compare against known site conditions and any prior enforcement history in the source set. - For reopener provisions: verify that mandatory statutory or regulatory reopeners are preserved and that attempts to narrow them are resisted. - For response action obligations: assess whether the scope of required work is clearly defined and completion criteria are objectively measurable. - For financial assurance: assess whether the proposed mechanism is adequate and consistent with accepted environmental assurance practice. - For contribution protection: verify scope and conditionality; assess whether protection extends to claims that could realistically arise given site history. - Draft the redline markup using a plain-text-resistant convention in addition to any visual markup: flag deletions, insertions, and substitutions in-line, and attach a short rationale comment to each substantive change. - Draft the cover summary after the markup exists; prioritize issues by negotiating leverage and regulatory risk, and give each item an ordinal severity label. - For every issue or comment, state the relevant controlling authority where one is being invoked, and connect the point to the source documents and downstream consequence for the buyer. ## 5. Vertical / structural / temporal relationships (only if applicable) - Deal context: the prospective purchaser’s planned use of the property drives which obligations and protections are most critical; test each provision against the anticipated use. - State versus federal coordination: a state settlement may not by itself resolve all federal liability concerns; assess whether the agreement coordinates with or requires a corresponding federal action. - Technical diligence findings: the scope of site conditions known at the time of the agreement affects the adequacy of the covenant scope and informs which reopener scenarios are most likely. - Temporal sequencing: distinguish pre-closing deliverables, closing conditions, post-closing performance, reporting intervals, milestone dates, and end-point closure conditions. - If the agreement contemplates multiple periods or compliance windows, treat each separately rather than collapsing them into one generic risk. ## 6. Output structure conventions - Deliver the redlined agreement as the primary work product, and only then prepare the cover summary; do not let the summary substitute for the markup. - The markup must be readable from plain text alone: every substantive edit should be identifiable by explicit textual tags plus a brief rationale comment. - Use standard contract-comment practice, but keep comments short, targeted, and tied to a specific revision. - The cover summary should use conventional legal-drafting organization: executive priority list, provision-by-provision change summary, and negotiation recommendations. - Every summary entry should state severity on an explicit ordinal scale defined once at the top of the document. - When multiple issues exist, list them separately and address each one with its own rationale, controlling authority, and client impact. - Close the summary with an explicit Recommended Actions section that assigns each next step to a role and a timing anchor tied to the transaction or regulatory schedule. - Ensure the named deliverable file matches the task instructions exactly and contains the operative markup, not merely a description of it.