# Analyze Counterparty Markup Of Commercial Lease Agreement > Guides prioritized redline analysis of a counterparty lease markup by structuring cross-document reconciliation, economic impact quantification, and playbook-calibrated response recommendations. - Skill: `finchipaiorg/analyze-counterparty-markup-of-commercial-lease-agreement` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/analyze-counterparty-markup-of-commercial-lease-agreement` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/analyze-counterparty-markup-of-commercial-lease-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/analyze-counterparty-markup-of-commercial-lease-agreement --- # Skill: Analyze Counterparty Markup of Commercial Lease Agreement — Redline Review Memorandum ## 1. Subject-matter triage - Treat the landlord markup as the primary comparison document against the original draft, playbook, comps, and deal email. - Identify whether the source set contains multiple governing layers: draft lease, landlord markup, playbook, comp set, and deal communications. - If the sources conflict, surface the conflict and state which source appears to control under the deal instructions. - Use the deal email and comps to distinguish true negotiated business terms from template drift or non-market asks. ## 2. Failure modes the skill is correcting - Baseline identifies changes in isolation without reconciling them to the playbook, comps, or deal economics. - Baseline omits severity, priority, or response sequencing, making the memo non-actionable. - Baseline states that a clause is unfavorable without tying it to the operative lease term, schedule, or related rider it affects. - Baseline misses compound effects where two or more markup changes together shift economics, control, or exit flexibility. - Baseline treats all issues as equally important instead of separating material deal breakers from negotiable cleanups. - Baseline relies only on visual redline formatting and loses the actual change content when exported. - Baseline gives diagnoses without concrete response recommendations or role/timing guidance. ## 3. Legal frameworks / domain conventions that apply - Lease economics: base rent, rent abatement, operating expenses, and tenant improvement economics should be read together, not clause by clause in isolation. - Net lease allocation: expense pass-throughs, reimbursements, exclusions, and caps determine the practical rent burden. - Operating expense and CAM mechanics: controllable versus non-controllable items, audit rights, documentation support, and exclusions are core tenant protections. - Security and credit support: guaranty scope, letter of credit terms, replacement conditions, and replenishment triggers can materially change risk. - Use, assignment, and transfer controls: consent standards, permitted transfer exceptions, recapture, and profit sharing affect flexibility and exit value. - SNDA and lender-related terms: subordination and non-disturbance mechanics should be read with financing and estoppel provisions. - Casualty, condemnation, and restoration: termination rights, rent abatement, and rebuild timing are interdependent. - Default, cure, and remedies: notice periods, self-help, late charges, and acceleration language can create disproportionate leverage. - Holdover, surrender, and renewal provisions: these terms affect end-of-term planning and transition risk. - Where the source documents identify a governing authority or market standard, cite that authority or standard explicitly in the analysis. ## 4. Analytical scaffolds - Start by enumerating the discrete issues raised by the markup and, where relevant, the affected sections, exhibits, and riders. - For each issue, compare the markup against the original draft, playbook, comps, and deal email, then state whether the change is aligned, a deviation, or a conflict. - Tie each issue to a concrete lease economic, operational, or legal consequence rather than describing the change abstractly. - Use an ordinal severity scale defined once at the top of the memo, and apply it consistently to every issue. - For each issue, include: - the section reference, - the markup change, - the governing source position, - the practical impact, - the severity rating, - the recommended counter-position. - Close each issue by: - scaling it against an available lease figure, term, threshold, or timing marker from the source set, - cross-referencing the interacting clause, schedule, or document, - stating the downstream consequence for the client. - When a single redline affects multiple provisions, analyze the combined effect before recommending a response. - When the deal email or playbook expressly authorizes a deviation, note that authorization and treat the issue accordingly. - If the source set does not support a precise quantification, state the limitation and give the best available directional impact instead of inventing arithmetic. - Track whether an issue is market, negotiable, or outlier-level by reference to the comps and playbook, but do not overwrite the severity scale with those labels. ## 5. Vertical / structural / temporal relationships - Read the body, exhibits, riders, and referenced forms as one integrated lease package. - Confirm that defined terms remain consistent across the lease and all attachments. - Check whether a markup in one section changes the operation of another section, especially where timing, notice, cure, commencement, abatement, reimbursement, or termination rights interact. - Analyze commencement, delivery, tenant-improvement milestones, and any rent-free period together when any one of them moves. - Treat amendment language, priority clauses, and exhibit order as potential conflict rules. - When multiple periods or alternative triggers exist, analyze each relevant period separately rather than collapsing them into one generalized answer. - If only one issue, party, or timing path is actually in scope, say so affirmatively before analyzing it. ## 6. Output structure conventions - Title the memo as a redline review memorandum and keep the filename exactly as instructed. - Begin with a short executive summary that states the overall posture of the markup, the highest-severity themes, and the practical negotiation stance. - Define the severity scale once near the top using an ordinal set such as Critical / High / Medium / Low. - Organize the body by severity first, then by lease section or topic. - For each issue entry, use a consistent structure: section reference, description of the change, comparison to source positions, impact, severity, and recommended response. - Use robust plain-text change notation in the analysis so the reader can identify the substantive edits even if styling is stripped in export. - Include an explicit recommendation for each issue using imperative language, and identify the responsible role and timing anchor where the source documents provide one. - End with a Recommended Actions block that sequences the next steps and flags which issues to lead with versus hold for leverage. - Make the negotiation sequencing practical: lead with issues that affect economics, control, or closing risk; reserve lower-leverage items for later rounds. - If the memo relies on a legal proposition or market-standard statement, name the controlling authority, rule, or standard supporting it. - Keep the analysis prioritized and concise; do not reproduce the markup as a flat summary without judgment.