Skip to content
FunCoding

Search

Search docs, Skills and MCP

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.

AI 与智能体1.4kskills/acquirer-red-team/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/mohitagw15856/pm-claude-skills/acquirer-red-team/install.md ,按里面的步骤帮我安装这个 Skill。

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.)

Not quite this? Use red-team-my-plan when you want a general stress test of a plan rather than diligence preparation.

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: The Five Hunting Grounds

CategoryWhat chips priceTypical chip size
Revenue qualityNon-recurring dressed as recurring, discount-bought renewals, related-party revenue, pilot revenue counted as land-and-expandMultiple compression — the biggest lever
ConcentrationAny customer >15–20%, channel dependence, one geographyEscrow/earnout territory
Key-person riskFounder-held relationships, single-maintainer systems, no second-in-commandRetention packages carved from YOUR proceeds
Tech & IPUn-transferable licenses, unclear IP assignment (contractors!), tech debt that implies post-close spendDollar-for-dollar price cuts
Legal & complianceOpen disputes, data-protection exposure, misclassified contractors, missing customer consents for assignmentIndemnities, holdbacks, or walk-aways

Per finding, estimate the chip as a range and mechanism (multiple compression / holdback / earnout shift / retention carve-out). Ranges must be defensible from the input; label all assumptions.

Output Format


Project [codename]: Diligence Red Flags — INTERNAL

Simulation — a plausible adversarial reading, not a prediction or financial advice.

Summary Box

Asking frame · our current view · total identified chips (range) · walk-away risks: [n]

Findings

#CategoryFindingEvidence we'd requestPrice mechanismChip estimate

The Retrade Script

[The exact paragraph the corp-dev lead says on the call for finding #1.]

Debrief — out of character

FindingFixable pre-process?Fix and time-to-fixOr: pre-disclose how

One paragraph: the order of operations for the next two quarters, and the one finding to pre-disclose rather than fix (credibility is also an asset).

Route through your M&A counsel and banker before a real process — this is a stress test, not deal advice.


Quality Checks

  • Every finding traces to the supplied facts or a labeled assumption — no invented skeletons
  • Chip estimates carry a mechanism, not just a number
  • Revenue quality is examined first and hardest — it moves the multiple
  • The debrief distinguishes fixable / disclose-and-frame / structural honestly
  • Retention-package math is called out as coming from the seller's proceeds

Anti-Patterns

  • Do not pull punches — the user can get cheerleading from their banker
  • Do not produce findings without price mechanics; "risk" without a chip is noise
  • Do not recommend hiding anything — the debrief may only fix or pre-disclose; concealment discovered in DD kills deals and worse
  • Do not treat PE and strategic buyers identically if the frame is known — they chip differently
  • Do not stay in character in the debrief

Example Trigger Phrases

  • "Red-team my company before a sale."
  • "How will an acquirer attack our valuation?"
  • "What will DD find?"

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents