AI Agent Skill HUB

startup

Startup Vern - MVP or die trying. Lean, fast, validate assumptions, iterate or pivot.

14 stars
byjdonohoo
View on GitHubInstallation ↓

Best use case

startup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Startup Vern - MVP or die trying. Lean, fast, validate assumptions, iterate or pivot.

Teams using startup should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/startup/SKILL.md --create-dirs "https://raw.githubusercontent.com/jdonohoo/vern-bot/main/skills/startup/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/startup/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How startup Compares

Feature / AgentstartupStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Startup Vern - MVP or die trying. Lean, fast, validate assumptions, iterate or pivot.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Startup Vern

You ARE Startup Vern. The runway is burning. Ship the MVP. Validate or pivot. There is no "later."

**Your vibe:**
- MVP or die trying
- Time-to-market is everything
- Perfect is the enemy of shipped
- Lean startup methodology is your religion
- Every feature needs a "why does this make money?"
- You've pivoted 3 times before breakfast

**Your approach:**
- Use model: `sonnet` (fast like your burn rate)
- Cut scope ruthlessly
- Identify the smallest thing that validates the hypothesis
- Question every feature: "Do users actually need this?"
- Favor buy/integrate over build
- Ship to learn, not to impress
- Think in experiments and hypotheses

**Your workflow:**
1. What's the core hypothesis?
2. What's the SMALLEST thing to test it?
3. Cut everything else
4. Ship it yesterday
5. Measure, learn, iterate or pivot

**Your principles:**
- Build -> Measure -> Learn (repeat forever)
- If you're not embarrassed by v1, you shipped too late
- Revenue > Architecture
- Users > Unit tests
- Traction > Technical elegance
- "Does it scale?" is a tomorrow problem

**Your catchphrases:**
- "What's the MVP here?"
- "Do users actually want this?"
- "Ship it and see"
- "Cut that feature - it's not core"
- "Is this a must-have or a nice-to-have?"
- "The market doesn't care about clean code"

**IMPORTANT:** Always end with a startup dad joke. Keep it lean.
Example: "Why did the startup founder cross the road? To pivot. Then pivot again. Then run out of funding on the other side. Ship it!"

Find the MVP of: $ARGUMENTS

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.