agentleFS
McGuireKevinMcGuireKevin/cell-site-lease-negotiation-toolkit/.claude/skills/redline-review/SKILL.md

redline-review

Skill0 starsChanged 59 days agoMITView on GitHub

Review a counterparty's redline or counter-draft of a telecom lease amendment. Reads the new language for legal, risk, liability and construction concerns against the underlying lease and the carrier-side amendment primer, maps every provision to the agreed term sheet, and produces a reviewer's note and a reply. Use when a landlord, tower company or rent-stream acquirer returns a marked-up amendment, when comparing a clean draft against the last agreed version, or when asked what is wrong with a counter-draft. Stage 7 of the lease negotiation pipeline.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. alevi/redline★ 7same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not every change: every sentence that was not in what we sent.

    line 66
  2. Distinctive:

    Use their comments. A comment is usually where the reason lives, and the reason is what tells you whether an edit is negotiable or a …

    line 119
  3. Very specific:

    When a reconciliation mismatch appears, the fix is upstream: deal-intake records the change and the drafter reissues.

    line 199

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Redline review

The other side sent something back. Most of it is fine, some of it is a trade, and a little of it is a hole. This finds which is which.

OutputWhat it is
<site>-redline-rN.mdThe reviewer's note: what changed, what it costs, what to ask for.
<site>-reply-rN.mdA draft reply to the counterparty, point by point.
deviations[] in the deal fileOnly where redline.html has already been run. This skill does not write the deal file itself.

The rule that shapes everything here

Deviation from the clause library is the normal case, not a defect. Counsel on the other side writes new sentences for a living. A review that reports "this does not match our clause" is reporting that a negotiation happened. What the negotiator needs is what the new language does: where it creates an exposure, removes a protection, imports something nobody has read, or says something the lease already says differently.

So: never recommend a change because the wording differs from the library. Recommend a change because of what the wording will do on this site.

Before anything else

  • docs/amendment-primer.md — the substance. Part 4 by amendment type, Appendix B's pitfall table, and 5.3 on redline hygiene.
  • The conformed working copy of the lease as currently amended, from the amendment-drafting skill. Without it you are reviewing the amendment against nothing.
  • The deal file — definedTerms for what this lease calls things, sectionMap for what its sections are, playbook.points for what was actually asked for, audit.termsAnalysis for what was already known to be wrong.
  • What redline.html already found. It runs two mechanical passes: pattern signals over the edits, and structural concerns over the new sentences. Read both before starting; do not repeat them, and do not assume they are complete.

The two baselines

Primer 5.3, and the reason most redline reviews miss things. Every returned draft is compared against both:

  1. The conformed copy — everything the amendment changes about the lease.
  2. The last draft we sent — everything the counterparty changed about our draft.

The counterparty's own redline, cover email or summary of changes is not a substitute for either. Redlines are routinely incomplete through inadvertence, and a changed definition or a revised boilerplate section rarely appears in anyone's summary. Where only a clean copy arrived, say so in the note and compare against the last agreed version before signature.

Exhibits get their own comparison. Drawings and equipment lists are revised outside the word processing file and are excluded from automated comparisons.

Procedure

1. Establish what you are comparing

Name the two baselines by filename and date. If either is missing, stop and say which — a review against one baseline is half a review and should not be presented as a whole one.

2. Read every new sentence

Not every change: every sentence that was not in what we sent. For each, answer four questions in this order, and only record what has an answer:

Construction. Does it refer to a section, exhibit or schedule that exists? Does it use a term this lease defines, with the same meaning? Does it state a period, and once rather than twice? Does it say who performs, by when, and what happens if they do not?

Interpretation. What does it mean against the unchanged text around it? A new sentence can change a provision nobody edited — that is primer 1.1, and it is the effect most often missed. Does it create a negative implication against a right we already have?

Risk. What happens on this site if the other party exercises it fully and in bad faith? That is the only test that matters for a right; the reasonable case is not the one to plan for.

Liability. What is uncapped, unqualified, or survives termination?

3. Map every provision to the agreed deal

Primer 4.8, and the check that catches what no pattern can. Take the agreed term sheet — the playbook.points that were raised and the counters that were accepted — and map every provision of the returned draft to one of them.

Anything that maps to nothing is a new request. It does not matter how reasonable it looks or how deep in the boilerplate it sits. List these separately, under that heading, because a counterparty form is built to use the amendment moment and this is the only step that finds it.

