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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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-planwhen you want a general stress test of a plan rather than diligence preparation.
Ask for these if not provided:
| Category | What chips price | Typical chip size |
|---|---|---|
| Revenue quality | Non-recurring dressed as recurring, discount-bought renewals, related-party revenue, pilot revenue counted as land-and-expand | Multiple compression — the biggest lever |
| Concentration | Any customer >15–20%, channel dependence, one geography | Escrow/earnout territory |
| Key-person risk | Founder-held relationships, single-maintainer systems, no second-in-command | Retention packages carved from YOUR proceeds |
| Tech & IP | Un-transferable licenses, unclear IP assignment (contractors!), tech debt that implies post-close spend | Dollar-for-dollar price cuts |
| Legal & compliance | Open disputes, data-protection exposure, misclassified contractors, missing customer consents for assignment | Indemnities, 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.
Simulation — a plausible adversarial reading, not a prediction or financial advice.
Asking frame · our current view · total identified chips (range) · walk-away risks: [n]
| # | Category | Finding | Evidence we'd request | Price mechanism | Chip estimate |
|---|
[The exact paragraph the corp-dev lead says on the call for finding #1.]
| Finding | Fixable pre-process? | Fix and time-to-fix | Or: 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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
日本語の概要は準備中です。原文の説明を表示しています。
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
日本語の概要は準備中です。原文の説明を表示しています。
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
日本語の概要は準備中です。原文の説明を表示しています。
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
日本語の概要は準備中です。原文の説明を表示しています。
Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
日本語の概要は準備中です。原文の説明を表示しています。