基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/lev-os/agents --skill cold-start-problem命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | cold-start-problem |
| description | Five-stage framework for launching and scaling network effect products from zero to defensible moat |
Andrew Chen's Cold Start Theory, developed through 3 years of research and hundreds of interviews with founders of LinkedIn, Uber, Airbnb, Tinder, and other network-effect companies, provides a systematic approach to the chicken-and-egg problem: how do you build value in a networked product when value comes from users, but users won't join without existing value? The framework breaks network effect growth into 5 stages: (1) Cold Start Problem, (2) Tipping Point, (3) Escape Velocity, (4) Hitting the Ceiling, (5) The Moat. Success requires solving each stage's unique challenge.
Start with the smallest viable network that delivers value - often a single city, campus, or company. Don't launch everywhere at once. Identify the "hard side" (supply in marketplaces) and over-index on recruiting them. Example: Facebook launched only at Harvard, Uber started in San Francisco with black car services, Tinder launched at USC sorority parties.
Use one of four proven strategies: (a) "Come for the tool, stay for the network" - build single-player utility first, (b) Fake it with bots/manual curation (Reddit founders), (c) Subsidize hard side with payments (Uber driver guarantees), (d) Invite-only scarcity (Clubhouse, Gmail). Get to the tipping point where network provides more value than tool. Example: Instagram was a photo editing tool before becoming social, LinkedIn was resume builder before becoming network.
Demonstrate that adding users makes product exponentially more valuable, not linearly. Measure network density and engagement increasing as network grows. Hard side should be getting enough demand to stay engaged, easy side should be getting enough supply to find value. Example: Tipping point is when 60%+ of Uber requests get drivers in <5 minutes, or when Airbnb has 100+ listings per neighborhood.
Clone the successful atomic network to adjacent markets using a playbook. Build "network of networks" where each geography/vertical operates semi-independently but benefits from cross-network learnings and brand. Prioritize markets by network potential, not just size. Example: Uber's city-by-city launch playbook, Airbnb's neighborhood-by-neighborhood density strategy.
Every network hits natural limits: market saturation, engagement plateau, quality degradation from too many users, or competition fragmenting the network. Diagnose which ceiling you've hit. Responses: (a) Add new use cases, (b) Go upmarket/downmarket, (c) Geographic expansion, (d) Acquire competitors, (e) Launch new atomic networks. Example: LinkedIn added job postings when professional networking saturated, Uber added Eats when rides plateaued.
Layer defensive mechanisms beyond network effects: (a) Engagement effects (product gets stickier with use), (b) Acquisition effects (users invite others virally), (c) Economic effects (lower costs/higher quality at scale). Create anti-network effects against competitors (users multi-tenant, quality degrades). Example: Airbnb's reviews create trust moat, Uber's routing data creates economic moat, WhatsApp's cross-platform messaging creates engagement moat.
Situation: Launching a professional services marketplace (design, legal, consulting) connecting freelancers with companies.
Application:
Outcome: Reached 10,000 freelancers and $50M GMV in 18 months, vs. competitor who launched nationwide simultaneously and achieved 1,000 freelancers and $2M GMV in same timeframe due to lack of network density.
Routes adaptive multi-agent deliberation with fractal context cycles. Use when using /cdo, think/deep/debug/parliament work, or long runs paired with autoresearch scheduling.
Use when you need an evidence-first provenance report from `cass`, repo docs, `.lev`, `~/.agents/diagrams`, `qmd`, or Grep/Glob tools.
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher query examples, edge types, how to use search_graph.