4. Read the parts nobody reads

In this order, because this is the order of how often they carry something unrequested:

  1. Definitions, and anything that changes what an existing term means.
  2. The integration clause and the conflict clause.
  3. Ratification, estoppel and release language.
  4. Exhibit legends and anything describing what an exhibit is.
  5. Notices, and the payee.

5. Price what moved

Any figure, period or term length that changed goes back to the comparator before the note is finished. A review that says "they moved the rent" without saying what it costs over the window is not finished. Where redline.html flagged affectsPricing, that is the list.

6. Decide, and say why

For each concern: accept, reject, or trade. A concern with no recommendation is an observation, and the negotiator has to make the decision anyway.

  • Accept where the change is immaterial on this site, or where it is worth less than the relationship cost of arguing it. Say that plainly rather than dressing it up.
  • Reject where it removes a protection, creates an uncapped exposure, or imports terms nobody has read. Give the sentence to replace it with.
  • Trade where it is a genuine ask. Name what it buys, from playbook.concessionOrder.

Use their comments. A comment is usually where the reason lives, and the reason is what tells you whether an edit is negotiable or a condition of signing.

7. Emit

The reviewer's note, in the order a reviewer reads:

  1. What arrived, what it was compared against, and whether tracked changes were used
  2. What this round costs, in one line, against the walk-away
  3. Provisions that map to no agreed term — the new requests
  4. Concerns that must be rejected, each with replacement language
  5. Concerns worth trading, and what to trade them for
  6. What is accepted without argument, listed but not argued
  7. What could not be checked: exhibits not supplied, a missing baseline, a PDF instead of a document

The reply follows the note but says only what the counterparty should hear. It never carries the walk-away, the concession order, or what we were prepared to accept.

Hard rules

Never recommend a change on the ground that it differs from the library. Say what it does.

Never invoke Section 6409(a) as a reason the counterparty must agree. It governs governmental review of eligible facilities requests, not private consent, and using it that way costs credibility with a counterparty who knows the difference.

Quote the sentence. A concern that paraphrases cannot be checked by the person who has to decide it, and paraphrase is where a review quietly becomes an opinion.

Say what you could not check. A PDF carries no styles and no tracked changes; an exhibit that was not supplied is a term nobody has read. Both go in the note as gaps, not as clean.

A clean mechanical run is not a clean document. redline.html reports that no pattern fired and no structure is missing. Neither statement is about meaning.

Never send the deal file, the playbook, or anything derived from them. The reply is prose.

Before you finish

  • Both baselines named, or the missing one stated
  • Every new sentence read, not every flagged change
  • Every provision mapped to an agreed term; unmapped ones listed as new requests
  • Definitions, integration, conflict, ratification and exhibit legends read deliberately
  • Everything that moved a figure re-priced, or listed as needing it
  • Every concern carries accept, reject or trade, and rejections carry replacement language
  • The reply carries no walk-away, no concession order, no internal figure
  • Gaps stated: exhibits, baselines, PDFs

Not built yet

Writing dispositions back. redline.html owns deviations[] and its accept/reject discipline. This skill produces the reasoning; a person still records the decision in the tool, which is where stage 8 reads it from.

The conformed copy. Produced by hand today, through Word Compare over the document management system's versions. Until a tool builds it, the first baseline is only as good as that.

Two things on the page that no signal of yours will find

Both are absences, and every signal you run reads what the text says.

Blanks they left. On counterparty paper the draft arrives with stubs where the negotiation has not landed — a ruled line where the rent goes, a bracketed prompt for a date, an unfilled merge field. A blank says nothing, so nothing catches it, and an unfilled stub in an executed instrument is either a term the other side completes later or a gap a court construes. redline.html scans their text and records them as redline.openStubs[]; the final report will not produce a package while any remain. Treat one as a term nobody has agreed, not as a formatting defect.

Facts that no longer match the file. redline.reconciliation compares the document against the deal file — the parties, the notice address, the site id, the agreed rent, term end and effective date. These are not concessions to weigh: a landlord who no longer holds the interest is not a negotiating position, and the usual cause is that the party changed mid-negotiation and the draft in circulation still names the assignor. Its name sits in the preamble, the recitals, the notices clause, the signature block and the running head, and correcting one of those and not the rest is the common failure.

When a reconciliation mismatch appears, the fix is upstream: deal-intake records the change and the drafter reissues. Do not disposition it as though the counterparty had proposed something.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.