What does this skill do, and when should you use it?
Deal Tracker is designed for investment-banking teams managing multiple active transactions. It records deal setup details, process stages, key milestones, and cross-deal action items, then prepares a weekly deal-review summary. It covers sell-side, buy-side, financing, and restructuring work, including lead-advisor, co-advisor, and fairness-opinion roles. The documented output is an Excel workbook, with an optional Markdown summary for email or Slack.
Captures the deal name, client, deal type, advisory role, expected enterprise value, stage, assigned team, and key dates; maintains milestone tables with target dates, actual dates, statuses, and notes from engagement through close; keeps a master action-item list with deal, owner, due date, priority, and status; generates per-deal weekly updates covering current status, developments, next-two-week milestones, blockers or risks, and next-week actions; and summarizes active deals by stage, at-risk processes, new mandates or pitches, and expected quarterly closings.
- An investment-banking VP managing several M&A processes needs a concise status pack for the weekly team meeting.
- A sell-side deal team moving through marketing, management meetings, and final bids needs to monitor buyer-process milestones and overdue items.
- A buy-side or financing advisory team needs consistent owners, priorities, and due dates across multiple live transactions.
- An investment-banking MD wants a pipeline view showing deal stage, size, and likelihood-related information for revenue forecasting.
How do you install this skill?
- Do not treat this skill as a transaction-execution, compliance-approval, or investment-advice tool; authorized personnel should verify all deal data, statuses, and deadlines.
- Before deployment, add controls for sensitive-data access, user confirmation, backup/rollback, date and time-zone handling, input validation, and abnormal cases.
- The workbook output has no representative sample or reproducible generation procedure; manually check field completeness, stage/status mapping, and overdue logic before use.
The source documents collection-level or vertical-plugin installation. In Cowork, open Settings → Plugins → Add plugin, paste https://github.com/anthropics/financial-services, and select the investment-banking vertical. In Claude Code, run claude plugin marketplace add anthropics/financial-services, then claude plugin install investment-banking@claude-for-financial-services. The source does not document a standalone deal-tracker installation command.
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/deal-tracker" ~/.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:
- where are we on,
- weekly deal review.
After installation, trigger it with “deal tracker,” “deal status,” “where are we on,” “process update,” “deal pipeline,” or “weekly deal review.” Example: Weekly deal review for all active sell-side and buy-side deals; flag overdue milestones and assign next-week action items. Provide each deal’s name, client, type, role, size, stage, team, and key dates for a complete tracker.
What are this skill's strengths and limitations?
- Covers deal setup, milestone tracking, action items, weekly review, and closed or dead deal archiving guidance.
- Uses explicit status categories: On Track, At Risk, Delayed, and Complete.
- Provides both a cross-deal pipeline view and an action-item structure requiring owners and due dates.
- The repository is licensed under Apache License 2.0, and its README describes weekly tracker maintenance.
- The SKILL.md provides no specific Excel template, script, or data-import interface.
- The source does not demonstrate automatic access to deal systems, email, data rooms, or external databases.
- Results depend on regular manual updates; the source explicitly warns that stale trackers can be worse than no tracker.
- The skill organizes and summarizes deal progress; it does not execute transactions or provide investment, legal, tax, or accounting advice.
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 |
|---|---|---|---|---|
| Investment Banking Deal Tracker this page ✓ Anthropic · Official | 44 · Not recommended | ★ 40k | 1mo ago | Apache-2.0 |
| M&A Buyer Universe Builder ✓ Anthropic · Official | 52 · Use with care | ★ 40k | 1mo ago | Apache-2.0 |
| Anonymous M&A Teaser ✓ Anthropic · Official | 49 · Use with care | ★ 40k | 1mo ago | Apache-2.0 |
| M&A Process Letter Drafter ✓ Anthropic · Official | 47 · 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 |
How did FollowSkills review this skill?
The skill describes deal tracking and document output only, with no malware, credential theft, or external write behavior; the repository explicitly requires professional review and prohibits automated transaction execution. However, it does not specify handling of sensitive deal data, access isolation, user confirmation, rollback, or data-flow controls, so points are deducted from the mid-level baseline.
The workflow, stages, milestones, and statuses are broadly consistent and the happy path is understandable. It lacks input validation, date/time-zone rules, duplicate handling, abnormal-input feedback, failure recovery, and skill-specific tests. Under the static-review cap of 10, the score remains conservative.
Audience, scenarios, and trigger phrases are reasonably clear for pipeline tracking, milestone management, and weekly reviews. Inputs, non-fit boundaries, transaction-type variations, Chinese-language conventions, and environment requirements are unspecified. The core function has no stated dependency on unreachable overseas services, so no mainland-network deduction is applied.
The document is readable, structured progressively, and uses useful tables; the repository provides an Apache-2.0 license, contribution process, and CI maintenance signals. The skill lacks examples, FAQs, known limitations, versioning, changelog information, and explicit maintenance ownership, preventing a high score.
The workflow covers setup, milestones, action items, and weekly review, and specifies Excel and optional Markdown outputs, so it plausibly completes the core tracking task. However, there is no template, field validation, representative output, or generation mechanism; direct usability still requires manual preparation and review. The static cap is 7.
The source is auditable, and repository CI validates plugin structure while security workflows provide repository-level checks. There are no key-path tests, fixed fixtures, third-party execution results, or independent corroboration for deal-tracker behavior. The static cap is 5.
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 →