Agent skill · Testing & QA

vc-partner-meeting

Simulate the VC partner meeting that discusses your pitch after you leave the room — four partner archetypes debate, then write the internal verdict memo. Use when asked how will VCs discuss my pitch, simulate the partner meeting, stress-test my fundraise, or what happens after the pitch. Produces the meeting transcript, the internal fund/pass/track memo, and a debrief listing which objections are fixable before the real meeting.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill vc-partner-meeting --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/vc-partner-meeting/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# VC Partner Meeting Skill The most important meeting of your fundraise is one you're not in. This skill runs it early: four partners who just watched your pitch debate it the way funds actually do — pattern-matching, fund math, and all — then commit a verdict to the internal memo. ## What This Skill Produces - **The transcript** — four partner archetypes discussing your company, each in a distinct voice - **The internal memo** — the fund/pass/track verdict with the reasoning a fund would actually write down - **The debrief** — out of character: objections ranked by fixability before your real meeting ## Required Inputs Ask for these if not provided: - **The pitch** — deck text, memo, or a summary of the business (stage, traction, team, market, raise amount, valuation ask) - **The fund context** (optional) — fund size and stage focus; default to a $300M multi-stage fund if absent - **Known objections** (optional) — what pushback the user has already heard ## Framework: The Four Partners Each speaks at least twice; they must disagree somewhere — real partner meetings are arguments: | Partner | What they weigh | Their failure mode (include it) | |---|---|---| | **The Champion** | Why

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Four Partners
  4. Output Format
  5. Transcript
  6. Internal Memo
  7. Debrief — out of character
  8. Quality Checks
  9. Anti-Patterns
Ships with 1 file
  • references/worked-example.md
More from pm-claude-skills
All skills →
About this skill
What does the vc-partner-meeting skill do?

Simulate the VC partner meeting that discusses your pitch after you leave the room — four partner archetypes debate, then write the internal verdict memo. Use when asked how will VCs discuss my pitch, simulate the partner meeting, stress-test my fundraise, or what happens after the pitch. Produces the meeting transcript, the internal fund/pass/track memo, and a debrief listing which objections are fixable before the real meeting.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill vc-partner-meeting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going