mcpbeat Sign in

Process Letter Skill for Claude

Draft process letters and bid instructions for sell-side M&A processes. Covers initial indication of interest (IOI) instructions, final bid procedures, and management meeting logistics. Triggers on "process letter", "bid instructions", "IOI letter", "bid procedures", "final round letter", or "management meeting invite".

907 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
33987
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/financial-services --skill process-letter

The instruction itself

8 sections, as written by the author

Process Letter

Workflow

Step 1: Determine Letter Type

  • Initial process letter: Sent with teaser/CIM to outline the process and IOI requirements
  • IOI instructions: Specific requirements for first-round indications of interest
  • Second round / final bid letter: Instructions for submitting binding offers after diligence
  • Management meeting invitation: Logistics for in-person management presentations

Step 2: Initial Process Letter / IOI Instructions

Header:

  • Date, deal code name
  • "Confidential"
  • Addressed to prospective buyer

Sections:

  • Introduction: Brief overview of the opportunity and the seller's objectives
  • Process Overview: Timeline, key dates, expected number of rounds
  • IOI Requirements: What to include in the initial indication:
  • Proposed valuation range (enterprise value)
  • Consideration form (cash, stock, earnout, rollover)
  • Financing sources and certainty
  • Key due diligence requirements
  • Indicative timeline to close
  • Any conditions or contingencies
  • Brief description of the buyer and strategic rationale
  • Submission Details: Where to send, deadline (date and time), format
  • Confidentiality Reminder: Reference to NDA, data room access
  • Contact Information: Banker contacts for questions

Step 3: Final Bid / Second Round Letter

Additional requirements beyond IOI:

  • Markup of purchase agreement: Provide the draft SPA/APA and request markup
  • Detailed financing commitments: Committed financing letters required
  • Remaining diligence items: Specify what confirmatory diligence is expected
  • Exclusivity terms: Duration and conditions of any exclusivity period
  • Regulatory analysis: Antitrust filing requirements and timeline
  • Key personnel terms: Employment agreements, compensation, rollover equity
  • Binding vs. non-binding: Clarify what is binding at this stage
  • Evaluation criteria: How bids will be evaluated (price, certainty, speed, fit)

Step 4: Management Meeting Invitation

  • Logistics: Date, time, location (or video link), duration
  • Attendees: Who from the company will present, who from the buyer should attend
  • Agenda: Typical management presentation agenda (overview, financials, operations, growth, Q&A)
  • Ground rules: No recording, confidentiality, questions format
  • Materials: What will be distributed (presentation deck, data room access)
  • Follow-up: Process for submitting additional questions after the meeting

Step 5: Output

  • Word document (.docx) with professional letter formatting
  • Firm letterhead placeholder
  • Track changes version for client review

Important Notes

  • Process letters set the tone for the entire deal — be clear, professional, and organized
  • Deadlines should be firm but reasonable — typically 2-3 weeks for IOIs, 3-4 weeks for final bids
  • Always include the evaluation criteria — buyers want to know how they'll be judged
  • Coordinate with legal on any representations or commitments in the letter
  • Client should review and approve before sending — they may want to adjust tone or terms
  • Keep a log of who received each letter and when — this becomes the process tracker

Other skills for the same job

different authors, same section of the catalogue
Meeting Insights Analyzer
by frostant
×8

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

3k tokens
Slack Gif Creator
by JayZeeDesign
×7

Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".

53k tokens scripts
Developer Growth Analysis
by frostant
×6

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

4k tokens
Skill Share
by frostant
×4

A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

728 tokens
Electron
by vercel-labs
vendor ×2

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

2k tokens
Notion Meeting Intelligence
by openai
vendor ×2

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

18k tokens
Daily Meeting Update
by softaworks
×2

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

8k tokens scripts
Professional Communication
by softaworks
×2

Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.

12k tokens

How to use it

Copy the folder

Take anthropics/process-letter from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.