Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Due Diligence

ASecurity

Structures and runs a diligence process with a workstream request list, a findings tracker, and a red-flag log.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoapisecurity

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-finance-skills --skill due-diligence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Due Diligence?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Due Diligence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-due-diligence/badge)](https://www.skillsdirectory.com/skills/andreworia-due-diligence)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: due-diligence
description: Structures and runs a diligence process with a workstream request list, a findings tracker, and a red-flag log.
---

# Due Diligence Agent

## When to use
Use this when you must structure and run a diligence process on a target, whether buy-side confirmatory diligence or sell-side vendor diligence. It is the right tool the moment a deal moves past a signed LOI or a data room opens. Reach for it when you need to turn a vague "do diligence" instruction into an organized, owner-assigned process.

## What it does
It produces a diligence request list organized by workstream and a findings tracker that logs every issue with severity, owner, and status, plus a running red-flag log that surfaces deal-threatening items early.

## Method
Diligence checklist and findings log, worked step by step.

1. Frame the scope.
   - Confirm deal type, sector, materiality thresholds, and the investment thesis to prove or disprove.
   - Pitfall: an unbounded request list stalls the process; anchor every ask to a thesis question.

2. Build the request list by workstream: commercial, financial, legal, tax, operational, HR, and IT.
   - Under each, list specific documents and data to pull from the data room or management.
   - Commercial: customer concentration, churn, pipeline. Operational: capacity, supply chain, key facilities.

3. Prioritize quality of earnings in the financial workstream.
   - Revenue recognition, one-time and non-recurring items, working capital trends, and normalized EBITDA with a clean add-back bridge.
   - Watch for aggressive capitalization or channel stuffing that flatters earnings.

4. Cover legal, tax, HR, and IT.
   - Legal and tax: material contracts, change-of-control clauses, litigation, IP ownership, open tax positions.
   - HR: key-person dependencies and retention. IT: systems, security posture, and integration debt.

5. Assign each request an owner and a due date.
   - Track receipt status: outstanding, received, under review, or cleared.
   - Good practice: a single owner per item, never a team, so accountability is clear.

6. Log findings as documents arrive.
   - Capture description, workstream, severity (high, medium, low), potential deal impact (price, structure, walk-away), owner, and status.
   - Severity is about deal impact, not effort: a small dollar item with a legal walk-away trigger is high.

7. Escalate high-severity findings to the red-flag log.
   - Add a one-line thesis on why it threatens value and a recommended mitigation (price adjustment, escrow, indemnity, or condition to close).

8. Roll findings into a diligence summary.
   - Tie each material issue to a proposed action in the purchase agreement or valuation, so diligence directly informs deal terms.

## Inputs
- Deal type (buy-side or vendor) and the target sector
- The core investment thesis to prove or disprove
- Data room access or a document index
- Materiality thresholds and the diligence timeline
- Names of workstream owners on the deal team
- Any prior findings or known issues to carry forward
- Purchase agreement stage, so findings can be routed to terms

## Output format
- A request list grouped by the seven workstreams, each item with an owner and status
- A findings tracker as a prose list, each finding naming its workstream, severity, deal impact, owner, and status
- A red-flag log: a short ranked list of the highest-severity items, each with a recommended mitigation
- A diligence summary mapping material issues to purchase-agreement or valuation actions
- All of the above described in prose, never rendered as literal markdown tables

## Example
For Meridian Foods, a buy-side process, the financial workstream flags a high-severity finding: 38 percent of revenue comes from a single grocery chain whose contract carries a change-of-control termination right. Deal impact is rated high and routed to the red-flag log, with a recommended mitigation of a specific indemnity plus a portion of consideration held in escrow until the contract is reaffirmed. A medium finding notes 4 million of owner add-backs in normalized EBITDA that thin the defensible earnings base. A low finding flags an expiring facility lease, tracked but not deal-threatening, and the summary ties the concentration issue directly to a proposed purchase-price adjustment.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →