vc-first-call

Original：🇺🇸 English

Translated

Prep for a first VC meeting by mapping a founder's pitch deck against the investor's pre-meeting questions, producing an honest assessment of what is answered vs. what is missing, then generating a memo the founder can send ahead of the call. Use when a founder asks for help prepping a first VC meeting, when an investor has shared a pre-meeting question list (e.g. Jess Lin / Work-Bench), or when the user wants a deck reviewed against specific investor expectations.

1installs

Sourcerezzk2/first-call-skill

Added on2026-06-25

NPX Install

npx skill4agent add rezzk2/first-call-skill vc-first-call

SKILL.md Content

View Translation Comparison →

VC First Call Prep

Help a founder show up to their first VC meeting with a tight, honest read on how well their current materials answer the investor's stated questions — and a memo they can optionally send ahead of time.

The default question set is Jess Lin's (Work-Bench) pre-meeting guide. Founders can drop in any investor's questions by adding a new file under

questions/

.

Operating principles (do not violate)

No hallucination. Every claim you make about the deck must be backed by a direct quote with a slide/page reference. If you cannot quote it, it is not there.
No over-inference. "The deck mentions enterprise customers" is not the same as "the deck explains the enterprise GTM motion." A passing reference is not an answer.
Be blunt about gaps. The founder's job is to know what is missing before the investor finds out. Do not soften, do not pad, do not reassure.
Stick to the investor's question list. Do not invent your own questions, critiques, or "advice" beyond what is needed to flag gaps.
Do not write the founder's answers for them. Stage 1 surfaces gaps. Stage 2 integrates the founder's own words from the filled-in assessment. If a gap is left blank, leave a visible
```
[TODO: founder to fill]
```
marker in the memo — never invent content to cover it.

Inputs to ask for

Before starting, confirm with the user:

Deck — path to a PDF (preferred), a markdown export, or pasted slide text. If they only have
```
.pptx
```
or Google Slides, ask them to export to PDF or paste the text. Do not guess slide contents.
Supporting docs (optional) — one-pager, founder notes, prior memo, Notion page, etc. Treat these as secondary to the deck — quote them with their own labels (e.g.
```
[one-pager]
```
) so the founder can see where evidence came from.
Investor question set — default to
```
questions/jess-lin-workbench.md
```
. If the founder names a different investor, look for a matching file in
```
questions/
```
; if absent, ask them to paste the investor's questions and offer to save a new file.
Stage — are they at Stage 1 (first pass on the deck) or Stage 2 (assessment is filled in and they want a memo)? If unclear, check whether
```
assessment.md
```
exists in the working directory and whether its
```
Founder fills in:
```
blocks have been completed.

Stage 1 — Assessment

Goal: produce

assessment.md

in the working directory that scores every investor question against the deck.

Steps:

Read the deck fully with the
```
Read
```
tool (it handles PDFs — for long PDFs, use the
```
pages
```
parameter to read in chunks).
Read any supporting docs the founder shared.
Load the chosen questions file. Treat every bullet under every top-level theme as its own question.
For each question, assign exactly one verdict:
- Answered — the deck contains a direct, specific answer. Quote it with slide/page reference.
- Partial — there is relevant material but it does not fully address the question. Quote what is there. Name precisely what is missing.
- Not in deck — no material addresses this question. Say so plainly. Do not speculate about what the founder "probably" thinks.
Use the template at
```
templates/assessment.md
```
. For every Partial and Not-in-deck verdict, include a
```
Founder fills in:
```
block with a short prompt that tells the founder exactly what to write.
End the assessment with a Summary: count of Answered / Partial / Not-in-deck, plus the 3–5 highest-leverage gaps to close before the meeting.
After writing the file, tell the founder: "Fill in the
```
Founder fills in:
```
blocks in
```
assessment.md
```
, then ask me to generate the memo."

What "objective" looks like in practice:

A slide titled "Why now" with three crisp bullets that answer the question → Answered, quote the bullets.
A slide titled "Why now" with vague platitudes ("AI is changing everything") → Partial, quote it, say "does not name a specific market shift or why it makes this inevitable now."
No mention of timing or market dynamics anywhere → Not in deck.

Stage 2 — Memo

Goal: produce

memo.md

in the working directory — a tight document the founder can send to the investor before the meeting.

Steps:

Read the filled-in
```
assessment.md
```
.
Verify every
```
Founder fills in:
```
block has content. If any are still blank, list them and stop — do not generate a memo with invented content. Offer to generate a partial memo with
```
[TODO]
```
markers if the founder explicitly asks.
Use the template at
```
templates/memo.md
```
. Structure the memo around the investor's question themes (not slide order).
Voice rules:
- First person plural ("we"), founder-voice
- Tight prose, not bullet salad — bullets are okay where they genuinely help (lists of customers, traction numbers)
- Quote the deck where the deck already says it well; otherwise paraphrase the founder's filled-in answers without embellishing
- No marketing fluff, no adjectives the founder did not use, no claims not in source material
End with a one-line "What we'd love to dig into with you" that mirrors the investor's framing — sourced from the founder's notes, not invented.

What to say to the founder

Before Stage 1: "I'll read your deck and any supporting docs against [investor]'s questions. I'll mark each question as Answered / Partial / Not in deck with quoted evidence, and flag exactly what you need to fill in. I won't invent answers — gaps will be visible."

After Stage 1: "Here's the assessment. The summary at the bottom flags the highest-leverage gaps. Fill in the

Founder fills in:

blocks directly in

assessment.md

(your own words, not polished prose — I'll tighten it for the memo), then tell me to generate the memo."

After Stage 2: "Here's the memo. Read it once for voice — make sure it sounds like you, not me. The deck quotes are verbatim; the prose between them is built only from what you wrote in the assessment."