agentleFS
shawnpangshawnpang/startup-founder-skills/skills/startup-context/SKILL.md

startup-context

Skill331 starsChanged 8 months agoMITView on GitHub

When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user says "let me tell you about my startup" or similar

    line 15
  2. Distinctive:

    When any skill detects missing context and needs to gather it

    line 16
  3. Distinctive:

    If no context exists, ask these in order (group related questions, don't ask all at once):

    line 78
  4. Very specific:

    Write the completed context to .agents/startup-context.md and confirm with the user.

    line 97
  5. Distinctive:

    Keep this document factual, not aspirational — other skills need accurate context

    line 101
  6. Distinctive:

    Update it whenever the user shares new information (new hire, funding, pivot, etc.)

    line 102
  7. Distinctive:

    If a field is unknown, mark it as "TBD" rather than guessing

    line 103

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Startup Context

This is the foundation skill. Every other skill reads this context first to produce tailored, specific output instead of generic advice.

When to Use

  • First time a user runs any skill and no context file exists
  • When the user says "let me tell you about my startup" or similar
  • When any skill detects missing context and needs to gather it

Workflow

  1. Check for existing context — look for .agents/startup-context.md in the project root
  2. If missing, interview the founder — ask the questions below, one section at a time
  3. Generate the context file — write structured markdown to .agents/startup-context.md
  4. Keep it updated — when the user shares new info that changes context, update the file

Context Document Structure

# Startup Context

## Company
- **Name:**
- **One-liner:** (what you do in one sentence)
- **Stage:** (idea / pre-seed / seed / series A / series B / growth)
- **Founded:** (date)
- **Location:** (city/remote)
- **Legal entity:** (Delaware C-Corp, LLC, etc.)

## Product
- **What it does:** (2-3 sentences)
- **Category:** (e.g., developer tools, fintech, healthtech)
- **Platform:** (web app, mobile, API, desktop, hardware)
- **Tech stack:** (languages, frameworks, infra)
- **Current state:** (idea, prototype, beta, launched, scaling)

## Market
- **Target customer:** (who buys / who uses — be specific)
- **ICP:** (ideal customer profile — industry, size, role, pain)
- **TAM/SAM/SOM:** (if known)
- **Competitors:** (top 3-5, how you differ)
- **Positioning:** (why you vs alternatives)

## Business Model
- **Revenue model:** (SaaS, usage-based, marketplace, etc.)
- **Pricing:** (current pricing or planned)
- **Current MRR/ARR:** (if applicable)
- **Key metrics:** (the 3-5 numbers you track most)

## Team
- **Founders:** (names, roles, backgrounds)
- **Team size:**
- **Key hires needed:**
- **Advisors/board:**

## Fundraising
- **Total raised:**
- **Last round:** (amount, date, lead investor)
- **Current runway:** (months)
- **Next raise:** (target amount, timeline, what it's for)

## Goals
- **Next 3 months:**
- **Next 12 months:**
- **Biggest challenge right now:**

Interview Questions

If no context exists, ask these in order (group related questions, don't ask all at once):

Round 1 — The basics:

  • What does your startup do? Who is it for?
  • What stage are you at? (idea through scaling)
  • What's your business model?

Round 2 — Market & traction:

  • Who's your ideal customer? Be as specific as you can.
  • Who are your main competitors? What's different about you?
  • What traction do you have? (users, revenue, waitlist, LOIs)

Round 3 — Team & resources:

  • Who's on the team? What are their backgrounds?
  • How much have you raised? What's your runway?
  • What are you trying to accomplish in the next 3 months?

Output

Write the completed context to .agents/startup-context.md and confirm with the user.

Notes

  • Keep this document factual, not aspirational — other skills need accurate context
  • Update it whenever the user shares new information (new hire, funding, pivot, etc.)
  • If a field is unknown, mark it as "TBD" rather than guessing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.