jevbooks

← All projects

killmyidea

monteduro/killmyidea · Homepage

Describe a startup idea; Jev decides kill, fix, or ship.

Automated README summary

Automatically summarized from the README on 4 Nov 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A web app and MCP server for indie hackers and founders: submit a startup idea and get a KILL / FIX / SHIP verdict with a 0–100 score, best signal and biggest risk, without any generative LLM.

How it uses Jev

Jev answers 10 typed questions in parallel on the idea text: 8 indie-hacker questions scored 0–4 (Real problem, Clear customer, Demand, Money, Reach, Different, Buildable, Shareable), plus category and understandability. Scores ×25 are weighted-averaged; below 0.3 understandability gates the verdict.

Primitives:choicescorenoul

Technique worth stealing

Turn each qualitative question into five concrete situations Jev scores 0–4, then weight-average into a single verdict with a clarity gate.

Try it

npm install, set TYPESAFE_API_KEY in .env, then npm run dev (or TYPESAFE_MOCK=1 for fake data).

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.14.0
Project signals
jev-1.14.0
Category
jev-1.14.0
Pattern tags
jev-1.14.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.96
  • Shows a System One patternFound in material0.97
  • Describes handling uncertaintynot found in the excerpt0.08
  • Reports measured numbersnot found in the excerpt0.03
  • Is a runnable toolFound in material0.96
  • Top-10 learning shortlist signalFound in material0.61
  • Is a replica of the modelnot found in the excerpt0.02
  • Solves a common problem (0–2)score on a 0–2 scale0.86 / 2
  • About JevFound in material0.99
Signals
Jev is core to the project0.96Shows a System One pattern0.97Describes handling uncertainty0.08Reports measured numbers0.03Is a runnable tool0.96Top-10 learning shortlist signal0.61Is a replica of the model0.0200.51Solves a common problem (0–2)0.86 / 2012

no-judgment band (0.40–0.60)

Design patterns
Scorecard0.98Questionnaire0.96Traffic light0.85Flight recorder0.61Prefetch0.37Viewfinder0.29Funnel0.25Check-up0.2500.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 4 Nov 2026.