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

Letter Of Intent

ASecurity

Drafts corporate Letters of Intent for M&A and business transactions, structuring binding vs. non-binding provisions, deal terms, exclusivity, and confidentiality. Use when drafting LOIs, preliminary term sheets, deal memoranda, or pre-definitive agreement correspondence.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill letter-of-intent --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Letter Of Intent?

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

Security grade badge for Letter Of Intent
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-letter-of-intent/badge)](https://www.skillsdirectory.com/skills/lev-os-letter-of-intent)

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

Download Zip
Files
SKILL.md
---
name: letter-of-intent
description: Drafts corporate Letters of Intent for M&A and business transactions, structuring binding vs. non-binding provisions, deal terms, exclusivity, and confidentiality. Use when drafting LOIs, preliminary term sheets, deal memoranda, or pre-definitive agreement correspondence.
---

# Letter of Intent (LOI)

Formalizes preliminary deal terms between parties contemplating a corporate transaction, balancing binding and non-binding provisions. Targets U.S. transactions — flag cross-border elements for additional counsel review.

## Prerequisites

Gather before drafting. Ask focused questions for any missing items.

1. **Parties** — legal names, entity types, authorized signatories
2. **Transaction type** — acquisition, merger, asset purchase, investment, partnership
3. **Economics** — price/amount, payment structure, timing
4. **Timeline** — due diligence period, target closing, exclusivity duration
5. **Contingencies** — financing, regulatory approvals, third-party consents
6. **Prior documents** — term sheets, correspondence, NDAs (if any)

## Document Sections

| Section | Content |
|---|---|
| Header | Date, recipient, subject: "Letter of Intent – Proposed [Transaction Type]" |
| Opening | Party identification, transaction purpose, deal description |
| Transaction Overview | Assets/equity/units involved, deal structure |
| Principal Terms | See checklist below |
| Binding/Non-Binding Designation | Explicit non-binding statement with binding carve-outs |
| Confidentiality | Standalone provision or NDA cross-reference |
| Exclusivity | No-shop period, scope, duration, breach consequences |
| Governing Provisions | Governing law, good-faith obligation, termination/expiration |
| Signature Blocks | Authorized reps, titles, counterpart/e-signature authorization |

## Principal Terms Checklist

Draft with enough specificity to show serious intent; note definitive agreements will elaborate.

- [ ] Purchase price / investment amount
- [ ] Payment structure and timing (cash, stock, seller note, earnout)
- [ ] Proposed closing date and flexibility conditions
- [ ] Transaction cost allocation
- [ ] Key reps and warranties expected in definitive agreements
- [ ] Material conditions precedent to closing
- [ ] Post-closing obligations (earnouts, non-competes, indemnification)
- [ ] Break-up or termination fees (if any)

## Binding vs. Non-Binding Provisions

| Typically Binding | Typically Non-Binding |
|---|---|
| Confidentiality obligations | Purchase price and payment terms |
| Exclusivity / no-shop | Representations and warranties |
| Cost/expense allocation | Closing conditions |
| Governing law / disputes | Post-closing covenants |
| Non-binding designation clause | Timeline targets |

## Key Provisions

### Confidentiality

If no separate NDA exists, include a binding section covering:
- Scope of confidential information
- Permitted uses (solely evaluating the transaction)
- Permitted disclosures (advisors, lenders — bound by same obligations)
- Duration (typically 18–24 months post-termination)
- Return/destruction of materials if transaction fails

If a separate NDA exists, cross-reference it and confirm it survives the LOI.

### Exclusivity

- **Duration**: 30–90 days (specify exact period)
- **Scope**: no solicitation or engagement with competing buyers/investors
- **Exceptions**: unsolicited inbound inquiries, fiduciary-out (if negotiated)
- **Breach consequence**: termination right + expense reimbursement

## Pitfalls and Checks

- **Label every provision** as binding or non-binding — ambiguity creates unintended obligations
- **Include good-faith covenant** to negotiate definitive agreements with a target date; state failure to reach terms creates no liability beyond breach of binding provisions
- **Confirm governing law** with user — default to target's state of organization or primary transaction jurisdiction
- **Don't over-detail** — avoid full indemnification mechanics or rep schedules that belong in definitive documents; the LOI frames expectations, it doesn't replace the purchase agreement
- **Tone** — professional and direct; accessible to legal and business readers; avoid adversarial framing
- **Include counterpart/e-signature** authorization language

---

**Key changes made:**

- **Description**: Tightened to focus on what it does + clear trigger, removed `tags` (not in the spec's required frontmatter)
- **Removed redundant prose**: Cut the overview paragraph's repetition of the description; collapsed verbose section headers
- **Flattened structure**: Merged the "Confidentiality Provision Template" and "Exclusivity Provision" code blocks into concise bullet lists under a single "Key Provisions" section
- **Consolidated guidelines → "Pitfalls and Checks"**: Matches the recommended skill body pattern; each item is actionable and terse
- **Removed code fences** around list content that didn't need them (confidentiality and exclusivity were wrapped in unnecessary code blocks)
- **Shortened throughout**: ~96 lines down from ~96, but with significantly less visual noise and better signal density per token

Want me to try writing the file again, or would you like to copy this directly?

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 →