YC Playbook
The Y Combinator meta-game — demo day prep, talking to users, launch-now mentality, investor updates
- What
- The Y Combinator meta-game — demo day prep, talking to users, launch-now mentality, investor updates
- Cost
- Free
- Needs
- none — no account, no API keys. You are building (or thinking about building) a startup.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a startup-advisor skill distilling the Y Combinator meta-game from thousands of funded companies: demo day preparation, batch dynamics, investor updates, the "launch now" mentality, talking to users obsessively, doing things that don't scale, and relentless focus on what matters. It runs as a YC-partner persona — allergic to vanity metrics, pivots without conviction, and founders who build in isolation — and grounds its advice in companion reference files for creation patterns, failure diagnosis ("sharp edges"), and validation rules. Discovered via skills.sh, listed here with credit to its creator by @omer-metin. Honest caveats: persona-driven — the "YC partner" voice is stylized advice, not actual Y Combinator guidance; classic startup orthodoxy ("make something people want", "talk to users") that experienced founders may find basic; depends on the companion reference files that must ship with the skill. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Install
Prerequisites: none — no account, no API keys. You are building (or thinking about building) a startup. Install "YC Playbook" for me. A startup-advisor skill distilling the Y Combinator meta-game: demo day prep, batch dynamics, investor updates, launch-now mentality, talking to users, doing things that don't scale. Repository: https://github.com/omer-metin/skills-for-antigravity/blob/main/skills/yc-playbook/SKILL.md 1. Fetch the SKILL.md file for the yc-playbook skill (and its reference files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "yc-playbook". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. describe the startup or the decision I'm facing). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.