[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5B68A4M28W73GZ5S2C7TS":3,"skill-same:01M7F5B68A4M28W73GZ5S2C7TS":59},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F5B68A4M28W73GZ5S2C7TS","founder-evaluation",null,"Evaluates founding teams for venture investment. Assesses founder-market fit, team composition, co-founder dynamics, execution track record, coachability, and leadership capacity. Used primarily by the Founder Assessor agent.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-founder-assessor\u002Fskills\u002Ffounder-evaluation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: founder-evaluation\ndescription: >\n  Evaluates founding teams for venture investment. Assesses founder-market fit, team composition,\n  co-founder dynamics, execution track record, coachability, and leadership capacity. Used\n  primarily by the Founder Assessor agent.\n---\n\n# Founder Evaluation Skill\n\n## When to Use\n\nOn every deal where team quality is material to the investment decision (all stages, but especially Pre-seed through Series A where the team IS the investment).\n\n---\n\n## Evaluation Protocol\n\n### Step 1 — Founder-Market Fit\n\nThe single most important assessment: does this founder have an unfair advantage in this specific market?\n\n**Unfair advantages (in order of strength):**\n\n1. **Built and sold a company in this exact space before.** They know the customers, the buyers, the channel, and the pitfalls. Strongest possible signal.\n2. **Operated as a senior executive in this domain.** Deep domain knowledge from the buy side — they understand the problem from the inside.\n3. **Technical breakthrough creator.** They invented or deeply understand the core technology. Relevant for deep tech and infrastructure plays.\n4. **Built the same *type* of company before.** They've scaled a marketplace, or built an enterprise sales motion, or managed a hardware supply chain — even if in a different domain.\n5. **Obsessive domain outsider.** No direct experience but demonstrable deep learning and customer obsession. Weakest unfair advantage but sometimes produces the most creative approaches because they're not constrained by \"how it's always been done.\"\n\n**Red flag:** Founder chose this market because it has a large TAM, not because they have a personal connection to the problem. \"We analyzed markets and chose healthcare\" is a weaker signal than \"I spent 10 years as a nurse and this problem made me quit.\"\n\n### Step 2 — Team Composition Assessment\n\n**Key question:** Does the team have all critical capabilities for the next 18 months?\n\n**Minimum viable team by stage:**\n\n| Stage | Must-Have Capabilities |\n|---|---|\n| Pre-seed | Technical ability to build the product + domain knowledge to identify the right product to build |\n| Seed | Technical (CTO-level), product (someone owns what to build), distribution (someone who can get it to customers) |\n| Series A | Above + sales\u002Fgrowth leadership, operational management, ability to recruit senior talent |\n| Series B+ | Above + CFO-caliber finance, VP-level functional leaders, board governance experience |\n\n**Complementarity check:** Do co-founders have overlapping or complementary skills? Overlap creates conflict and gaps. Complementarity creates coverage.\n\n**Founder-role fit:** Is each founder in the role that matches their strength? A technical founder as CEO can work if they're an exceptional communicator. A business founder as CTO never works.\n\n### Step 3 — Co-Founder Dynamics\n\n**Healthy signals:**\n- Clear role delineation (no ambiguity about who owns what)\n- Equitable but not necessarily equal equity split (70\u002F30 is fine if justified; 50\u002F50 with one founder doing more is a time bomb)\n- History of working together before (prior company, prior job, long friendship tested under stress)\n- Complementary working styles (one detail-oriented, one big-picture; one introverted, one extroverted)\n- Ability to disagree constructively in front of the investor\n\n**Warning signals:**\n- Founders can't clearly explain who does what\n- One founder defers to the other on everything (power imbalance)\n- Equity split \"hasn't been finalized\" (unresolved ownership = unresolved commitment)\n- Met recently and decided to start a company together (untested under stress)\n- One founder does all the talking; the other seems disengaged\n\n### Step 4 — Execution Track Record\n\n**What counts as evidence:**\n- Previous startup experience (founded, scaled, exited — even if the exit was modest)\n- Built and shipped products at a company with high standards\n- Led and grown teams (managed 10+ people through a scaling phase)\n- Navigated a crisis (pivot, near-death experience, market downturn) and survived\n- Track record of recruiting strong people (their previous hires went on to do impressive things)\n\n**What doesn't count:**\n- Prestigious employers without evidence of specific impact\n- Degrees and certifications\n- Speaking at conferences or being on podcast circuits\n- Advisory roles without operational involvement\n- Time spent at a successful company without causal contribution\n\n### Step 5 — Coachability and Self-Awareness\n\n**Coachability indicators:**\n- Asks investors and advisors for specific input (not validation)\n- Can articulate their own weaknesses and what they're doing about them\n- Has changed their mind about something important based on evidence\n- Responds to tough questions with curiosity rather than defensiveness\n- References specific advice from mentors\u002Finvestors that changed their approach\n\n**Low coachability indicators:**\n- Defensive when challenged\n- Cannot name a mistake they've made or something they've changed their mind about\n- Dismisses competition or market concerns with \"we're better\"\n- Treats fundraising as the primary measure of success\n- Surrounded by yes-people (board, advisors, team all agree with everything)\n\n### Step 6 — Reference Check Protocol\n\n**Formal references (founder-provided):** Useful as baseline but inherently biased. The founder chose these people.\n\n**Backchannel references (independently sourced):** Far more valuable. Find these through:\n- LinkedIn connections in common\n- Former employees (especially those who left)\n- Co-workers from previous jobs\n- Other founders in the same space\n- Other investors who saw the deal and passed\n\n**Reference check questions:**\n1. \"What's [Founder]'s superpower — the thing they do better than almost anyone?\"\n2. \"If you were building a company in this space, would you want [Founder] on your team? In what role?\"\n3. \"What's the biggest gap in [Founder]'s capabilities? What would you worry about?\"\n4. \"How does [Founder] handle disagreement? Can you give me a specific example?\"\n5. \"Would you invest your own money in [Founder]'s company?\" (This question gets the most honest answers.)\n\n---\n\n## The Pivot Test\n\nThe ultimate founder evaluation question: \"If the current product fails, do I trust this team to find the right next thing?\"\n\nThis matters because most successful startups pivoted at least once. The current product is a hypothesis. The team's judgment, resilience, and market instincts are what actually determine the outcome.\n\n---\n\n## References & Templates\n\n| File | Content |\n|---|---|\n| `references\u002Ffounder-archetypes.md` | Common founder profiles, strengths, risks, and what to watch for |\n| `references\u002Freference-check-protocol.md` | Detailed backchannel reference process and question bank |\n| `templates\u002Ffounder-assessment.md` | Founder evaluation output template |\n","# Founder Evaluation Skill\n\n## When to Use\n\nOn every deal where team quality is material to the investment decision (all stages, but especially Pre-seed through Series A where the team IS the investment).\n\n---\n\n## Evaluation Protocol\n\n### Step 1 — Founder-Market Fit\n\nThe single most important assessment: does this founder have an unfair advantage in this specific market?\n\n**Unfair advantages (in order of strength):**\n\n1. **Built and sold a company in this exact space before.** They know the customers, the buyers, the channel, and the pitfalls. Strongest possible signal.\n2. **Operated as a senior executive in this domain.** Deep domain knowledge from the buy side — they understand the problem from the inside.\n3. **Technical breakthrough creator.** They invented or deeply understand the core technology. Relevant for deep tech and infrastructure plays.\n4. **Built the same *type* of company before.** They've scaled a marketplace, or built an enterprise sales motion, or managed a hardware supply chain — even if in a different domain.\n5. **Obsessive domain outsider.** No direct experience but demonstrable deep learning and customer obsession. Weakest unfair advantage but sometimes produces the most creative approaches because they're not constrained by \"how it's always been done.\"\n\n**Red flag:** Founder chose this market because it has a large TAM, not because they have a personal connection to the problem. \"We analyzed markets and chose healthcare\" is a weaker signal than \"I spent 10 years as a nurse and this problem made me quit.\"\n\n### Step 2 — Team Composition Assessment\n\n**Key question:** Does the team have all critical capabilities for the next 18 months?\n\n**Minimum viable team by stage:**\n\n| Stage | Must-Have Capabilities |\n|---|---|\n| Pre-seed | Technical ability to build the product + domain knowledge to identify the right product to build |\n| Seed | Technical (CTO-level), product (someone owns what to build), distribution (someone who can get it to customers) |\n| Series A | Above + sales\u002Fgrowth leadership, operational management, ability to recruit senior talent |\n| Series B+ | Above + CFO-caliber finance, VP-level functional leaders, board governance experience |\n\n**Complementarity check:** Do co-founders have overlapping or complementary skills? Overlap creates conflict and gaps. Complementarity creates coverage.\n\n**Founder-role fit:** Is each founder in the role that matches their strength? A technical founder as CEO can work if they're an exceptional communicator. A business founder as CTO never works.\n\n### Step 3 — Co-Founder Dynamics\n\n**Healthy signals:**\n- Clear role delineation (no ambiguity about who owns what)\n- Equitable but not necessarily equal equity split (70\u002F30 is fine if justified; 50\u002F50 with one founder doing more is a time bomb)\n- History of working together before (prior company, prior job, long friendship tested under stress)\n- Complementary working styles (one detail-oriented, one big-picture; one introverted, one extroverted)\n- Ability to disagree constructively in front of the investor\n\n**Warning signals:**\n- Founders can't clearly explain who does what\n- One founder defers to the other on everything (power imbalance)\n- Equity split \"hasn't been finalized\" (unresolved ownership = unresolved commitment)\n- Met recently and decided to start a company together (untested under stress)\n- One founder does all the talking; the other seems disengaged\n\n### Step 4 — Execution Track Record\n\n**What counts as evidence:**\n- Previous startup experience (founded, scaled, exited — even if the exit was modest)\n- Built and shipped products at a company with high standards\n- Led and grown teams (managed 10+ people through a scaling phase)\n- Navigated a crisis (pivot, near-death experience, market downturn) and survived\n- Track record of recruiting strong people (their previous hires went on to do impressive things)\n\n**What doesn't count:**\n- Prestigious employers without evidence of specific impact\n- Degrees and certifications\n- Speaking at conferences or being on podcast circuits\n- Advisory roles without operational involvement\n- Time spent at a successful company without causal contribution\n\n### Step 5 — Coachability and Self-Awareness\n\n**Coachability indicators:**\n- Asks investors and advisors for specific input (not validation)\n- Can articulate their own weaknesses and what they're doing about them\n- Has changed their mind about something important based on evidence\n- Responds to tough questions with curiosity rather than defensiveness\n- References specific advice from mentors\u002Finvestors that changed their approach\n\n**Low coachability indicators:**\n- Defensive when challenged\n- Cannot name a mistake they've made or something they've changed their mind about\n- Dismisses competition or market concerns with \"we're better\"\n- Treats fundraising as the primary measure of success\n- Surrounded by yes-people (board, advisors, team all agree with everything)\n\n### Step 6 — Reference Check Protocol\n\n**Formal references (founder-provided):** Useful as baseline but inherently biased. The founder chose these people.\n\n**Backchannel references (independently sourced):** Far more valuable. Find these through:\n- LinkedIn connections in common\n- Former employees (especially those who left)\n- Co-workers from previous jobs\n- Other founders in the same space\n- Other investors who saw the deal and passed\n\n**Reference check questions:**\n1. \"What's [Founder]'s superpower — the thing they do better than almost anyone?\"\n2. \"If you were building a company in this space, would you want [Founder] on your team? In what role?\"\n3. \"What's the biggest gap in [Founder]'s capabilities? What would you worry about?\"\n4. \"How does [Founder] handle disagreement? Can you give me a specific example?\"\n5. \"Would you invest your own money in [Founder]'s company?\" (This question gets the most honest answers.)\n\n---\n\n## The Pivot Test\n\nThe ultimate founder evaluation question: \"If the current product fails, do I trust this team to find the right next thing?\"\n\nThis matters because most successful startups pivoted at least once. The current product is a hypothesis. The team's judgment, resilience, and market instincts are what actually determine the outcome.\n\n---\n\n## References & Templates\n\n| File | Content |\n|---|---|\n| `references\u002Ffounder-archetypes.md` | Common founder profiles, strengths, risks, and what to watch for |\n| `references\u002Freference-check-protocol.md` | Detailed backchannel reference process and question bank |\n| `templates\u002Ffounder-assessment.md` | Founder evaluation output template |\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fvc-founder-assessor\u002Fskills\u002Ffounder-evaluation","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill founder-evaluation",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill founder-evaluation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill founder-evaluation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-founder-assessor\u002Fskills\u002Ffounder-evaluation\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Ffounder-archetypes.md","REFERENCE","参考文档",6915,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-founder-assessor\u002Fskills\u002Ffounder-evaluation\u002Freferences\u002Ffounder-archetypes.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Freference-check-protocol.md",5966,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-founder-assessor\u002Fskills\u002Ffounder-evaluation\u002Freferences\u002Freference-check-protocol.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"templates\u002Ffounder-assessment.md",2825,"https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fvc-founder-assessor\u002Fskills\u002Ffounder-evaluation\u002Ftemplates\u002Ffounder-assessment.md",[60,67,74,81,88,95],{"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},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\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},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\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},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\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},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\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},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]