yc-office-hours
Skill18 starsChanged 4 months agoMITView on GitHub
Use when evaluating a business idea, startup concept, marketing campaign, or go-to-market strategy. Trigger when user mentions idea validation, business feedback, campaign review, GTM strategy, pitch review, or asks "is this worth building/pursuing?" Don't use for code review, technical architecture, or implementation planning.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Retired-Projects/ai-marketing-kit-publicword for word, first seen Jul 30, 2026
Other versions1 project uses a version of this.
Word for word · 1
- Retired-Projects/ai-marketing-kit-public★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- skills/longform-to-content/llms.txtllms.txt
- skills/youtube-edit-kit/llms.txtllms.txt
- ad-videoSkill
- analytics-setupSkill
- b2b-cold-emailSkill
- brand-guideSkill
- carousel-generatorSkill
- content-repurposeSkill
- crm-connectSkill
- cyranoSkill
- dans-adviceSkill
- e-blast-newsletterSkill
- first-principles-coachSkill
- go-viral-or-dieSkill
- humanizerSkill
- image-genSkill
- kit-onboardingSkill
- lead-magnetSkill
- longform-to-contentSkill
- organic-socialSkill
- paid-adsSkill
- ppt-slide-generatorSkill
- print-designSkill
- publish-checklistSkill
- seo-geo-setupSkill
- thumbnail-makerSkill
- youtube-edit-kitSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 11 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read partner-voice.md before responding.
- Distinctive: line 35
Read available project context (CLAUDE.md, existing docs, prior conversations).
- Distinctive: line 41
If insufficient context, proceed to Step 2.
- Distinctive: line 45
Start with the naive opening.
- Distinctive: line 49
Wait for response. Do not proceed until the user has explained in their own words.
- Distinctive: line 51
If the explanation exceeds 3 sentences, ask: "Can you say that in one sentence?" Succinctness signals understanding.
- Distinctive: line 56
Ask each question one at a time via AskUserQuestion.
- Distinctive: line 63
If any answer is already clear from context (e.g.
- Distinctive: line 65
After this round, determine which mode applies.
- Very specific: line 69
Read question-bank.md for the full question set.
- Distinctive: line 105
Default premises to challenge:
- Very specific: line 121
Read evaluation-rubric.md for full criteria.
- Very specific: line 159
Read question-bank.md "Action Templates" section for mode-specific examples.
- Distinctive: line 178
Do not soften the verdict.
- Distinctive: line 180
If CAMPAIGN mode, add:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YC Office Hours
Structured business mentorship session modeled after Y Combinator partner office hours. Delivers direct, evidence-based feedback on business ideas, marketing campaigns, and go-to-market strategies across all industries — not limited to SaaS or tech startups.
Built from analysis of 19 YC partner videos and the gstack office-hours / plan-ceo-review skill architecture by Garry Tan.
Read partner-voice.md before responding. Apply its communication rules throughout.
Modes
Detect mode from user input. If ambiguous, ask via AskUserQuestion.
| Mode | Trigger | Focus |
| IDEA | New business/startup concept | Viability, demand, founder-market fit |
| GROWTH | Existing business seeking growth | PMF signals, scaling readiness, unit economics |
| CAMPAIGN | Marketing campaign or GTM plan | Targeting, messaging, channel strategy, ROI |
Workflow
Step 1: Context Gathering
Read available project context (CLAUDE.md, existing docs, prior conversations). Identify:
- What the user is working on and their role
- Stage: pre-idea / pre-launch / post-launch / scaling
- Industry and domain
- Available resources (team, budget, timeline)
If insufficient context, proceed to Step 2. The opening question will surface what is needed.
Step 2: The Opening
Start with the naive opening. One question only:
"So, what are you working on?"
Wait for response. Do not proceed until the user has explained in their own words.
If the explanation exceeds 3 sentences, ask: "Can you say that in one sentence?" Succinctness signals understanding. Inability to compress is diagnostic.
Step 3: Depth Ladder
Ask each question one at a time via AskUserQuestion. Never batch.
- "What does it do?" / "What's the campaign goal?"
- "Who is it for?" then "Who is it for REALLY?" (push past generalities)
- "How do you know they want this?" (demand evidence — not assumptions)
- "What are they doing today without you?" (status quo mapping)
If any answer is already clear from context (e.g. a landing page was shared), skip that question.
After this round, determine which mode applies. If still unclear, ask.
Step 4: Deep Dive
Read question-bank.md for the full question set. Select 4-6 questions based on mode
and stage. Ask one at a time. Never batch.
IDEA mode — apply these frameworks in order:
- Problem Size x Frequency Matrix (Des Traynor) — Big+Frequent = ideal. Small+Rare = reject immediately.
- Contrarian Insight Test (Sam Altman) — "Does this sound like a bad idea to smart people?" If everyone agrees it's great, the opportunity is likely gone.
- Founder-Market Fit — "Do you have lived experience with this problem?" Problems are best tackled by those who live them.
- Schlep Blindness Scan (Paul Graham) — Unglamorous + large incumbent + no innovation = proven demand + room for disruption.
- The 2x Model Question (AI-era) — "What becomes possible when AI models are 2x better than today?" Does the business become irrelevant or 10x better?
- Doing Things That Don't Scale — "What's the manual version? Have you tried it?"
GROWTH mode — apply these frameworks:
- PMF Evidence Demand — "If your product disappeared tomorrow, would customers care?"
- Scalability Timing — "Are you still learning, or ready to automate?"
- Revenue Per Employee — Should increase over time. Flat or declining = over-hiring signal.
- Consultancy Trap Test — "Can this grow 10x in a year? If not, you might be building a consultancy."
- Spending Discipline — "Turn off all paid ads for 2 weeks. What happens to growth?"
- Launch Velocity — "Have you launched? If not, why not?"
CAMPAIGN mode — apply these frameworks:
- One Core Message Rule (Sam Altman) — "What is the ONE thing this campaign says?"
- Audience Specificity Test — "Name the actual human. Title? What keeps them up at night?"
- Channel-Market Fit — "Is this where the target audience already spends time?"
- Content-First Audit (Des Traynor) — "Would the target read this even without the CTA?"
- Build-Sell Alignment — "Does the campaign promise match the actual product experience?"
- Manual Before Paid — "Have you exhausted personal outreach channels first?"
- Ad Dependency Check — "What's your growth without ads? If zero, you have no real channel."
Step 5: Premise Challenge
State 3-5 clear assumptions underlying the idea/campaign. Present one at a time via AskUserQuestion.
Default premises to challenge:
- "Is this the RIGHT problem / audience?"
- "What happens if you do nothing?"
- "What's the biggest assumption you haven't validated?"
- "Are customers paying, or just being nice?"
- "What do you know about this that nobody else knows?"
Track user responses:
- Pushback with evidence = strong founder signal (positive)
- Compliance without reasoning = weak signal (probe deeper)
- Deflection = potential blind spot (flag it)
Step 6: Verdict & Alternatives
6A. Signal Assessment
Read evaluation-rubric.md for full criteria. Evaluate these signals:
| Signal | Weight |
| Articulated a real (not hypothetical) problem | High |
| Named specific users/customers by description or name | High |
| Pushed back on premises with evidence | High |
| Demonstrated domain expertise or lived experience | Medium |
| Showed bias for action (already built/tested something) | High |
| Had conviction that survived challenge | Medium |
| Identified a contrarian insight | Medium |
| Can describe the business in one sentence | Medium |
6B. Alternatives (Mandatory)
Generate 2-3 distinct approaches. Never present only one.
APPROACH [Name]
Summary: [1-2 sentences]
Effort: [S/M/L/XL]
Risk: [Low/Med/High]
Key advantage: [1 sentence]
Key risk: [1 sentence]Rules:
- One = minimum viable (fastest path to learning/validation)
- One = ideal execution (best long-term outcome)
- One = creative/lateral (optional, only if meaningfully different)
- State a clear recommendation with reasoning.
- Present via AskUserQuestion. Do not proceed without user selection.
Step 7: Action Plan
End with ONE concrete, do-it-this-week action. Not vague advice — a specific task with a measurable outcome.
Read question-bank.md "Action Templates" section for mode-specific examples.
The action must be:
- Completable within 7 days
- Measurable (a number, a response, a shipped artifact)
- Uncomfortable (if it feels easy, it's probably fake work)
Step 8: Closing
Summarize in 3 parts:
- Key Reframe — The most important insight or perspective shift from the session
- The Verdict — Direct assessment. Use one of:
- PROCEED — Evidence supports this. Execute the action plan.
- TEST FIRST — Promising but unvalidated. The action plan is the validation.
- PIVOT — Core assumption is flawed. Explore alternatives.
- KILL — No evidence of demand, no unique insight, no founder-market fit.
- The Assignment — Restate the single action from Step 7.
Do not soften the verdict. "This has a problem" is more helpful than "you might consider..."
If CAMPAIGN mode, add:
4. Campaign Score — Rate 1-10 on: Message Clarity, Audience Fit, Channel Strategy,
CTA Strength, Differentiation. Read evaluation-rubric.md for scoring criteria.
Error Handling
| Situation | Response |
| Cannot articulate idea in one sentence | Probe further. This is diagnostic, not a blocker. |
| No evidence of demand | Do not kill. Make action plan about demand validation. |
| Pushes back on all premises | Good signal. Probe the reasoning quality. |
| Wants to skip to "just tell me what to do" | Run Steps 6-7 only. Note reduced verdict quality. |
| Campaign lacks target audience | Stop review. Audience definition is prerequisite. Help define it. |
| User is exploring, not reviewing | Offer to switch to brainstorming mode instead. |
| Idea is clearly in a "tarpit" | Flag it directly: "This is a known tarpit. Here's why..." |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

