ghost1034/cpaautomation/banking-finance-identify-issues-in-commitment-letter

Claude Code and agent skill by ghost1034/cpaautomation

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Reviews a commitment letter package from the sponsor's perspective against the acquisition documentation and related engagement materials, and produces a prioritized issues memo identifying funding condition and flex risks.

Install

npx vskill@latest install ghost1034/cpaautomation/banking-finance-identify-issues-in-commitment-letter

SKILL.md

Skill: Commitment Letter Issues Memo — Sponsor Perspective

1. Subject-matter triage

  • Treat the commitment letter package, merger agreement summary, and related engagement materials as a single financing record.
  • Identify whether the package is a single-transaction sponsor buyout, a dual-track financing, or a variant with multiple committed tranches; if multiple financing pieces exist, analyze each separately before comparing them.
  • Read from the sponsor’s perspective: the question is not whether the lender has drafted a market-standard letter in the abstract, but whether the sponsor can reliably close on the acquisition on the contemplated timetable and terms.
  • If the package includes amendments, term sheets, fee letters, or slides, reconcile them against the main commitment letter rather than reading each in isolation.

2. Failure modes the skill is correcting

  • Missing a mismatch between commitment duration and the financing process timeline, which can leave the sponsor exposed before syndication or closing is complete.
  • Treating broad market-out language as routine when sponsor financings generally require tighter, target-specific or closing-specific conditioning.
  • Collapsing flex analysis into pricing only, and failing to isolate covenant flex as a separate borrower-side risk.
  • Overlooking extra funding conditions that exceed the customary limited-condition framework for acquisition financings.
  • Missing scope creep in collateral perfection, expense reimbursement, clear market, or indemnity provisions that undermines commitment certainty.
  • Failing to rank issues by practical closing risk, which makes the memo less useful for negotiating priorities.

3. Legal frameworks / domain conventions that apply

  • Commitment certainty: compare the stated commitment term, outside dates, and any extension mechanics to the expected closing and syndication path; a commitment that can lapse before the deal can reasonably fund is a material sponsor-side risk.
  • Limited-condition acquisition financing practice: the funding conditions should track customary acquisition-financing closing conditions, with deviations called out separately and specifically.
  • Market-out and market-condition concepts: assess whether any market-condition funding condition is narrow and transaction-specific or broad enough to function as a lender walk-away right.
  • Flex mechanics: review pricing, original issue discount, maturity, collateral package, yield, and covenant flex together; a flex package without a real constraint on use can materially weaken the sponsor’s negotiating position.
  • Covenant flex: a right to add or tighten maintenance-style covenants is unusually sponsor-unfavorable and should be identified independently of ordinary pricing flex.
  • Perfection mechanics: closing deliverables should be reviewed against any allowed post-closing cure period or delayed-perfection framework; blanket same-day perfection demands may be impractical.
  • Indemnity and expense allocation: sponsor-side risk increases if indemnity or expense reimbursement is open-ended, uncapped, or missing customary conduct carve-outs.
  • Clear market and syndication restrictions: any restriction on syndication communications or a post-closing tail should be assessed for breadth, duration, and operational effect on marketing.
  • Use controlling authority only where the source package invokes a specific statute, regulation, rule, or defined market standard; otherwise frame conclusions as transactional convention rather than legal doctrine.

4. Analytical scaffolds

  1. Map the deal timetable
  • Identify the outside date for commitment availability, the expected signing-to-closing path, and any marketing or syndication period.
  • Flag any date mismatch that could cause the financing to expire or become unstable before funding.
  1. Test funding firmness
  • Isolate every condition to funding and classify it as customary, negotiable, or sponsor-unfriendly.
  • Separate target-specific conditions from broad market-outs, then assess the practical discretion each gives the lender.
  1. Decompose flex
  • Review all flex provisions in one pass: price, OID, fee, maturity, collateral, prepayment, and covenant flex.
  • For each flex right, ask whether it is bounded by necessity for syndication or otherwise constrained; if not, flag the degree of lender discretion.
  1. Reconcile conditions and deliverables
  • Compare the commitment letter’s closing conditions with the acquisition agreement summary and any ancillary materials.
  • Flag any condition that appears duplicative, overbroad, internally inconsistent, or not clearly tied to a customary closing deliverable.
  1. Review collateral and post-closing mechanics
  • Determine which perfection steps must be completed at closing and which may be deferred.
  • If no workable post-closing cure period exists for burdensome deliverables, identify the operational risk.
  1. Evaluate indemnity, expenses, and syndication controls
  • Check whether indemnity preserves customary carve-outs for wrongful conduct.
  • Check whether expenses are capped or otherwise bounded.
  • Check whether clear market restrictions or information controls are unusually broad in scope or duration.
  1. Prioritize by transaction impact
  • Rank the most material issues first: commitment certainty, closing deliverability, syndication flexibility, then economic leakage.
  • Use a concise explanation for why the issue matters to the sponsor’s ability to close or preserve leverage.

5. Vertical / structural / temporal relationships

  • Track how each issue changes across time: commitment signing, marketing, syndication, signing of the merger agreement, closing, and any post-closing cure period.
  • Track how each issue propagates across documents: a clause in the commitment letter may be softened or worsened by the merger agreement summary, fee letter, or term sheet.
  • Where multiple facilities, tranches, or financing sources exist, compare them vertically so that a problem in one piece is not masked by better language in another.
  • If the package contains alternative formulations, note which version controls and whether the alternates create uncertainty.
  • If the source documents use different defined terms for the same concept, reconcile them before drafting the issue.

6. Output structure conventions

  • Draft a prioritized issues memo from the sponsor’s perspective; do not present a generic contract summary.
  • Use a short executive summary first, focused on the issues most likely to affect closing certainty, syndicationability, and economics.
  • Define a single ordinal severity scale at the top and apply it uniformly to every issue entry.
  • For each issue, include: the provision or concept, the concern, the related document interaction, the downstream sponsor impact, a severity label, and a recommended resolution.
  • Close each issue with a concrete sponsor-side consequence and an action-oriented fix; avoid issues that stop at description.
  • If the source materials identify specific governing law, regulation, rule, or market authority relevant to a point, cite it by name and section in the issue discussion.
  • End with a Recommended Actions block that assigns an imperative next step, the responsible role, and a timing anchor tied to the signing, marketing, or closing process.
  • Use conventional memorandum headings rather than a rubric-shaped checklist.

Security

  • Security scanPassed, 96 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/ghost1034/cpaautomation/banking-finance-identify-issues-in-commitment-letter/badge)](https://verified-skill.com/skills/ghost1034/cpaautomation/banking-finance-identify-issues-in-commitment-letter)

Something wrong with this skill or its page? Tell us.