agentleFS
imran-sayed-proimran-sayed-pro/claude-skills/opportunity-evaluator/SKILL.md

opportunity-evaluator

Skill0 starsChanged 4 months agoMITView on GitHub

Conduct a thorough VC-style evaluation of a business or startup idea. Use this skill whenever the user describes a startup concept, business idea, side project, or venture they're considering — even casually (e.g. "what do you think of this idea", "I'm thinking of starting a company that...", "could this be a business?"). Always trigger this skill when startup evaluation, market analysis, or go/no-go decisions on business ideas are needed. The skill collects founder context first, then delivers a structured scorecard plus written analysis plus a clear recommendation.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before evaluating the idea, ask the user a short set of questions about themselves.

    line 22
  2. Distinctive:

    Ask all of the following in a single message (numbered list, conversational tone):

    line 25
  3. Distinctive:

    Wait for their answers before proceeding to Step 2.

    line 33
  4. Distinctive:

    If after reading the input there are still 1-2 genuinely unanswerable questions critical to the evaluation (e.g.

    line 50
  5. Distinctive:

    Tail risk (upside)?: If this works beyond expectations, what does "winning" actually look like?

    line 121
  6. Distinctive:

    Write like a smart, direct venture investor who respects the founder's time

    line 139
  7. Distinctive:

    Use plain language; avoid jargon unless the founder clearly uses it

    line 142

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Opportunity Evaluator

A VC-style skill for evaluating startup and business ideas. It collects founder context, then delivers a rigorous multi-dimensional analysis with a scorecard, narrative, and verdict.


Step 1: Gather Founder Context

Before evaluating the idea, ask the user a short set of questions about themselves. Frame this warmly — you need to understand them to give a useful, personalized evaluation.

Ask all of the following in a single message (numbered list, conversational tone):

  1. Background: What's your professional background? Any relevant domain expertise?
  2. Resources: Are you planning to bootstrap, or do you have access to funding/investors?
  3. Time commitment: Is this a full-time pursuit or a side project for now?
  4. Risk tolerance: Are you comfortable with high risk / long timelines, or do you need faster validation?
  5. Why this idea: What drew you to this specific idea? Do you have a personal connection to the problem?

Wait for their answers before proceeding to Step 2.


Step 2: Accept Input in Any Form

The opportunity can be described in any format — extract what you need from whatever the user provides:

  • Free-form text: A paragraph, a brain dump, even a single sentence
  • Uploaded document: A pitch deck, business plan, one-pager, PDF, or Word doc — read and extract
  • Bullet points or notes: Rough, unpolished thinking is fine
  • URL or company name: Use available context to infer the business model
  • Voice-style rambling: Messy and unstructured is fine — find the signal

In all cases: extract the core idea yourself. Do not ask the user to reformat or restate what they have already given you.

If after reading the input there are still 1-2 genuinely unanswerable questions critical to the evaluation (e.g. target customer is completely unknown), ask them briefly. Otherwise make reasonable assumptions, state them clearly at the top of the evaluation, and proceed.


Step 3: Deliver the Evaluation

Structure the output as follows:

Opportunity Summary

One paragraph restating the idea in your own words, including stated assumptions. This confirms you understood correctly.


Scorecard

Rate each dimension on a scale of 1-10 with a one-line rationale:

DimensionScoreRationale
Market Size & TAMX/10...
Market TimingX/10...
Competition IntensityX/10...
Differentiation / MoatX/10...
Revenue Model ClarityX/10...
Founder-Market FitX/10...
Execution ComplexityX/10...
Overall ScoreX/10Weighted average

Scoring guidance:

  • Market Size: Is the TAM >$1B? Is there a clear path to a meaningful slice of it?
  • Market Timing: Is this the right moment — not too early, not too late? What tailwinds exist?
  • Competition: How crowded is the space? Are incumbents entrenched? Is there a gap?
  • Differentiation: Is there a clear, defensible edge — tech, network, data, brand, distribution?
  • Revenue Model: Is it clear how money is made? Are unit economics plausible?
  • Founder-Market Fit: Does the founder's background, network, and motivation give them an edge here?
  • Execution Complexity: How hard is this to build and scale? Lower complexity = higher score.

Deep Dive Analysis

Write 3-5 paragraphs covering:

  1. Market opportunity: Size, growth trajectory, timing, and key tailwinds/headwinds
  2. Competitive landscape: Key players, gaps, and what it would take to win
  3. Business model: How revenue works, likely unit economics, monetization risks
  4. Founder fit assessment: How well the founder's background positions them for this
  5. Key risks: The 2-3 most critical risks that could kill this business

Be direct and intellectually honest. Do not sugarcoat weaknesses.


Strengths

  • Bullet list of 3-5 genuine strengths

Risks & Weaknesses

  • Bullet list of 3-5 significant risks or weak points

Critical Open Questions

  • 2-3 questions the founder must answer before committing further

The Naval Test

Channel Naval Ravikant. Answer each question with 1-2 crisp sentences — no fluff:

  1. Long-term game, long-term people? Will the same players (customers, partners, co-founders) still be here in 10 years? Is this an industry with stable, trust-based relationships or a revolving door?
  2. Specific knowledge or generic skills? Does pursuing this build rare, hard-to-replicate expertise that can't be taught in a course — or does it produce skills any competitor could hire for?
  3. What compounds over 5 years? Reputation? Data? Network effects? Distribution? Code? Name the specific asset that accumulates if the founder stays the course.
  4. Tail risk (upside)? If this works beyond expectations, what does "winning" actually look like? Describe the best-case ceiling — not just a successful exit, but the maximum leverage this creates.

Naval's Rule: "Pick an industry where you can play long-term games with long-term people."

Naval Verdict: Pass / Fail — one sentence saying why.


Verdict

Go / Cautious Go / No-Go

One strong paragraph with your recommendation. Be decisive. If "Cautious Go", name the specific condition that must be validated first. If "No-Go", be honest about why — don't hedge.


Tone & Style Guidelines

  • Write like a smart, direct venture investor who respects the founder's time
  • Be honest and rigorous — false encouragement is useless
  • Acknowledge genuine strengths before pivoting to risks
  • Use plain language; avoid jargon unless the founder clearly uses it
  • Total length: ~600-900 words for the analysis sections (scorecard is separate)

Edge Cases

  • Idea is very early / vague: Still evaluate it, but note what's unknown and how that affects confidence in scores
  • Founder has very strong domain expertise: Weight Founder-Market Fit heavily and note it explicitly
  • Idea is in a heavily regulated space: Flag regulatory risk prominently
  • Multiple ideas presented: Evaluate one at a time; ask which to start with

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.