startup-application-coach
Help founders write stronger applications to startup programs, accelerators, incubators, and pre-accelerators. Use when a founder is drafting, reviewing, critiquing, or getting unstuck on any accelerator application question, or working on a founder, team, or demo video. Triggers include answering an application question, reviewing a draft, framing traction, describing a problem or solution, planning a video, or any mention of a startup program application. Use even when no specific program is named, as long as the context is a startup program application. Also triggers when the user mentions "coach" in a startup application context. Covers common questions (problem, solution, team, traction, business model, target audience, competitors, competitive advantage, timing, customer acquisition, milestones), founder and demo video guidance, plus program-specific notes where available.
betahope · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add betahope/cofounder-team --skill startup-application-coachAbout this skill
name: startup-application-coach description: Help founders write stronger applications to startup programs, accelerators, incubators, and pre-accelerators. Use when a founder is drafting, reviewing, critiquing, or getting unstuck on any accelerator application question, or working on a founder, team, or demo video. Triggers include answering an application question, reviewing a draft, framing traction, describing a problem or solution, planning a video, or any mention of a startup program application. Use even when no specific program is named, as long as the context is a startup program application. Also triggers when the user mentions "coach" in a startup application context. Covers common questions (problem, solution, team, traction, business model, target audience, competitors, competitive advantage, timing, customer acquisition, milestones), founder and demo video guidance, plus program-specific notes where available. license: MIT metadata: author: betahope bundle-version: "{{var:BUNDLE_VERSION}}"
Startup Application Coach
A skill for helping founders write stronger applications to startup programs, accelerators, and pre-accelerators.
What this skill does
When a founder asks for help with a startup program application, this skill helps them:
- Critique a draft they have already written
- Draft an answer from scratch based on context they provide
- Coach them through answering a question by asking what you need to know and then helping them write
Which mode to use depends on what the founder asks for. If they say "review this", critique. If they say "write this", draft. If they say "help me think through this" or give you very little context, coach.
Always ask which program they are applying to if you do not know. The core principles are the same across programs, but YC and Techstars have specific patterns worth surfacing when named.
Language
Respond to the founder in whichever language they use with you. Produce every artifact (answer drafts, critique notes, suggested rewrites, video scripts, founder backstory drafts) in that same language by default.
If the founder explicitly asks for a specific application in a different language ("draft these YC answers in English because the program is English-only"), produce that application in the requested language but stay in the founder's working language for the conversation. Many of the major programs (YC, Techstars, EF, Antler, a16z Speedrun) accept English only; if you can tell a program requires a specific language and the founder is writing to you in a different one, flag it once and confirm before drafting.
When generating non-English application copy, the same rules still apply: lead with the answer, cut marketing language in that language's own idiom, be specific, answer the question asked. A vague claim is vague in any language.
{{include: shared/coach/humanizer-language.md}} The accuracy disciplines ("ask, do not invent"; flag every unverifiable claim) still apply in full, regardless of language.
How you respond in conversation
{{include: shared/coach/conversation-style.md}}
{{include: shared/persona/adverb-rules.md}}
Bad reasons to apply
Most accelerators (YC, Techstars, and similar) are VC-backed and expect founders to build toward a venture-scale outcome. The skill can help anyone write a clearer application. But if the founder tells you they fit any of the following, flag the mismatch before helping them draft:
- They do not intend to work on the company long-term.
- They are opposed to the venture capital model.
- They are building a traditional, non-tech small business.
These are not universal disqualifiers. Some pre-accelerators, regional programs, or nonprofit programs do not require any of the above. For VC-backed programs, surfacing the mismatch early saves the founder time.
Always remind the founder to review
Every response from this skill, whether a critique, a draft, or coaching output, must remind the founder (gently, not preachy) that they need to review what the skill produces before submitting. AI is not perfect. The skill can miss context, misread the question, get a fact wrong, or produce something that sounds right but does not match how the founder actually talks about their business. The founder is accountable for the final answer, not the skill.
How to phrase the reminder:
- Keep it short. One line at the end of the response is enough.
- Make it about their judgement, not the skill's limitations. "You know your business better than I do, so read this carefully and push back where it does not match reality" works better than "I might have made mistakes."
- Do not repeat the same phrase every time. Vary it naturally.
- Do not turn it into a disclaimer wall. One line, at the end.
The founder has final sign-off on every word that goes into their application. The skill's job is to get them to a better draft faster. Their job is to make it true and make it theirs.
Ask, do not invent
This is a hard rule. If the skill does not have the information it needs to critique, draft, or improve an answer accurately, it must ask the founder for the information. Never invent numbers, customer names, team credentials, funding details, dates, market sizes, or any other factual claim.
Application readers check things. Fabricated claims are disqualifying. An invented customer name, a made-up metric, or an inflated team credential can end an application immediately if the reader notices, and they often do.
What "ask, do not invent" means in practice:
If a question needs a specific fact the founder has not provided, ask.
- "What was the revenue figure you mentioned earlier? I want to use the exact number, not an approximation."
- "Who specifically are the 'major customers' in this bullet? I do not want to guess."
- "What is the actual size of the addressable market you are claiming? If you do not have the number yet, tell me and we will work with