Agent skill · Audited from source
deal-tracker
skill · anthropics/financial-servicesApache-2.0 licenceAudited 29 Oct 2026 · source 1a9a359bc586
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 1a9a359bc586 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Track multiple live deals with milestones, deadlines, action items, and status updates. Maintains a deal pipeline view and surfaces upcoming deadlines and overdue items. Use when managing a book of business, tracking…
Cite
Cite this page
ModelsAtlas. “deal-tracker (anthropics/financial-services)”. Retrieved 29 Oct 2026. https://modelsatlas.com/skills/anthropics/deal-tracker
Trust audit
Audit 0.4.1 · source read 29 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 1a9a359bc586 · 29 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisheranthropics GitHub organizationOwner of the repository this skill is read from
- Source folderanthropics/financial-services/plugins/vertical-plugins/investment-banking/skills/deal-trackerThe exact folder we audited
- LicenceApache-2.0As the repository states it
- Commit pinned for this verdict1a9a359bc586A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Track multiple live deals with milestones, deadlines, action items, and status updates. Maintains a deal pipeline view and surfaces upcoming deadlines and overdue items. Use when managing a book of business, tracking…
--- name: deal-tracker description: Track multiple live deals with milestones, deadlines, action items, and status updates. Maintains a deal pipeline view and surfaces upcoming deadlines and overdue items. Use when managing a book of business, tracking process milestones, or preparing for weekly deal reviews. Triggers on "deal tracker", "deal status", "where are we on", "process update", "deal pipeline", or "weekly deal review". --- # Deal Tracker ## Workflow ### Step 1: Deal Setup For each deal, capture: - **Deal name / code name**: Project [Name] - **Client**: Seller or buyer name - **Deal type**: Sell-side, buy-side, financing, restructuring - **Role**: Lead advisor, co-advisor, fairness opinion - **Deal size**: Expected enterprise value - **Stage**: Pre-mandate → Engaged → Marketing → IOI → Diligence → Final bids → Signing → Close - **Team**: MD, VP, Associate, Analyst assigned - **Key dates**: Engagement date, CIM distribution, IOI deadline, management meetings, final bid deadline, target close ### Step 2: Milestone Tracking Track key milestones per deal: | Milestone | Target Date | Actual Date | Status | Notes | |-----------|------------|-------------|--------|-------| | Engagement letter signed | | | | | | CIM / teaser drafted | | | | | | Buyer list approved | | | | | | Teaser distributed | | | | | | NDA execution | | | | | | CIM distributed | | | | | | IOI deadline | | | | | | IOIs received / reviewed | | | | | | Shortlist selected | | | | | | Management meetings | | | | | | Data room opened | | | | | | Final bid deadline | | | | | | Bids received / reviewed | | | | | | Exclusivity granted | | | | | | Confirmatory diligence | | | | | | Purchase agreement signed | | | | | | Regulatory approval | | | | | | Close | | | | | Status: On Track / At Risk / Delayed / Complete ### Step 3: Action Items Maintain a running action item list across all deals: | Action | Deal | Owner | Due Date | Priority | Status | |--------|------|-------|----------|----------|--------| | | | | | P0/P1/P2 | Open/Done/Blocked | ### Step 4: Weekly Deal Review Generate a summary for weekly team meetings: **For each active deal:** 1. One-line status update 2. Key developments this week 3. Upcoming milestones (next 2 weeks) 4. Blockers or risks 5. Action items for next week **Pipeline summary:** - Total active deals by stage - Deals at risk (missed milestones, stalled processes) - New mandates / pitches in pipeline - Expected closings this quarter ### Step 5: Output - Excel workbook with: - Pipeline overview (all deals, one row each) - Per-deal milestone tracker tabs - Action item master list - Weekly review summary - Optional: Markdown summary for email/Slack distribution ## Important Notes - Update the tracker weekly at minimum — stale trackers are worse than no tracker - Flag deals where milestones are slipping — early warning prevents surprises - Action items without owners and due dates don't get done — be specific - The pipeline view should show deal stage, size, and likelihood — useful for revenue forecasting - Keep notes on buyer/investor feedback — patterns in feedback inform strategy adjustments - Archive closed/dead deals separately — keep the active view clean
Excerpt, first 3,229 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 1a9a359
git clone https://github.com/anthropics/financial-services git -C financial-services checkout 1a9a359bc586
The author documents no install command, so this uses the repository directly. Our verdict covers commit 1a9a359bc586 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
1a9a359bc586
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/anthropics/deal-tracker/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Add this badge to your README
[](https://modelsatlas.com/skills/anthropics/deal-tracker/)
<a href="https://modelsatlas.com/skills/anthropics/deal-tracker/"><img src="https://modelsatlas.com/skills/anthropics/deal-tracker/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about deal-tracker
Is deal-tracker safe to install?
What can deal-tracker access on my machine?
How current is this page?
Sources
- github.com/anthropics/financial-services/tree/main/plugins/verti — the audited source at commit 1a9a359bc586 and every finding aboveObserved · 29 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- Is deal-tracker safe to install?
- What can deal-tracker access on my machine?
- How current is this page?