[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PR7VA7AXMNKMJ86S2M2Q7":3,"skill-same:01M75PR7VA7AXMNKMJ86S2M2Q7":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75PR7VA7AXMNKMJ86S2M2Q7","ma-playbook",null,"M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fskills\u002Fma-playbook\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"ma-playbook\"\ndescription: \"M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ma-strategy\n  updated: 2026-03-05\n---\n\n# M&A Playbook\n\nFrameworks for both sides of M&A: acquiring companies and being acquired.\n\n## Keywords\nM&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout\n\n## Quick Start\n\n**Acquiring:** Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.\n\n**Being Acquired:** Start with readiness assessment → data room prep → advisor selection → negotiation → transition.\n\n## When You're Acquiring\n\n### Strategic Rationale (answer before anything else)\n- **Buy vs Build:** Can you build this faster\u002Fcheaper? If yes, don't acquire.\n- **Acqui-hire vs Product vs Market:** What are you really buying? Talent? Technology? Customers?\n- **Integration complexity:** How hard is it to merge this into your company?\n\n### Due Diligence Checklist\n| Domain | Key Questions | Red Flags |\n|--------|--------------|-----------|\n| Financial | Revenue quality, customer concentration, burn rate | >30% revenue from 1 customer |\n| Technical | Code quality, tech debt, architecture fit | Monolith with no tests |\n| Legal | IP ownership, pending litigation, contracts | Key IP owned by individuals |\n| People | Key person risk, culture fit, retention risk | Founders have no lockup\u002Fearnout |\n| Market | Market position, competitive threats | Declining market share |\n| Customers | Churn rate, NPS, contract terms | High churn, short contracts |\n\n### Valuation Approaches\n\nThe ranges below are **illustrative, not current market data** — always verify against current market comps before using them in a model or negotiation.\n\n- **Revenue multiple:** Industry-dependent (illustrative range: 2-15x ARR for SaaS, varying with growth rate, NRR, and rate environment)\n- **Comparable transactions:** What similar companies sold for — the most defensible anchor\n- **DCF:** For profitable companies only (most startups: use multiples)\n- **Acqui-hire:** Illustrative range: $1-3M per engineer in hot talent markets\n\n**Sources to verify against (check the latest edition):** the SaaS Capital Index (private SaaS revenue multiples, updated monthly), Software Equity Group (SEG) Annual\u002FQuarterly SaaS M&A Reports (transaction multiples), and Aventis Advisors' SaaS valuation multiples reports. Cross-check at least two before anchoring a price.\n\n### Integration Frameworks\nSee `references\u002Fintegration-playbook.md` for the 100-day integration plan.\n\n## When You're Being Acquired\n\n### Readiness Signals\n- Inbound interest from strategic buyers\n- Market consolidation happening around you\n- Fundraising becomes harder than operating\n- Founder ready for a transition\n\n### Preparation (6-12 months before)\n1. Clean up financials (audited if possible)\n2. Document all IP and contracts\n3. Reduce customer concentration\n4. Lock up key employees\n5. Build the data room\n6. Engage an M&A advisor\n\n### Negotiation Points\n| Term | What to Watch | Your Leverage |\n|------|--------------|---------------|\n| Valuation | Earnout traps (unreachable targets) | Multiple competing offers |\n| Earnout | Milestone definitions, measurement period | Cash-heavy vs earnout-heavy split |\n| Lockup | Duration, conditions | Your replaceability |\n| Rep & warranties | Scope of liability | Escrow vs indemnification cap |\n| Employee retention | Who gets offers, at what terms | Key person dependencies |\n\n## Red Flags (Both Sides)\n\n- No clear strategic rationale beyond \"it's a good deal\"\n- Culture clash visible during due diligence and ignored\n- Key people not locked in before close\n- Integration plan doesn't exist or is \"we'll figure it out\"\n- Valuation based on projections, not actuals\n\n## Verification Loop (before any LOI or signature)\n\nThis skill frames the deal; two sibling skills verify it. Hand off — don't duplicate:\n\n1. **Legal terms** → `general-counsel-advisor`: run the LOI\u002Fterm sheet through `..\u002Fgeneral-counsel-advisor\u002Fscripts\u002Fterm_sheet_analyzer.py` (12-dimension 0-100 score) and the definitive docs through `..\u002Fgeneral-counsel-advisor\u002Fscripts\u002Fcontract_risk_scanner.py` (12 founder-killer patterns: earnout traps, uncapped indemnity, vague IP, etc.). Any 🔴 finding goes to outside counsel before signing.\n2. **Data diligence** → `chief-data-officer-advisor`: run `..\u002Fchief-data-officer-advisor\u002Fscripts\u002Fai_training_data_audit.py` (training-data rights, GDPR Art. 6 basis) and `..\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_asset_valuator.py` (data-asset value, M&A multiplier with carve-out penalties) on the target's data estate. Undocumented consent provenance is a price-reduction or walk-away item.\n3. **Valuation math** → `cfo-advisor` tools for the quantitative model; this playbook stays qualitative.\n\nLoop the findings back into the negotiation-points table above before the next counter.\n\n## Integration with C-Suite Roles\n\n| Role | Contribution to M&A |\n|------|-------------------|\n| CEO | Strategic rationale, negotiation lead |\n| CFO | Valuation, deal structure, financing |\n| GC | LOI\u002Fterm sheet review, contract risk scan, regulatory triggers |\n| CDO | Data diligence: training-data rights, data-asset valuation |\n| CTO | Technical due diligence, integration architecture |\n| CHRO | People due diligence, retention planning |\n| COO | Integration execution, process merge |\n| CPO | Product roadmap impact, customer overlap |\n\n## Resources\n- `references\u002Fintegration-playbook.md` — 100-day post-acquisition integration plan\n- `references\u002Fdue-diligence-checklist.md` — comprehensive DD checklist by domain\n- `..\u002Fgeneral-counsel-advisor\u002FSKILL.md` — term sheet analyzer + contract risk scanner\n- `..\u002Fchief-data-officer-advisor\u002FSKILL.md` — data diligence + data-asset valuation\n","# M&A Playbook\n\nFrameworks for both sides of M&A: acquiring companies and being acquired.\n\n## Keywords\nM&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout\n\n## Quick Start\n\n**Acquiring:** Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.\n\n**Being Acquired:** Start with readiness assessment → data room prep → advisor selection → negotiation → transition.\n\n## When You're Acquiring\n\n### Strategic Rationale (answer before anything else)\n- **Buy vs Build:** Can you build this faster\u002Fcheaper? If yes, don't acquire.\n- **Acqui-hire vs Product vs Market:** What are you really buying? Talent? Technology? Customers?\n- **Integration complexity:** How hard is it to merge this into your company?\n\n### Due Diligence Checklist\n| Domain | Key Questions | Red Flags |\n|--------|--------------|-----------|\n| Financial | Revenue quality, customer concentration, burn rate | >30% revenue from 1 customer |\n| Technical | Code quality, tech debt, architecture fit | Monolith with no tests |\n| Legal | IP ownership, pending litigation, contracts | Key IP owned by individuals |\n| People | Key person risk, culture fit, retention risk | Founders have no lockup\u002Fearnout |\n| Market | Market position, competitive threats | Declining market share |\n| Customers | Churn rate, NPS, contract terms | High churn, short contracts |\n\n### Valuation Approaches\n\nThe ranges below are **illustrative, not current market data** — always verify against current market comps before using them in a model or negotiation.\n\n- **Revenue multiple:** Industry-dependent (illustrative range: 2-15x ARR for SaaS, varying with growth rate, NRR, and rate environment)\n- **Comparable transactions:** What similar companies sold for — the most defensible anchor\n- **DCF:** For profitable companies only (most startups: use multiples)\n- **Acqui-hire:** Illustrative range: $1-3M per engineer in hot talent markets\n\n**Sources to verify against (check the latest edition):** the SaaS Capital Index (private SaaS revenue multiples, updated monthly), Software Equity Group (SEG) Annual\u002FQuarterly SaaS M&A Reports (transaction multiples), and Aventis Advisors' SaaS valuation multiples reports. Cross-check at least two before anchoring a price.\n\n### Integration Frameworks\nSee `references\u002Fintegration-playbook.md` for the 100-day integration plan.\n\n## When You're Being Acquired\n\n### Readiness Signals\n- Inbound interest from strategic buyers\n- Market consolidation happening around you\n- Fundraising becomes harder than operating\n- Founder ready for a transition\n\n### Preparation (6-12 months before)\n1. Clean up financials (audited if possible)\n2. Document all IP and contracts\n3. Reduce customer concentration\n4. Lock up key employees\n5. Build the data room\n6. Engage an M&A advisor\n\n### Negotiation Points\n| Term | What to Watch | Your Leverage |\n|------|--------------|---------------|\n| Valuation | Earnout traps (unreachable targets) | Multiple competing offers |\n| Earnout | Milestone definitions, measurement period | Cash-heavy vs earnout-heavy split |\n| Lockup | Duration, conditions | Your replaceability |\n| Rep & warranties | Scope of liability | Escrow vs indemnification cap |\n| Employee retention | Who gets offers, at what terms | Key person dependencies |\n\n## Red Flags (Both Sides)\n\n- No clear strategic rationale beyond \"it's a good deal\"\n- Culture clash visible during due diligence and ignored\n- Key people not locked in before close\n- Integration plan doesn't exist or is \"we'll figure it out\"\n- Valuation based on projections, not actuals\n\n## Verification Loop (before any LOI or signature)\n\nThis skill frames the deal; two sibling skills verify it. Hand off — don't duplicate:\n\n1. **Legal terms** → `general-counsel-advisor`: run the LOI\u002Fterm sheet through `..\u002Fgeneral-counsel-advisor\u002Fscripts\u002Fterm_sheet_analyzer.py` (12-dimension 0-100 score) and the definitive docs through `..\u002Fgeneral-counsel-advisor\u002Fscripts\u002Fcontract_risk_scanner.py` (12 founder-killer patterns: earnout traps, uncapped indemnity, vague IP, etc.). Any 🔴 finding goes to outside counsel before signing.\n2. **Data diligence** → `chief-data-officer-advisor`: run `..\u002Fchief-data-officer-advisor\u002Fscripts\u002Fai_training_data_audit.py` (training-data rights, GDPR Art. 6 basis) and `..\u002Fchief-data-officer-advisor\u002Fscripts\u002Fdata_asset_valuator.py` (data-asset value, M&A multiplier with carve-out penalties) on the target's data estate. Undocumented consent provenance is a price-reduction or walk-away item.\n3. **Valuation math** → `cfo-advisor` tools for the quantitative model; this playbook stays qualitative.\n\nLoop the findings back into the negotiation-points table above before the next counter.\n\n## Integration with C-Suite Roles\n\n| Role | Contribution to M&A |\n|------|-------------------|\n| CEO | Strategic rationale, negotiation lead |\n| CFO | Valuation, deal structure, financing |\n| GC | LOI\u002Fterm sheet review, contract risk scan, regulatory triggers |\n| CDO | Data diligence: training-data rights, data-asset valuation |\n| CTO | Technical due diligence, integration architecture |\n| CHRO | People due diligence, retention planning |\n| COO | Integration execution, process merge |\n| CPO | Product roadmap impact, customer overlap |\n\n## Resources\n- `references\u002Fintegration-playbook.md` — 100-day post-acquisition integration plan\n- `references\u002Fdue-diligence-checklist.md` — comprehensive DD checklist by domain\n- `..\u002Fgeneral-counsel-advisor\u002FSKILL.md` — term sheet analyzer + contract risk scanner\n- `..\u002Fchief-data-officer-advisor\u002FSKILL.md` — data diligence + data-asset valuation\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28},"Alireza Rezvani","ma-strategy",1772668800000,"1.0.0","c-level","main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fc-level-advisor\u002Fskills\u002Fma-playbook","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill ma-playbook",{"tool":41,"command":42},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill ma-playbook",{"tool":44,"command":45},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill ma-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fskills\u002Fma-playbook\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdue-diligence-checklist.md","REFERENCE","参考文档",4943,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fskills\u002Fma-playbook\u002Freferences\u002Fdue-diligence-checklist.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fintegration-playbook.md",5733,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fc-level-advisor\u002Fskills\u002Fma-playbook\u002Freferences\u002Fintegration-playbook.md",[60,67,73,80,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]