Lease abstract
Turns a lease or property agreement and its amendments into a standardized abstract with key dates, financial terms, obligations, and exceptions. Use for lease abstraction, rent-roll preparation, tenancy data capture, property contract summaries, or portfolio review.
Published Aug 21, 2026 · Updated Aug 26, 2026
Requirements
Add the company abstract schema and required record fields. Define the currency, area, date, and rent-period conventions used in records. Specify which lease obligations property teams want tracked after abstraction. Add the company policy for escalation of ambiguous or conflicting amendments.
Skill document
The full SKILL.md your agent reads and follows.
Lease abstract
Purpose
Convert a lease file into a consistent record that property and finance teams can use without rereading the agreement.
Scope
Commercial, residential, and mixed-use leases or operating agreements, including amendments and side letters. Excluded: legal advice, enforceability opinions, and negotiation of lease terms.
Data basis
- Lease, amendments, side letters, object record, and the company abstract schema.
- The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.
Result
A lease abstract document and a structured row containing parties, premises, dates, rent mechanics, options, security, cost obligations, and unusual rights.
Quality criteria
- Every extracted term cites its document and page or section.
- Amendments override earlier terms only where the amendment clearly does so.
- Unknown or conflicting values remain visible as open points.
- The structured row and narrative abstract contain the same key values.
Instructions
Read amendments in chronological order and state which version controls each changed term. Preserve contractual wording for dates, formulas, notice periods, and options before normalizing values. Distinguish fixed rent, variable charges, incentives, deposits, and pass-through costs. Never infer a missing date or amount. Use the company schema when present; otherwise use the output fields defined in the steps.
Adapt before use
Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence.
- Add the company abstract schema and required record fields.
- Define the currency, area, date, and rent-period conventions used in records.
- Specify which lease obligations property teams want tracked after abstraction.
- Add the company policy for escalation of ambiguous or conflicting amendments.
Related skills
- Claim chronology builder
Builds a dated chronology from claim notices, correspondence, contracts, invoices, incident records, and evidence logs, preserving source citations and disputed dates. Use for insurance claims, commercial disputes, incident files, demand packages, litigation chronologies, and internal fact reviews.
- Compliance training refresh
Updates compliance training modules against revised policies, identifies changed learner obligations, and creates source-linked lesson text, scenario questions, and an answer key. Use for annual compliance refreshes, policy changes, code-of-conduct training, and controlled learning-content updates.
- Contract obligation register
Extracts dated and recurring duties from signed contracts into an obligation register with parties, triggers, notice windows, service levels, payment terms, evidence, and owners. Use for contract lifecycle management, renewal tracking, vendor obligations, or inherited agreement cleanup.
- Contract playbook review
Reviews a commercial contract against a company playbook, records missing or non-standard clauses with exact citations, and proposes fallback positions. Use for procurement, sales, SaaS, services, and contract redline preparation.