Acquirer Red Team logo

Acquirer Red Team

CommunityPopular
mohitagw15856
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.

Overview

Publishermohitagw15856
Repositorypm-claude-skills
Skill nameacquirer-red-team
Stars
1.4K
Forks
240
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mohitagw15856 on GitHub. Read the source before you install it.

Installation

Install the Acquirer Red Team AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p .claude/skills
cp -r /tmp/pm-claude-skills/exports/openclaw/acquirer-red-team .claude/skills/acquirer-red-team
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Acquirer Red Team in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Acquirer Red Team on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Acquirer Red Team is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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: 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

Frequently asked questions

What does the Acquirer Red Team AI 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.

Why use Acquirer Red Team on TypingMind?

Because you install it once and use it with any model. Acquirer Red Team is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Acquirer Red Team in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/acquirer-red-team. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Acquirer Red Team?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Acquirer Red Team?

As many as you like. As long as a model supports skills, you can use Acquirer Red Team with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Acquirer Red Team AI skill free?

Yes. It is published on GitHub by mohitagw15856 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