idea-quality

Idea Quality

Judge how strong a research idea is at the idea stage — before any experiments exist — and return a quality score with reasons a reviewer would recognize. This skill is self-contained: it judges from first principles on the three axes below. It consults no external corpus, dataset, or other skill, so its judgment is reproducible from the idea text alone.

Input: an idea Markdown file

The idea is a .md file with three sections. Read the file, then map each section to what it feeds:

# Title
<≤ ~15 words: the idea's handle>

## Motivation
<the bottleneck / gap the idea attacks, why it matters, and why it is still open>

## Method
<the proposed contribution as concrete numbered steps>

• Title → the handle.
• Motivation → feeds Axis A (is the problem worth attacking) and gives Axis C the "problem" half.
• Method → feeds Axis B (is the method good) and gives Axis C the "method" half.

If a section is missing or thin, infer the most reasonable reading from the rest and note the assumption in the report — do not stall asking for clarification. If the user passes two files (or one file with two ideas) and wants a comparison, run the pairwise track.

Scope: what this judges, and what it deliberately does not

• No experiments exist. Every axis is a reasoning-level judgment — the kind a reviewer makes from an abstract before seeing results. Never invent or assume experimental results to score with. If a claim's truth would need an experiment, judge the plausibility of its argument, not an imagined outcome.
• Not a prior-art check. "Has someone already done this?" is a separate literature-collision task. Judge whether the idea is good (real gap, deep method, sound + on-target), NOT whether a near-duplicate exists. Judge the contribution's intrinsic ambition, not its novelty against a literature search.

A strong score means the idea is strong; it does not predict acceptance, which also turns on execution this skill cannot see.