idea-discovery

Orchestrates a multi-phase research pipeline from literature survey to validated, pilot-tested ideas.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill idea-discovery-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: idea-discovery
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.claude/skills/idea-discovery
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill idea-discovery-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Going from a broad research direction to a validated, publication-worthy idea requires literature surveying, brainstorming, novelty verification, critical review, and pilot experiments — a process that is slow, unstructured, and easy to get wrong when done manually. ## Core Features & Use Cases - End-to-End Pipeline Orchestration: Chains literature survey, idea generation, novelty checking, external review, and method refinement into one automated workflow with checkpoints. - Empirical Validation: Runs bounded pilot experiments (max 2 hours per GPU, 8 GPU-hours total) on the top 2-3 ideas and ranks them by empirical signal rather than theoretical appeal. - Structured Deliverables: Produces a ranked IDEA_REPORT.md, a refined FINAL_PROPOSAL.md, and a claim-driven EXPERIMENT_PLAN.md ready for execution. - Use Case: A researcher says "find ideas for efficient video tokenization" and receives a literature landscape, 8-12 brainstormed ideas filtered by feasibility, pilot results on the top candidates, a senior-reviewer critique, and a concrete experiment roadmap. ## Quick Start Run the idea discovery pipeline on the research direction "machine-oriented video compression" and proceed automatically through each checkpoint.

Frequently Asked Questions about idea-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full research idea discovery pipeline?▼

Invoke the pipeline with a research direction, and it chains literature survey, idea generation, novelty check, external review, and method refinement phases automatically. Each phase ends with a checkpoint summarizing findings before proceeding.

How are research ideas validated before implementation?▼

Top ideas go through a deep novelty check against arXiv, Scholar, and Semantic Scholar, plus parallel pilot experiments capped at 2 hours per GPU. Ideas are ranked by empirical pilot signal, and published or negative-signal ideas are eliminated early.

What GPU budget do the pilot experiments use?▼

Pilots are limited to 2 hours per GPU per idea, a 3-hour hard timeout, at most 3 ideas in parallel, and 8 total GPU-hours. Over-budget ideas are flagged as needing manual pilot runs in the report.

Can I customize the pipeline defaults like pilot budget?▼

Yes, constants such as pilot hours, total GPU budget, auto-proceed behavior, reviewer model, and arXiv PDF downloading can be overridden inline when invoking the pipeline, for example by specifying a larger per-idea pilot budget.

What outputs does the idea discovery workflow produce?▼

It produces a ranked IDEA_REPORT.md with pilot and novelty results, plus refine-logs/FINAL_PROPOSAL.md, EXPERIMENT_PLAN.md, and EXPERIMENT_TRACKER.md for the top idea, ready to hand off to experiment execution.

What happens if all generated ideas are weak or already published?▼

Ideas failing novelty checks or showing negative pilot signals are eliminated and documented with reasons. If the user is unhappy with all ideas, the pipeline collects feedback and regenerates with updated constraints or refined scope.