Agent skill · Workflow & Productivity

diligence-risk-burndown

Run diligence as a fast risk burn-down: build a ranked risk register (max 4), execute the fastest tests, and produce decision-changing evidence. Use when a deal advances past first meeting.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill diligence-risk-burndown --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 0.2
Declared author: evalops
Requires: Works offline; improved with web access and customer calls; optional Salesforce logging.
Path: skills/analysis/diligence-risk-burndown/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Diligence risk burn-down ## When to use Use this skill when: - A company is past first meeting and needs structured diligence - You need to answer "what could kill this?" quickly - You need customer, product, GTM, and team evidence for an IC memo ## Inputs you should request (only if missing) - Stage + round dynamics (lead? follow? timeline?) - A draft "must be true" list from the first meeting - Access to customer references (including churned / lost deals if possible) - Data room or key docs (deck, pipeline, financial model, product docs) ## Outputs you must produce 1) **Ranked risk register** (MAX 4 RISKS - force prioritization) 2) **Diligence plan** (one fastest test per risk, time-boxed) 3) **Evidence pack** (notes + quotes + data) 4) **Anti-confirmation evidence** (required: churned customer or lost deal call, competitor validation) 5) **Go/No-go recommendation** with rationale Templates: - assets/risk-register.md - assets/diligence-plan.md - assets/customer-call-script.md - assets/product-eval-checklist.md ## Hard rules ### Max 4 risks (non-negotiable) - If you have more than 4 risks, you haven't prioritized. - The discipline is choosing: what are the 4 things that would a

What's inside
Steps it walks through
  1. When to use
  2. Inputs you should request (only if missing)
  3. Outputs you must produce
  4. Hard rules
  5. Max 4 risks (non-negotiable)
  6. One fastest test per risk
  7. Time-box per test
  8. Evidence standard
  9. Procedure
  10. 1) Build the ranked risk register (MAX 4)
  11. 2) Define the fastest falsification test for each risk
  12. 3) Run anti-confirmation diligence (REQUIRED)
  13. 4) Run customer diligence (buyers first)
  14. 5) Product diligence (can it survive reality?)
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the diligence-risk-burndown skill do?

Run diligence as a fast risk burn-down: build a ranked risk register (max 4), execute the fastest tests, and produce decision-changing evidence. Use when a deal advances past first meeting.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill diligence-risk-burndown --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going