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…
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects.
$ npx skills add wondelai/skills --skill cold-start-problem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wondelai/skills cold-start-problem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "cold-start-problem" agent skill from https://github.com/wondelai/skills/tree/main/cold-start-problem into .claude/skills/cold-start-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-start-problem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wondelai/skills/tree/main/cold-start-problemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wondelai/skills --skill cold-start-problem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wondelai/skills cold-start-problem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cold-start-problem .agents/skills/cold-start-problem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cold-start-problem" agent skill from https://github.com/wondelai/skills/tree/main/cold-start-problem into .agents/skills/cold-start-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-start-problem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill cold-start-problem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wondelai/skills cold-start-problem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cold-start-problem .cursor/skills/cold-start-problem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cold-start-problem" agent skill from https://github.com/wondelai/skills/tree/main/cold-start-problem into .cursor/skills/cold-start-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-start-problem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wondelai/skills.git --path cold-start-problem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wondelai/skills --skill cold-start-problem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wondelai/skills cold-start-problem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cold-start-problem .gemini/skills/cold-start-problem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cold-start-problem" agent skill from https://github.com/wondelai/skills/tree/main/cold-start-problem into .gemini/skills/cold-start-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-start-problem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wondelai/skills cold-start-problemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wondelai/skills --skill cold-start-problem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/cold-start-problem .github/skills/cold-start-problem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cold-start-problem" agent skill from https://github.com/wondelai/skills/tree/main/cold-start-problem into .github/skills/cold-start-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-start-problem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wondelai/skills --skill cold-start-problem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wondelai/skills cold-start-problem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wondelai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cold-start-problem .opencode/skills/cold-start-problem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cold-start-problem" agent skill from https://github.com/wondelai/skills/tree/main/cold-start-problem into .opencode/skills/cold-start-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-start-problem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cold-start-problemStart 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. 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.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c172996. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
amazon.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from wondelai/skills at commit c172996, republished under its MIT licence (© wondelai). 2,470 words, ~4,713 tokens.
.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.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.
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.
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.
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:
Applications:
| Context | Application | Example |
|---|---|---|
| Metric design | Replace totals with density measures | Track weekly active networks, not registered users |
| Growth diagnosis | Attribute growth to the three effects separately | Viral factor vs. session frequency vs. conversion, each per network |
| Strategy review | Map the product as a network of networks | A 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.
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:
Applications:
| Context | Application | Example |
|---|---|---|
| Launch scoping | Pick a network, not a market | "Agents in one Austin brokerage," not "the US housing market" |
| Activation | Define and instrument the magic moment | New member posts and gets a teammate reply within minutes |
| Empty side | Flintstone missing supply manually | Founders 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.
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:
Applications:
| Context | Application | Example |
|---|---|---|
| Marketplace seeding | Recruit and subsidize supply before demand | Guarantee cleaner earnings for eight weeks pre-launch |
| Social or content app | Court creators with status and reach | Early-follower advantage, featuring, creator funds |
| B2B collaboration | Give the organizer single-player value | Project 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).
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:
Applications:
| Context | Application | Example |
|---|---|---|
| Consumer launch | Invite-only with a referral tree | Waitlist plus five invites per active user; track invite-graph density |
| Marketplace city #2 | Pay up to manufacture liquidity | Ninety-day driver earnings guarantee, tapered as fill rate rises |
| Post-tip growth | Staff the three forces as workstreams | Referral 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.
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:
Applications:
| Context | Application | Example |
|---|---|---|
| Stalled growth | Diagnose which ceiling hit first | Separate saturation, CAC creep, and quality-decay churn per network |
| Quality at scale | Fund trust and curation loops | Ratings, verification tiers, spam filters as a growth workstream |
| Competitive defense | Hold the hard side in dense niches | Match 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.
| Mistake | Why It Fails | Fix |
|---|---|---|
| Launching to a market instead of a network | Users arrive scattered; nobody finds anybody | Pick one atomic network and saturate it |
| Counting signups instead of density | Vanity totals mask empty rooms | Measure weekly active networks, fill rate, time-to-match |
| Treating both sides equally | The hard side is the bottleneck and the flight risk | Build product and economics for the hard side first |
| Big-bang launch | Fast fill, weak networks; hype lands on emptiness | Tip network by network with a repeatable playbook |
| Faking scarcity or activity | Users discover the deception; trust collapses | Flintstone with real work; keep invite scarcity real |
| Cloning network #2 before #1 is stable | Replicating a broken loop multiplies failure | Gate expansion on magic-moment and retention bars |
| Assuming network effects strengthen forever | Spam, overcrowding, and context collapse compound too | Fund quality, trust, and curation as growth work |
| Ignoring cherry-picking rivals | Niche players peel off your densest segments | Over-serve dense niches; defend hard-side economics |
| Question | If No | Action |
|---|---|---|
| Can you name your first atomic network (who, where, how many)? | You're launching to a market, not a network | Constrain by geography, org, or interest until self-sustaining |
| Is the magic moment defined and instrumented? | You can't tell live networks from dead ones | Define 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 out | Map money/status/utility motivations; build for them first |
| Does the product deliver value to its very first user? | Pure chicken-and-egg with no wedge | Add 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 bet | Codify invites, subsidies, and seeding from launch #1 |
| Are you measuring liquidity (fill rate, time-to-match)? | Growth optics hide network health | Add per-network density metrics to the core dashboard |
| Do you know which ceiling will hit first? | The stall will arrive as a mystery | Model saturation, CAC creep, and quality decay now |
| Is anything defending the hard side from rivals? | Cherry-pickers will peel off your best segments | Deepen hard-side economics and pro tooling |
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
SKILL.md and 5 other files (references) in cold-start-problem of wondelai/skills.
Open the folder on GitHubat commit c172996
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cold Start Problem this skillwondelai/skills | 2.4k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Product Lensaffaan-m/ECC | 275k | 2 repos | ~841 | Automated safety check: Pass | MIT | |
| Productthedaviddias/Front-End-Checklist | 74k | — | ~592 | Automated safety check: Pass | MIT | |
| Cold Emailcoreyhaines31/marketingskills | 54k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Product Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Cold Emailsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.9k | Automated safety check: Pass | MIT |
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…
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing e-commerce product pages or implementing structured data for a shop.
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.
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.
sickn33/agentic-awesome-skills
Write B2B cold emails and follow-up sequences that earn replies.
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.
wondelai/skills
Navigate the technology adoption lifecycle from early adopters to mainstream market.
wondelai/skills
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models.
wondelai/skills
Run a structured 5-day process to prototype, test, and validate product ideas with real users.
wondelai/skills
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment).
wondelai/skills
Diagnose and fix retention problems using behavior design (B=MAP).
wondelai/skills
Design products and pricing around validated willingness to pay, from Ramanujam & Tacke's "Monetizing Innovation".
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.
Cold Start Problem fits situations like: the user mentions network effects; chicken and egg; two-sided marketplace; invite-only launch.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Cold Start Problem is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: amazon.com. This is read from the text; nothing was executed.
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.
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.
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.
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.
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.