Agent skill

Cold Start Problem

by wondelai in wondelai/skills

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects.

MITAuto-check passed

Install Cold Start Problem

skills CLI
$ npx skills add wondelai/skills --skill cold-start-problem -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wondelai/skills cold-start-problem --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cold-start-problem .claude/skills/cold-start-problem && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cold-start-problem
GitHub stars
2.4k
Token cost
~4.7k tokens
SKILL.md length
2,470 words
Files
6 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects.

  • Works in 5 steps: Network Effects Fundamentals → The Cold Start: Atomic Networks → Solve the Hard Side → …
  • The user mentions network effects
  • SKILL.md covers Core Principle, Scoring, Framework and Common Mistakes, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cold Start Problem is an agent skill from wondelai/skills. Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing…

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/atomic-networks.md`, `references/case-studies.md` and `references/hard-side.md`).

The repository describes itself as: Wondel.ai Agent Skills — Business, Marketing, UX & Coding Frameworks from Bestselling Books. 50 skills + 12 guided journeys for Claude Code, Codex, Cursor & other agentskills.io… The licence is MIT.

When your agent uses it

  • The user mentions network effects
  • Chicken and egg
  • Two-sided marketplace
  • Invite-only launch

Example prompts

  • “The Cold Start Problem”
  • “network effects”
  • “chicken and egg”
  • “/cold-start-problem”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Network Effects Fundamentals
  2. The Cold Start: Atomic Networks
  3. Solve the Hard Side
  4. Tipping Point and Escape Velocity
  5. The Ceiling and the Moat

What it can do on your machine

Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • amazon.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cold Start Problem loads about 4.7k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 199 tokens; SKILL.md has 2,470 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~199
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 2,470 words, ~4,713 tokens.

Download SKILL.mdSave it as .claude/skills/cold-start-problem/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
cold-start-problem
description
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.
license
MIT
metadata.author
wondelai
metadata.version
1.2.0

The Cold Start Problem

A framework for starting and scaling products that live or die by network effects — marketplaces, social apps, messaging, and collaboration tools — distilled from Andrew Chen's The Cold Start Problem. Use it to launch products that are worthless until other users show up, to sequence growth network by network, and to navigate the five stages: the cold start, the tipping point, escape velocity, hitting the ceiling, and the moat.

Core Principle

Network effects start as a liability, not an asset. Value lives in connections between users, and on day one there are none — the same force that makes a dense network unstoppable makes an empty one useless. You don't escape by launching to a market; you escape by building one tiny, complete, self-sustaining network at a time, solving its hard side first, then tipping adjacent networks with a repeatable playbook until the market follows.

Scoring

Goal: 10/10. Rate launch plans and growth strategies for networked products 0-10 against the principles below. Report the current score and the specific changes needed to reach 10/10.

  • 9-10: Named atomic network with an instrumented magic moment, hard side solved first, repeatable tipping playbook, density/liquidity metrics, explicit ceiling and moat plan
  • 7-8: Clear atomic network and hard-side focus, but tipping tactics are ad hoc or metrics still track totals over density
  • 5-6: Network effects acknowledged, but the launch targets a broad market and both sides are treated equally
  • 3-4: Generic user-acquisition plan; network thinking limited to "add invites and hope it spreads"
  • 0-2: Big-bang launch to everyone at once, vanity signups, no hard-side strategy, no liquidity measures

Framework

1. Network Effects Fundamentals

Core concept: A networked product connects people with each other — buyers with sellers, creators with audiences, coworkers with coworkers — and becomes more valuable as the right people join. Network effects come in three distinct forms: the acquisition effect (the network pulls in its own new users), the engagement effect (more users make each session more valuable), and the economic effect (density improves monetization and unit economics). A product can be strong in one and weak in the others.

Why it works: Treating "network effects" as a single magic property hides where growth actually comes from and where it breaks. Metcalfe's law (value grows with n²) is an oversimplification — it counts nodes, not active, relevant connections, and a million scattered users can be worth less than five thousand in one dense community. Every large network is really a network of networks: Uber is hundreds of city-level markets, Slack is millions of team-sized networks. Density and quality of each sub-network beat raw user counts.

Key insights:

  • The three effects decouple: viral acquisition can mask dead engagement — downloads up, rooms empty
  • Metcalfe counts nodes; value lives in active connections — measure density, not totals
  • Anti-network effects are real: the dynamics that compound growth in a dense network compound emptiness in a sparse one
  • The network, not the feature set, is the moat — competitors can copy the product but not the people on it
  • Aggregate metrics lie; cut every metric by sub-network (city, team, category) to see true health

Applications:

ContextApplicationExample
Metric designReplace totals with density measuresTrack weekly active networks, not registered users
Growth diagnosisAttribute growth to the three effects separatelyViral factor vs. session frequency vs. conversion, each per network
Strategy reviewMap the product as a network of networksA marketplace is one network per city-category pair

See references/case-studies.md for three end-to-end worked scenarios — a B2B tool finding its atomic network, a services marketplace seeding one city, a social app recovering from a big-bang launch — when you want a full example to model a plan on.

2. The Cold Start: Atomic Networks

Core concept: An atomic network is the smallest network that is stable and self-sustaining — just enough of the right people that the product delivers its core value and the group keeps returning on its own. Slack needs roughly three users inside one team, Zoom needs two, a marketplace may need a single zip code or category. Pick a network, not a market, and build the killer product for that tiny group — even when it looks unscalably niche.

Why it works: Networks succeed or fail one network at a time. A product that works completely for fifty people in one community proves the loop and can be replicated; one that half-works for fifty thousand scattered users proves nothing and dies of emptiness. Tiny complete networks also expose the magic moment — the experience that shows the network working (the car arrives, the teammate replies) — which becomes the activation bar for every network that follows.

Key insights:

  • Smaller is better: find the minimum size at which the product works, then over-deliver for exactly that group
  • Constrain the first network hard — one company, one campus, one neighborhood, one collector niche — so density is achievable with founder-level effort
  • Define the magic moment precisely and instrument it; gate all expansion on networks reaching it
  • Killer products for tiny networks look like toys (Facebook at Harvard, eBay's collectibles) — niche optics are the cost of density
  • Flintstone the empty side: founders manually supply content, inventory, or matchmaking until the network stands alone

Applications:

ContextApplicationExample
Launch scopingPick a network, not a market"Agents in one Austin brokerage," not "the US housing market"
ActivationDefine and instrument the magic momentNew member posts and gets a teammate reply within minutes
Empty sideFlintstone missing supply manuallyFounders personally fulfill the first 100 marketplace orders

Ethical boundary: Flintstoning means doing real work manually behind the scenes — never fabricating fake users, reviews, or activity that deceives the people on the network.

See references/atomic-networks.md when scoping the first launch — it has the 5-step minimum-size derivation, the actor/action/response/time magic-moment template, instrumentation and zero-rate steps, honest-flintstoning rules, single-player fallbacks, and a launch checklist.

3. Solve the Hard Side

Core concept: Every network has a hard side — a small minority who do disproportionate work and are disproportionately hard to attract and keep: sellers, creators, drivers, hosts, organizers. They have better alternatives and higher expectations, and without them the easy side finds an empty product. Understand their motivations — money, status, utility — and build the product and economics for them first.

Why it works: The easy side shows up when the hard side delivers value, not before. A content app without creators, a marketplace without supply, a collaboration tool without the organizer who sets it up — all are empty rooms. "Come for the tool, stay for the network" is the classic hard-side wedge: a single-player tool (Instagram's filters, OpenTable's reservation book) recruits the hard side one by one before any network exists, and then the network makes leaving unthinkable.

Key insights:

  • Identify the hard side by work done, not money paid: a few percent of users create most of the value on Wikipedia, YouTube, and most marketplaces
  • Map motivations explicitly: money (drivers, sellers), status (creators, top reviewers), utility (organizers who need the tool anyway) — each demands different product investments
  • Build pro workflows and economics for the hard side first; the easy side mostly needs a clean consumer experience
  • Subsidize the scarce side early — guarantees, bonuses, zero fees — and publish the taper so trust survives the rollback
  • Early hard-siders professionalize fast: plan power tools, analytics, and payout improvements for month three, not year three

Applications:

ContextApplicationExample
Marketplace seedingRecruit and subsidize supply before demandGuarantee cleaner earnings for eight weeks pre-launch
Social or content appCourt creators with status and reachEarly-follower advantage, featuring, creator funds
B2B collaborationGive the organizer single-player valueProject tracker useful alone; inviting the team makes it better

Ethical boundary: Hard-side economics must be honest — present launch subsidies as temporary incentives, and never build people's livelihoods on terms you plan to quietly degrade.

See references/hard-side.md when designing supply-side acquisition and economics — it maps money/status/utility motivations to product investments and details three named playbooks (tools-first, content-first, subsidies).

4. Tipping Point and Escape Velocity

Core concept: Once the first atomic network works, growth becomes a repeatable playbook for tipping the next network, and the next — each launch cheaper than the last. The core tipping tools: invite-only mechanics (curation + scarcity + social proof), paying up for launch (subsidies, guarantees, pre-committed supply), and influencer or community seeding. After tipping, escape velocity is not a milestone but an operating model: continuously amplifying the acquisition, engagement, and economic effects.

Why it works: Invite-only launches look exclusionary but build density by design — every invitee arrives with at least one connection already inside, the network copies in along real social graphs, and scarcity manufactures the social proof that pulls the next cohort. Paying up converts money into density, the one asset rivals can't copy. Big-bang launches do the opposite: Google+ pushed hundreds of millions of signups into empty rooms, and the weak networks never retained.

Key insights:

  • Invite-only does three jobs at once: curates early culture, creates scarcity buzz, and imports each user's social graph
  • Subsidies are network CAC: spend to manufacture liquidity, measure cost per active network, taper on a published schedule
  • Big-bang launch is the canonical anti-pattern — fast fill, weak networks; press spikes land on emptiness and never return
  • After tipping, run the three forces as named workstreams: acquisition (viral loops, referrals), engagement (reinforcing loops, re-engagement), economic (conversion, subsidy rollback, pricing)
  • Each tipped network lowers the cost of the next: spillover awareness, a portable playbook, reusable supply relationships

Applications:

ContextApplicationExample
Consumer launchInvite-only with a referral treeWaitlist plus five invites per active user; track invite-graph density
Marketplace city #2Pay up to manufacture liquidityNinety-day driver earnings guarantee, tapered as fill rate rises
Post-tip growthStaff the three forces as workstreamsReferral loop, digest re-engagement, take-rate optimization

Ethical boundary: Scarcity and exclusivity must be real — fake waitlists and manufactured "limited spots" are deception, not strategy.

See references/tipping-playbooks.md when planning network #2 onward — invite-only and referral-tree mechanics, paid-launch and supply pre-commitment tactics, market selection, anti-patterns, and the liquidity metrics to gate on.

Show full SKILL.md (818 more words)Show less
5. The Ceiling and the Moat

Core concept: Growth always stalls. Rocketship curves are a sequence of S-curves, and each flattens against a ceiling: market saturation, channel degradation (CAC creep, banner blindness, viral fatigue), hard-side revolts, and quality collapse at scale — spam, overcrowding, context collapse. The moat is the network itself: defend the hard side, expect rivals to cherry-pick your densest segments, and remember that bundling fills the easy side but rarely wins the hard side.

Why it works: Every acquisition channel decays as audiences habituate and competitors pile in — the first banner ads clicked through at double-digit rates; today's average is a fraction of a percent. Networks also degrade from within: scale attracts spam and collapses the intimate contexts that made early networks valuable, so quality work becomes growth work. And competition between networks is asymmetric: challengers win by applying atomic-network discipline to one underserved niche — which is exactly how incumbents get unbundled.

Key insights:

  • Plot growth as stacked S-curves; start the next curve (geography, segment, use case, product) before the current one flattens
  • CAC creep and viral fatigue are laws, not failures — plan the next channel while the current one still works
  • Watch for hard-side revolt signals: take-rate complaints, multi-homing, organized protest — the hard side leaves first and takes the network with it
  • Quality interventions — curation, ranking, verification, spam fighting, sub-grouping — are growth investments at scale, not cost centers
  • Defend against cherry-picking by over-serving your densest niches; that is precisely where a David will attack your Goliath
  • Bundling buys distribution, not devotion — it fills seats on the easy side, while depth of engagement stays with whoever holds the hard side

Applications:

ContextApplicationExample
Stalled growthDiagnose which ceiling hit firstSeparate saturation, CAC creep, and quality-decay churn per network
Quality at scaleFund trust and curation loopsRatings, verification tiers, spam filters as a growth workstream
Competitive defenseHold the hard side in dense nichesMatch a rival's subsidies for top sellers before they multi-home

Ethical boundary: Fixing revolts and spam means addressing root causes for users — not silencing legitimate hard-side grievances with PR.

See references/scale-ceiling-moat.md when growth stalls or a rival appears — it runs the three forces as growth workstreams, diagnoses which ceiling hit first, and details quality interventions and cherry-picking defense at scale.

Common Mistakes

MistakeWhy It FailsFix
Launching to a market instead of a networkUsers arrive scattered; nobody finds anybodyPick one atomic network and saturate it
Counting signups instead of densityVanity totals mask empty roomsMeasure weekly active networks, fill rate, time-to-match
Treating both sides equallyThe hard side is the bottleneck and the flight riskBuild product and economics for the hard side first
Big-bang launchFast fill, weak networks; hype lands on emptinessTip network by network with a repeatable playbook
Faking scarcity or activityUsers discover the deception; trust collapsesFlintstone with real work; keep invite scarcity real
Cloning network #2 before #1 is stableReplicating a broken loop multiplies failureGate expansion on magic-moment and retention bars
Assuming network effects strengthen foreverSpam, overcrowding, and context collapse compound tooFund quality, trust, and curation as growth work
Ignoring cherry-picking rivalsNiche players peel off your densest segmentsOver-serve dense niches; defend hard-side economics

Quick Diagnostic

QuestionIf NoAction
Can you name your first atomic network (who, where, how many)?You're launching to a market, not a networkConstrain by geography, org, or interest until self-sustaining
Is the magic moment defined and instrumented?You can't tell live networks from dead onesDefine it, measure it per network, gate expansion on it
Do you know who your hard side is and why they stay?Supply churns and the easy side follows it outMap money/status/utility motivations; build for them first
Does the product deliver value to its very first user?Pure chicken-and-egg with no wedgeAdd come-for-the-tool value or flintstone the gap
Is there a written playbook for tipping the next network?Every launch is an expensive one-off betCodify invites, subsidies, and seeding from launch #1
Are you measuring liquidity (fill rate, time-to-match)?Growth optics hide network healthAdd per-network density metrics to the core dashboard
Do you know which ceiling will hit first?The stall will arrive as a mysteryModel saturation, CAC creep, and quality decay now
Is anything defending the hard side from rivals?Cherry-pickers will peel off your best segmentsDeepen hard-side economics and pro tooling

Further Reading

About the Author

Andrew Chen is a general partner at Andreessen Horowitz, where he invests in consumer technology, and previously led the rider growth team at Uber. His long-running essay series on growth, metrics, and network effects — read across the tech industry — became the foundation for The Cold Start Problem.

© wondelai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in cold-start-problem of wondelai/skills.

  • SKILL.md
  • references/atomic-networks.md
  • references/case-studies.md
  • references/hard-side.md
  • references/scale-ceiling-moat.md
  • references/tipping-playbooks.md

Open the folder on GitHubat commit c172996

Compare with similar skills

Cold Start Problem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cold Start Problem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cold Start Problem this skillwondelai/skills2.4k—~4.7kAutomated safety check: PassMIT
Product Lensaffaan-m/ECC275k2 repos~841Automated safety check: PassMIT
Productthedaviddias/Front-End-Checklist74k—~592Automated safety check: PassMIT
Cold Emailcoreyhaines31/marketingskills54k—~3.1kAutomated safety check: PassMIT
Product Analyticsalirezarezvani/claude-skills28k1 repos~1.4kAutomated safety check: PassMIT
Cold Emailsickn33/agentic-awesome-skills47k2 repos~1.9kAutomated safety check: PassMIT

Similar skills

  • Product Lens

    affaan-m/ECC

    Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go/no-go recommendation, a founder review scoring…

    275k GitHub starsUsed in 2 repos~841 tokens
    Product & Project ManagementAuto-check passed
  • Product

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing e-commerce product pages or implementing structured data for a shop.

    74k GitHub stars~592 tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • Cold Email

    coreyhaines31/marketingskills

    Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.

    54k GitHub stars~3.1k tokensUpdated today
    Sales & SupportAuto-check passed
  • Product Analytics

    alirezarezvani/claude-skills

    A skill your agent uses when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across product stages.

    28k GitHub starsUsed in 1 repo~1.4k tokens
    Data & AnalyticsAuto-check passed
  • Cold Email

    sickn33/agentic-awesome-skills

    Write B2B cold emails and follow-up sequences that earn replies.

    47k GitHub starsUsed in 2 repos~1.9k tokens
    Sales & SupportAuto-check passed
  • Product Strategy

    phuryn/pm-skills

    Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.

    27k GitHub stars~1.2k tokensUpdated 23 days ago
    Product & Project ManagementAuto-check passed

More from wondelai/skills

All 61 skills in this repo
  • Crossing The Chasm

    wondelai/skills

    Navigate the technology adoption lifecycle from early adopters to mainstream market.

    2.4k GitHub stars~3.6k tokensUpdated 27 days ago
    Auto-check passed
  • Design Everyday Things

    wondelai/skills

    Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.

    2.4k GitHub stars~4k tokensUpdated 27 days ago
    Auto-check passed
  • Design Sprint

    wondelai/skills

    Run a structured 5-day process to prototype, test, and validate product ideas with real users.

    2.4k GitHub stars~3.8k tokensUpdated 27 days ago
    Auto-check passed
  • Hooked UX

    wondelai/skills

    Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).

    2.4k GitHub stars~3.5k tokensUpdated 27 days ago
    Auto-check passed
  • Improve Retention

    wondelai/skills

    Diagnose and fix retention problems using behavior design (B=MAP).

    2.4k GitHub stars~3.8k tokensUpdated 27 days ago
    Auto-check passed
  • Monetizing Innovation

    wondelai/skills

    Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".

    2.4k GitHub stars~5.2k tokensUpdated 27 days ago
    Auto-check passed

Questions about Cold Start Problem

What does Cold Start Problem do?

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Cold Start Problem is an agent skill from wondelai/skills. Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects.

When should I use Cold Start Problem?

Cold Start Problem fits situations like: the user mentions network effects; chicken and egg; two-sided marketplace; invite-only launch.

How do I install Cold Start Problem in Claude Code?

Run `npx skills add wondelai/skills --skill cold-start-problem -a claude-code`. Or copy the skill folder (cold-start-problem in wondelai/skills) into .claude/skills/cold-start-problem in your project. Claude Code loads it when a task matches its description.

How do I install Cold Start Problem in Codex?

Run `npx skills add wondelai/skills --skill cold-start-problem -a codex`. Or copy the skill folder (cold-start-problem in wondelai/skills) into .agents/skills/cold-start-problem in your project. Codex loads it when a task matches its description.

Can I use Cold Start Problem in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wondelai/skills --skill cold-start-problem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cold-start-problem, .gemini/skills/cold-start-problem, .github/skills/cold-start-problem and .opencode/skills/cold-start-problem in your project.

What does Cold Start Problem need to run?

SKILL.md names no scripts, command-line tools or credentials: Cold Start Problem is instructions for the agent only.

Does Cold Start Problem access the network?

SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.

Is Cold Start Problem safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cold Start Problem use?

Cold Start Problem is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cold Start Problem use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.

What are the alternatives to Cold Start Problem?

Skills that share tags, products or a category with Cold Start Problem: Product Lens (affaan-m/ECC, 275k stars), Product (thedaviddias/Front-End-Checklist, 74k stars), Cold Email (coreyhaines31/marketingskills, 54k stars) and Product Analytics (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cold Start Problem?

wondelai (a GitHub organization) maintains it in wondelai/skills, which has 2,356 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 10, 2026.

Source: wondelai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.