Agent skill · Security

acquirer-red-team

Simulate the acquirer's diligence team hunting for reasons to cut your price — their internal red-flags memo with a price-chip estimate per finding. Use when asked to red-team my company before a sale, how will an acquirer attack our valuation, pre-diligence audit, or what will DD find. Produces the acquirer's internal memo (revenue quality, key-person, tech debt, concentration, legal) and a debrief on which flags are fixable before a process.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill acquirer-red-team --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/acquirer-red-team/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

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

From the SKILL.md

# Acquirer Red Team Skill Every acquisition has two diligence processes: the polite one in the data room, and the internal one where the deal team lists reasons to retrade the price. This skill runs the second one early. (The mirror-image skill is `financial-due-diligence` — that's you examining others; this is them examining you.) ## What This Skill Produces - **The internal red-flags memo** — what the acquirer's team flags, category by category, with a price-chip estimate per finding - **The retrade script** — the sentence they'll use to reopen price for the biggest flag - **The debrief** — out of character: which flags are fixable pre-process, in what order, and which you must simply pre-disclose ## Required Inputs Ask for these if not provided: - **The business** — revenue (recurring vs one-time), growth, team size, customer count and concentration, stack age, anything sensitive the user already knows about - **The deal frame** (optional) — strategic vs PE buyer, rough multiple expectation; default to a strategic acquirer - **Skeletons** (optional but powerful) — the things the user hopes nobody asks about; the simulation is only as useful as this input is honest ## Framework:

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Five Hunting Grounds
  4. Output Format
  5. Summary Box
  6. Findings
  7. The Retrade Script
  8. Debrief — out of character
  9. Quality Checks
  10. Anti-Patterns
Ships with 1 file
  • references/worked-example.md
More from pm-claude-skills
All skills →
About this skill
What does the acquirer-red-team skill do?

Simulate the acquirer's diligence team hunting for reasons to cut your price — their internal red-flags memo with a price-chip estimate per finding. Use when asked to red-team my company before a sale, how will an acquirer attack our valuation, pre-diligence audit, or what will DD find. Produces the acquirer's internal memo (revenue quality, key-person, tech debt, concentration, legal) and a debrief on which flags are fixable before a process.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill acquirer-red-team --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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