mcpbeat

Nanoresearch Planning

openraiser/nanoresearch-planning

Produce an experiment blueprint from a research hypothesis

362 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1480
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OpenRaiser/NanoResearch --skill nanoresearch-planning

The instruction itself

6 sections, as written by the author

Planning Skill

Purpose

Take the selected hypothesis from ideation and produce a detailed experiment blueprint specifying datasets, baselines, evaluation metrics, and ablation groups.

Tools Required

None. This skill operates entirely through LLM reasoning over the ideation output.

Input

  • ideation_output: Path to papers/ideation_output.json produced by the ideation skill

Process

  • Parse the selected hypothesis and supporting literature from the ideation output
  • Identify candidate datasets that are publicly available and appropriate for validating the hypothesis
  • Select 2-4 baseline methods from the surveyed literature for comparison
  • Define primary and secondary evaluation metrics aligned with the hypothesis
  • Design ablation groups that isolate each novel component of the proposed approach
  • Estimate computational requirements and timeline for each experiment
  • Compile everything into a structured experiment blueprint

Output

Produces papers/experiment_blueprint.json containing:

  • Selected hypothesis (carried forward)
  • Dataset specifications (name, source, splits, preprocessing steps)
  • Baseline methods with references
  • Evaluation metrics and success criteria
  • Ablation study design (groups, variables, expected outcomes)
  • Resource estimates and experiment schedule

How to use it

Copy the folder

Take openraiser/nanoresearch-planning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.