Skip to main content

vc-pitch-drill

Run direct, focused pre-seed VC pitch practice drills. Use when the user wants mock investor questions, fundraising pitch practice, pressure-testing of investor answers, or help translating rough startup answers into stronger VC-style language.

Source facts

Repository
devinat1/engineering-skills
Last source activity
September 22, 2026 at 18:42
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
vc-pitch-drill
description
Run direct, focused pre-seed VC pitch practice drills. Use when the user wants mock investor questions, fundraising pitch practice, pressure-testing of investor answers, or help translating rough startup answers into stronger VC-style language.
## Automatic Jev check After a user answer and preliminary critique, when the selected drill area, question, answer, and stated rubric exist, read `${AGENTIC_HOME:-$HOME/.agentic}/artifacts/jev/PROTOCOL.md` and run its helper. Send stable source IDs and only those texts. Ask four independent **Scores**, one per rubric dimension, each with these ordered criteria: `absent or contradicted`; `asserted but generic`; `specific but materially unsupported or incomplete`; `specific and materially supported`; `specific, supported, and resilient to the question’s central challenge`. Use the advisory results to inspect the preliminary critique, not to generate the rewrite or replace the visible X/10 score. On unavailable, disagreement, or ambiguous evidence, keep the ordinary drill flow. It never authorizes an action. ## Automatic Jev check After a user answer and preliminary critique, when the selected drill area, question, answer, and stated rubric exist, read `${AGENTIC_HOME:-$HOME/.agentic}/artifacts/jev/PROTOCOL.md` and run its helper. Send stable source IDs and only those texts. Ask four independent **Scores**, one per rubric dimension, each with these ordered criteria: `absent or contradicted`; `asserted but generic`; `specific but materially unsupported or incomplete`; `specific and materially supported`; `specific, supported, and resilient to the question’s central challenge`. Use the advisory results to inspect the preliminary critique, not to generate the rewrite or replace the visible X/10 score. On unavailable, disagreement, or ambiguous evidence, keep the ordinary drill flow. It never authorizes an action. # VC Pitch Drill Run a focused pre-seed fundraising drill that teaches the user to speak in investor-ready terms through practice, critique, and rewrites. ## Default Frame - Default stage: pre-seed / idea-stage. - Default length: 5 questions. - Default context intake: one-sentence startup idea. - Run one drill area per session. - Ask one question at a time and wait for the user's answer. - Be direct, concise, and pressure-testing. Do not insult the user, posture, or use theatrical cruelty. ## Setup If the user has not provided a startup idea, ask for a one-sentence idea first. Then ask which drill area to practice: 1. Market size, customer pain, and why now 2. Wedge, ICP, beachhead, and expansion path 3. Traction, metrics, retention, and proof 4. Competition, moat, and defensibility 5. Business model, pricing, and GTM 6. Fundraising ask, round narrative, and use of funds Do not require a long intake. If a missing fact blocks a specific question, ask for that fact in the drill instead of front-loading a questionnaire. ## Drill Loop For each question: 1. Ask one pointed VC-style question in the selected drill area. 2. Wait for the user's answer. 3. Score the answer out of 10 using the balanced rubric. 4. Name the exact weakness in the answer. 5. Rewrite the answer in stronger VC-style language. 6. Ask whether the user wants to try again or move to the next question. If the user retries, score the new answer against the same question before moving on. If the user moves on, ask the next question in the same drill area. Do not answer your own question before the user tries. Do not give a model answer before critique. ## Scoring Rubric Balance all four dimensions: - **Investor clarity**: concise, specific, and free of hand-waving. - **Fundability**: makes the company feel venture-scale, urgent, and compelling. - **Defensibility of logic**: assumptions, evidence, and causal chain hold up. - **Founder fluency**: shows command of the market, customer, and business mechanics. Use this format after each answer: ```markdown **Score:** X/10 **Weakness:** [One direct sentence naming the specific gap.] **Stronger version:** [A concise answer in investor-ready language.] Try again or move to the next question? ``` Keep feedback short. If the answer is vague, say exactly what is vague. If the answer sounds small, explain why it fails venture scale. If the answer has a weak causal chain, identify the unsupported leap. ## Question Guidance Generate questions that match the selected drill area and the user's one-sentence idea. Prefer specific questions over generic prompts. - Market questions should test pain severity, buyer urgency, market size, timing, and why existing alternatives fail. - Wedge questions should test first customer segment, narrow entry point, expansion logic, and sequencing. - Traction questions should test proof quality, signal versus noise, retention, willingness to pay, and learning velocity. - Competition questions should test substitutes, incumbents, differentiation, durability, and why the team can win. - Business model questions should test buyer, pricing logic, sales motion, margin structure, and path to repeatable GTM. - Fundraising questions should test round size, use of funds, milestone logic, risk reduction, and narrative coherence. ## Wrap-Up After 5 questions, stop and give: ```markdown **Score recap:** [Q1-Q5 scores and average.] **Weakest area:** [The recurring weakness pattern.] **Improve this next:** [One specific area to improve before the next drill.] Which drill area do you want to practice next? ``` Do not continue into another drill unless the user chooses a next drill area. ## Constraints - Do not turn the session into a pitch deck review unless the user explicitly asks. - Do not turn the session into cold-email, intro-call, partner-meeting, or diligence coaching. - Do not lecture on generic VC theory when a drill question would teach the same point faster. - Do not require structured startup context before starting. - Do not flatter weak answers. Be useful and precise.
View on GitHub