[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HGWGHC4SW0XYEGRN22091":3,"skill-same:01M71HGWGHC4SW0XYEGRN22091":78},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M71HGWGHC4SW0XYEGRN22091","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.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fma-playbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"ma playbook","playbook","planning","for","strategy","deal structure","use","when","acquisition","deal","structure","2026","integration","negotiation","valuation","2026-11-10 10:12:30",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- **Revenue multiple:** Industry-dependent (2-15x ARR for SaaS)\n- **Comparable transactions:** What similar companies sold for\n- **DCF:** For profitable companies only (most startups: use multiples)\n- **Acqui-hire:** $1-3M per engineer in hot markets\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## 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| 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","# 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- **Revenue multiple:** Industry-dependent (2-15x ARR for SaaS)\n- **Comparable transactions:** What similar companies sold for\n- **DCF:** For profitable companies only (most startups: use multiples)\n- **Acqui-hire:** $1-3M per engineer in hot markets\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## 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| 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",{"name":5,"license":15,"metadata":39,"description":7},{"author":40,"domain":41,"updated":42,"version":43,"category":44},"Alireza Rezvani","ma-strategy",1772668800000,"1.0.0","c-level","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fma-playbook",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill ma-playbook",{"tool":60,"command":61},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill ma-playbook",{"tool":63,"command":64},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill ma-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fma-playbook\u002FSKILL.md",true,[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fdue-diligence-checklist.md","REFERENCE","参考文档",4943,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fma-playbook\u002Freferences\u002Fdue-diligence-checklist.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fintegration-playbook.md",5733,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fma-playbook\u002Freferences\u002Fintegration-playbook.md",[79,111,133,155,174,197],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":110},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,26,105,106,107,108,109],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":110},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[117],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[91,119,120,95,121,122,123,124,104,125,26,126,105,127,128,129,130,131,132,22],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":110},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[139],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[91,141,142,95,143,124,144,26,145,126,105,146,147,148,149,150,151,152,153,154],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":110},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[161],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[163,95,164,151,165,166,167,168,154,169,170,25,26,171,126,105,172,173,106,91],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":110},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000010","后端与接口",[184,185,186,187,143,188,189,190,22,152,124,191,192,144,193,25,194,195,196,26],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":220},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[203],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[205,206,207,208,209,101,210,168,211,104,212,213,26,91,214,215,216,217,218,219],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]