agentleFS
akash-joshiakash-joshi/agent-skills/skills/startup-ideas/idea-scoring/SKILL.md

idea-scoring

Skill8 starsChanged 3 months agoMITView on GitHub

Score and rank a shortlist of startup ideas to decide which one to build. Use when the user has several candidate ideas and asks "which idea should I pick," "how do I prioritise these," "how do I choose between ideas," or mentions scoring, ranking, or culling a list. This is the "Order & Cull" stage of the B.R.O.T.H. framework. For generating the shortlist, see founder-market-fit and trend-research. For picking the entry angle once an idea is chosen, see market-entry-strategies.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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 scoring, widen the field so you are choosing from the best options, not the first few.

    line 25
  2. Distinctive:

    When ranking, weigh two different kinds of hard.

    line 38
  3. Distinctive:

    Run a Deep Research expansion to widen and deepen the field.

    line 51
  4. Distinctive:

    Commit to the top one or two.

    line 54
  5. Distinctive:

    Do not skip the expansion and score only your first three ideas.

    line 58
  6. Distinctive:

    Do not ignore "most interesting." An idea you find dull will die of neglect.

    line 59
  7. Distinctive:

    Do not chase the highest market-size score alone.

    line 60
  8. Distinctive:

    Do not keep everything. The output of this stage is a decision, not a longer list.

    line 61

≈ “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

Idea Scoring (Order & Cull)

You help the user go from a long list of researched ideas down to the one worth building. Good techniques make finding ideas easy, sometimes too easy. This stage is the discipline that whittles the pile down to a single committed direction.

The scoring model

Score each candidate idea from 1 to 5 on four questions. Higher is better.

  1. Biggest market size? Is there enough demand and enough addressable spend to reach roughly $10k MRR?
  2. Lowest competition? Is the market proven but not saturated, with a visible gap to enter through? (Some competition is good; a crowded field with no gap is not.)
  3. Most interesting? Will you still care in 12 months? Boredom kills bootstrapped projects as reliably as no demand.
  4. Can I build it? Does it fit your skills and constraints, or can you realistically learn what's missing?

Total the four scores per idea. Rank the list. The top one or two graduate to strategy.

How to expand before you cull

Before scoring, widen the field so you are choosing from the best options, not the first few. Use Deep Research (or your LLM's equivalent) with the keywords and competitor list from earlier stages.

Prompt shape:

"Here are my target market, the problems, and a list of competitors: [paste]. Do deep research to expand this into a fuller set of opportunities. For each: estimate market size and demand signals, list direct and indirect competitors, note how saturated it is and where the gaps are, and flag how hard it would be to validate and to build. End with an opinionated view of the two or three biggest opportunities and why."

Expected outputs from that research:

  • Deeper competitor analysis per direction
  • An opinionated view of the biggest opportunities

Then you score the expanded set, not just your original hunches.

Validation difficulty vs execution difficulty

When ranking, weigh two different kinds of hard. An idea can be easy to validate but hard to build, or vice versa. The three archetypes:

Entry typeValidation difficultyExecution difficulty
Direct competitor (go at a proven market)EasiestHardest (you must be genuinely better or cheaper)
Indirect competitor (adjacent market)MediumMedium
Growing trend (early mover)Hardest (demand not yet proven)Easiest, and first-mover advantage if you are right

There is no free lunch: the easier something is to validate, the harder it usually is to execute against entrenched players, and vice versa. Pick the trade-off that matches your strengths, then confirm the specific angle in market-entry-strategies.

Workflow

  1. Gather surviving candidates from research.
  2. Run a Deep Research expansion to widen and deepen the field.
  3. Score every candidate 1 to 5 on market size, competition, interest, and buildability.
  4. Overlay the validation-vs-execution trade-off.
  5. Commit to the top one or two. Cull the rest without regret.

What NOT to do

  • Do not skip the expansion and score only your first three ideas. You will miss better ones.
  • Do not ignore "most interesting." An idea you find dull will die of neglect.
  • Do not chase the highest market-size score alone. A huge market you cannot enter or cannot stand is worthless.
  • Do not keep everything. The output of this stage is a decision, not a longer list.

Related skills

  • founder-market-fit and trend-research - produce the candidates this stage ranks
  • market-entry-strategies - choose the angle for the idea you commit to
  • ship-v1 - build the winner
  • demand-first-validation - the mindset check underlying every score

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.