[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77EMDAMW9B2SZE33DFM8NHG":3,"skill-same:01M77EMDAMW9B2SZE33DFM8NHG":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M77EMDAMW9B2SZE33DFM8NHG","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.","haresh-sai06\u002FSapSynk-AI","haresh-sai06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180730984?v=4","01M75NJVH4TXYCE7FW7YVMSVFF","Haresh Sainaath S","01M75NJVHTCW1Z2P6MNCYGNSTJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__ma-playbook-2\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29},"Alireza Rezvani","ma-strategy",1772668800000,"1.0.0","c-level","main","835716bfbede9677a779d77bfd04befb81c069ac","skills\u002Fclaude__ma-playbook-2","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI","https:\u002F\u002Fgithub.com\u002Fharesh-sai06","https:\u002F\u002Fharesh-sainaath.live\u002F","I am a Student pursuing Artificial Intelligence and Machine Learning at Sri Krishna College of Technology,Coimbatore.","2026-06-13 22:42:28",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add haresh-sai06\u002FSapSynk-AI --skill ma-playbook",{"tool":44,"command":45},"bunx","bunx skills add haresh-sai06\u002FSapSynk-AI --skill ma-playbook",{"tool":47,"command":48},"pnpm","pnpm dlx skills add haresh-sai06\u002FSapSynk-AI --skill ma-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__ma-playbook-2\u002FSKILL.md",true,[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77GQ5PRFQMV3QBDAQPCSXJB","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__youtube-full-2\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77GPXXAB3Y8ZNG919MD4703","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__x-twitter-growth-2\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77GPSS7AFYH90Y5S6XHRXZW","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__write-a-skill-2\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77GPKB6HJS2X5XK03649C6R","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__workflow-builder-2\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77GP31EFXE1KS38XBZ1J9MN","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__webinar-marketing-2\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77GNNA22HWXX6CEQQ3JY2YB","vpe-advisor","VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad\u002Ftribe\u002Fchapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__vpe-advisor-2\u002FSKILL.md",[],[]]