What does this skill do, and when should you use it?
This skill supports drafting correspondence for sell-side M&A processes. It covers initial process letters, first-round IOI instructions, second-round or final bid letters, and management meeting invitations. It addresses timelines, bid requirements, diligence, financing certainty, regulatory analysis, and evaluation criteria. It fits investment-banking teams that need structured transaction communications subject to client and legal review.
Determines the appropriate letter type for the process stage; drafts process overviews, IOI or final-bid requirements, submission details, confidentiality reminders, and banker contacts; adds purchase-agreement markup, financing commitments, remaining diligence, exclusivity, regulatory analysis, personnel terms, binding status, and evaluation criteria for final bids; drafts management-meeting logistics, attendees, agendas, ground rules, materials, and follow-up procedures; produces a professionally formatted Word document with a letterhead placeholder and a track-changes version for client review.
- A sell-side M&A advisor needs an initial process letter and IOI requirements to accompany a teaser or CIM.
- A deal team needs second-round or final-bid instructions after diligence has progressed.
- An investment-banking team needs to standardize requirements for valuation, consideration, financing, timing, and bid evaluation.
- A seller needs a management-meeting invitation covering logistics, agenda, confidentiality, and follow-up questions.
How do you install this skill?
- This is a static review only; the skill and its .docx, tracked-changes, and formatting outputs were not executed or verified.
- Process letters may contain transaction, financing, regulatory, and confidential information, but the skill specifies no concrete handling, access-control, or retention requirements.
- Deadlines, binding language, exclusivity, regulatory provisions, and legal wording require client and counsel review before distribution.
- No Chinese template or mainland-China network reachability evidence is provided; additional localization may be required.
In Cowork, open Settings → Plugins → Add plugin, paste https://github.com/anthropics/financial-services, and select the investment-banking vertical. With Claude Code, run: claude plugin marketplace add anthropics/financial-services; claude plugin install investment-banking@claude-for-financial-services.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/anthropics/financial-services.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/plugins/vertical-plugins/investment-banking/skills/process-letter" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Draft a sell-side M&A initial process letter with IOI requirements, a submission deadline, and bid evaluation criteria.
In a session with the investment-banking vertical installed, use /process-letter or prompt: “Draft a sell-side M&A initial process letter with IOI requirements, a submission deadline, and bid evaluation criteria.” Specific templates and automation parameters are not documented in the source.
What are this skill's strengths and limitations?
- Covers initial, final-bid, and management-meeting correspondence.
- Includes concrete requirements for valuation, consideration, financing, diligence, regulatory matters, and bid evaluation.
- Specifies professional Word formatting, a letterhead placeholder, and a client-review version.
- The source provides no sample outputs, test results, or template files.
- It does not document automatic email delivery, data-room management, or process-tracker maintenance.
- Transaction and legal commitments still require client and legal review.
- Pricing, permission requirements, and broader platform support are not documented.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| M&A Process Letter Drafter this page ✓ Anthropic · Official | 47 · Use with care | ★ 40k | 1mo ago | Apache-2.0 |
| M&A Buyer Universe Builder ✓ Anthropic · Official | 52 · Use with care | ★ 40k | 1mo ago | Apache-2.0 |
| M&A Accretion & Dilution Model ✓ Anthropic · Official | 51 · Use with care | ★ 40k | 1mo ago | Apache-2.0 |
| Model Checker for Financial Audits | 53 · Use with care | ★ 1.8k | 11d ago | Apache-2.0 |
| Financial Data Pack Builder ✓ Anthropic · Official | 45 · Not recommended | ★ 40k | 1mo ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill is limited to drafting process letters and bid instructions and does not claim to send documents, execute transactions, or perform privileged actions. It calls for confidentiality, legal coordination, client approval before sending, and recipient tracking. Deductions reflect missing least-privilege details, sensitive-data handling, data-flow disclosure, isolation, rollback, and dependency-security controls.
The workflow consistently distinguishes initial/IOI, final/second-round, and management-meeting letters, with plausible guidance for each. The score is reduced because inputs, abnormal-input handling, diagnostic failure feedback, templates, and reproducible behavioral tests are absent; the required .docx and tracked-changes outputs have no implementation details.
Trigger phrases, audience, scenarios, and major content areas are reasonably clear, and the expected document format is stated. Points are deducted for unspecified non-fit cases, required inputs, jurisdictional or firm-specific variation, Chinese-language support, and tooling/environment boundaries.
The skill has a readable front matter block, progressive workflow sections, practical notes, and repository-level alignment with the /process-letter command and Apache-2.0 license. The score is reduced because the skill provides no version, changelog, named maintainer, installation/dependency guidance, examples, FAQ, or troubleshooting path.
The guidance covers core process-letter sections, IOI and final-bid requirements, meeting logistics, approval, and process tracking, so it can reduce omission risk. Deductions reflect the absence of concrete templates, representative outputs, or verified .docx/tracked-changes deliverables; substantial editing, formatting, and legal review remain necessary.
The review has pinned-revision source material, README command mapping, an Apache-2.0 license, and repository CI for plugin validation and secret scanning. Points are deducted because the CI does not test this skill's semantic behavior or output quality, and there are no committed behavior tests, third-party execution records, or cross-source corroboration.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →