/inno-idea-eval

id: inno-idea-eval
name: inno-idea-eval
version: 1.0.0
description: |-
  Multi-persona idea evaluation with quality gate.
stages: ["ideation"]
tools: ["read_file", "search_project", "write_file"]
summary: |-
  Multi-persona idea evaluation with quality gate. Evaluates ideas across 5 InnoEval dimensions (Clarity, Novelty, Validity, Feasibility, Significance) using 3 reviewer personas and a meta-review. Sits between inno-idea-generation and inno-c...
primaryIntent: ideation
intents: ["ideation", "evaluation"]
capabilities: ["research-planning"]
domains: ["general"]
keywords: ["inno-idea-eval", "idea evaluation", "research-planning", "inno", "idea", "eval", "multi", "persona", "evaluation", "quality", "gate", "evaluates"]
source: builtin
status: verified
upstream:
  repo: dr-claw
  path: skills/inno-idea-eval
  revision: 8322dc4ef575affaa374aa7922c0a0971c6db7d7
resourceFlags:
  hasReferences: true
  hasScripts: false
  hasTemplates: false
  hasAssets: false
  referenceCount: 3
  scriptCount: 0
  templateCount: 0
  assetCount: 0
  optionalScripts: false

inno-idea-eval

Canonical Summary

Multi-persona idea evaluation with quality gate. Evaluates ideas across 5 InnoEval dimensions (Clarity, Novelty, Validity, Feasibility, Significance) using 3 reviewer personas and a meta-review. Sits between inno-idea-generation and inno-c...

Trigger Rules

Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.

Resource Use Rules

• Read from `references/` only when the current task needs the extra detail.

Execution Contract

• Resolve every relative path from this skill directory first.
• Prefer inspection before mutation when invoking bundled scripts.
• If a required runtime, CLI, credential, or API is unavailable, explain the blocker and continue with the best manual fallback instead of silently skipping the step.
• Do not write generated artifacts back into the skill directory; save them inside the active project workspace.

Upstream Instructions

Inno Idea Eval

Directory structure

skills/inno-idea-eval/
├── SKILL.md                                    ← this file
├── prompts/
│   ├── build_eval_query.md                     ← Per-persona evaluation query (all 5 dims)
│   ├── build_evidence_assembly.md              ← How to compose evidence from pipeline artifacts
│   ├── build_meta_review_query.md              ← Area-chair aggregation of 3 persona reviews
│   ├── build_novelty_queries.md                ← Query extraction for novelty verification (Step 0.5a)
│   ├── build_novelty_analysis.md               ← Similarity analysis for novelty verification (Step 0.5c)
│   └── build_refinement_feedback_query.md      ← Structured feedback for refinement loop
└── references/
    ├── eval_agent_instructions.md              ← Full eval agent system prompt + scoring rubrics
    ├── novelty_verification_config.md          ← Novelty search config, threat levels, fast-fail protocol
    └── reviewer_personas.md                    ← 3 persona definitions + evidence filter logic

> **How to use the resource files**: Each prompt template in `prompts/` documents > the exact parameters, the full text template, and usage notes (when it is a new > conversation vs. appended message, how to format evidence blocks, etc.). > The `references/` directory contains the Eval Agent's complete system instructions > including its scoring rubrics, persona definitions, and evidence filter logic. > Consult these files for the authoritative details; the steps below provide a summary.

Inputs

Paths for `Ideation/ideas` and `Ideation/references` come from **`instance.json`** (`instance.Ideation.ideas`, `instance.Ideation.references`). They are **absolute** in Dr. Claw-created projects; use as-is. If relative, resolve with `path.join(project_path, value)`.

| Parameter | Required | Description | |----------------------|----------|-------------| | `selected_idea` | Yes | The idea to evaluate, read from `Ideation/ideas/selected_idea.txt` | | `references` | No\* | Pre-formatted string listing all source papers (from inno-prepare-resources) | | `prepare_res` | No\* | Full text response from the Prepare Agent (selected repositories and reasoning) | | `download_res` | No\* | Result log from downloading arXiv paper sources | | `data_module` | No\* | The imported metaprompt module (provides `TASK` field describing the ML task) | | `context_variables` | Yes | Shared context dictionary (must contain `final_selected_idea_data`) |

\*Standalone mode: only `selected_idea` required; evaluation proceeds ungrounded with a noted limitation.

Outputs

| Output | Description | |------------------------------------------------|-------------| | `eval_report` | Full markdown evaluation report (meta-review) | | `eval_scores` | Structured JSON: per-dimension, per-persona, aggregated | | `eval_decision` | One of: `strong_accept` / `accept` / `borderline_accept` / `borderline_reject` / `reject` | | `eval_feedback` | Strengths/weaknesses/suggestions (for refinement or downstream) | | `context_variables["idea_evaluation_result"]` | Complete structured result dict |

Cache file outputs

Each step produces **two kinds** of files:

1. **`.txt` files** (primary) -- the full markdown content of each review, written directly to `Ideation/ideas/` 2. **`.json` files** (derived) -- structured metadata under `Ideation/ideas/logs/`, whose text fields **must be copied verbatim** from the corresponding `.txt` files (never summarized)

Full directory layout

Ideation/ideas/
├── novelty_grounding_report.txt