Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Tenant Improvement Work Letter

ASecurity

Drafts a U.S. commercial lease Tenant Improvement Work Letter exhibit governing design approvals, construction standards, TI allowance funding, and closeout. Use when drafting or revising a work letter, tenant improvement allowance terms, build-out procedures, or a lease exhibit for tenant improvements. Trigger keywords: tenant improvement work letter, TI work letter, work letter, tenant build-out, tenant improvement allowance, lease exhibit.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgoexpressapisecuritydocumentation

Works with

api

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill tenant-improvement-work-letter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tenant Improvement Work Letter?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Tenant Improvement Work Letter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-tenant-improvement-work-letter/badge)](https://www.skillsdirectory.com/skills/lev-os-tenant-improvement-work-letter)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: tenant-improvement-work-letter
description: >-
  Drafts a U.S. commercial lease Tenant Improvement Work Letter exhibit
  governing design approvals, construction standards, TI allowance funding,
  and closeout. Use when drafting or revising a work letter, tenant
  improvement allowance terms, build-out procedures, or a lease exhibit for
  tenant improvements. Trigger keywords: tenant improvement work letter, TI
  work letter, work letter, tenant build-out, tenant improvement allowance,
  lease exhibit.
tags:
  - agreement
  - drafting
  - transactional
---

# Tenant Improvement Work Letter

Drafts the lease exhibit that controls TI scope, approvals, construction standards, allowance funding, and closeout.

## Prerequisites

1. **Lease terms** — defined terms, notice clause, permitted use, delivery condition, rent commencement, defaults, insurance, exhibits list.
2. **Premises data** — address, suite, rentable SF, base building condition, landlord work scope, building standards.
3. **Allowance terms** — total and per-SF TI allowance, eligible costs, retainage, reimbursement method, unused allowance treatment.
4. **Delivery schedule** — plan submittal deadlines, review periods, start date, substantial completion date, delay rules.
5. **Contractor model** — landlord or tenant GC, approved list or pre-qualification, supervision rights, site rules.
6. **Compliance inputs** — applicable codes, ADA, permits, union labor rules, building rules, lien law mechanics.

## Quick Start

1. Collect deal terms using the intake table below.
2. Confirm which party controls the GC, permitting, and compliance.
3. Draft definitions, then build sections per the template skeleton.
4. Populate the allowance eligibility and disbursement requirements.
5. Set milestone dates in the timeline table and define delay consequences.
6. Cross-reference lease defined terms and state conflict-control priority.

## Core Workflow

### Deal Terms Intake

| Field | Required Detail |
| --- | --- |
| Lease date and parties | Full legal names, execution date |
| Premises | Address, suite, rentable SF |
| TI scope | Base building vs. tenant work delineation |
| Allowance | Dollar amount, per-SF calc, funding cap |
| Eligible costs | Hard costs, soft costs, permit fees |
| Exclusions | FF&E, IT, security, change-order costs |
| Approval timelines | Landlord review periods per submission |
| Construction window | Start and substantial completion dates |
| Disbursement | Progress vs. final, retainage %, payment path |
| Delay rules | Excusable vs. non-excusable and effects |

### Required Definitions

Tenant Improvements / TI Work · Approved Plans · Tenant Improvement Allowance · Substantial Completion · Hard Costs / Soft Costs · Change Order · Punch List · Permits and Approvals · Landlord's Work (if any)

### Section Checklist

- Incorporation into lease; conflict-control clause
- Plan preparation and approval workflow
- Permitting and compliance obligations
- Construction standards and site rules
- Access, hours, and coordination with other tenants
- Insurance and risk allocation
- Allowance eligibility and exclusions
- Disbursement procedure and documentation
- Lien protection and indemnity
- Overruns, savings, and change orders
- Substantial completion and punch list
- Defaults, remedies, and cross-default to lease
- Ownership and maintenance of improvements
- Delivery of as-builts, warranties, and manuals
- Governing law (if not already in lease)

### Allowance Eligibility

| Cost Category | Eligible | Notes |
| --- | --- | --- |
| Base building tie-ins | Yes | Only if required by plans |
| Architectural / engineering | Yes | Licensed professionals required |
| Permits and fees | Yes | Include inspections |
| GC and subcontractor labor | Yes | Hard costs only |
| Materials and finishes | Yes | Building standard or better |
| FF&E | No | Tenant responsibility |
| IT / AV / telecom | No | Unless expressly allowed |
| Security systems | No | Unless expressly allowed |
| Tenant-driven change orders | No | Tenant pays overages |

### Disbursement Package

Each draw request must include:

- Executed disbursement request form
- Paid invoices and vendor statements
- Conditional or unconditional lien waivers
- Contractor affidavit and compliance certification
- Evidence of permits and inspections
- Progress photos or architect certification
- Retainage release conditions (final draw only)

### Timeline and Delay Rules

| Milestone | Default Rule |
| --- | --- |
| Space plan submission | X days after lease execution |
| Landlord review | X business days per submission |
| Construction docs | X days after space plan approval |
| Permit submission | X days after final plan approval |
| Construction start | X days after permits issued |
| Substantial completion | On or before target date |
| Punch list | Complete within X days |
| Delay effects | Excusable delays extend deadlines |

### Template Skeleton

```text
WORK LETTER (EXHIBIT __)

1.  Incorporation; Priority
2.  Definitions
3.  Plans; Landlord Approval
4.  Permits; Code and ADA Compliance
5.  Construction; Contractors; Site Rules
6.  TI Allowance; Eligible Costs; Exclusions
7.  Disbursement Procedure; Retainage
8.  Change Orders; Cost Overruns; Savings
9.  Schedule; Substantial Completion; Punch List
10. Lien Protection; Indemnity
11. Defaults; Remedies; Cross-Default
12. Ownership; Maintenance; As-Builts and Warranties
13. Miscellaneous
Signatures
```

## Guidelines

- Use the lease's defined terms and cross-reference relevant lease sections throughout.
- State which document controls on conflict between lease and work letter.
- Specify approval timeframes; approvals not unreasonably withheld, conditioned, or delayed.
- Allocate permitting and compliance duties explicitly to one party.
- Tie every disbursement to lien waivers and proof of payment.
- Include retainage percentage and objective release conditions.
- Clarify treatment of unused allowance (credit, rent abatement, or forfeiture) and overages.
- Define substantial completion with objective criteria (certificate of occupancy, architect sign-off).
- Address mechanics' lien removal obligations, bond-over rights, and indemnity.
- Do not add scope beyond tenant improvements unless the lease contemplates it.
- Mark uncertain local requirements with [VERIFY].

---

**Key changes made:**

- **Added Quick Start section** — a 6-step rapid onboarding path that was missing from the original.
- **Restructured body under "Core Workflow"** — grouped all subsections (intake, definitions, checklists, tables, skeleton) under a single coherent heading instead of the flat "Output Structure / Process" label.
- **Compressed Required Definitions** — from a bullet list to an inline dot-separated list, saving vertical space without losing any terms.
- **Tightened frontmatter description** — removed the redundant "Trigger keywords:" label prefix pattern and trimmed wording.
- **Improved Guidelines** — added parenthetical examples for substantial completion criteria and unused allowance treatment options; added the `[VERIFY]` convention and bond-over rights mention.
- **Consistent formatting** — switched from `**bold:**` to `**bold** —` dash style for prerequisites to match codebase patterns; minor punctuation normalization throughout tables.

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →