Nanoresearch Planning Agent Skill
Produce an experiment blueprint from a research hypothesis
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/OpenRaiser/NanoResearch --skill nanoresearch-planningThe instruction itself
6 sections, as written by the authorPlanning 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 topapers/ideation_output.jsonproduced 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
Other skills for the same job
different authors, same section of the catalogue
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls. Never use for ranking people or consequential decisions.
Loop 2 of the Three-Loop Integrated Development System. META-SKILL that dynamically compiles Loop 1 plans into agent+skill execution graphs. Queen Coordinator selects optimal agents from 86-agent registry and assigns skills (when available) or custom instructions. 9-step swarm with theater detection and reality validation. Receives plans from research-driven-planning, feeds to cicd-intelligent-recovery. Use for adaptive, theater-free implementation.
Loop 1 of the Three-Loop Integrated Development System. Research-driven requirements analysis with iterative risk mitigation through 5x pre-mortem cycles using multi-agent consensus. Feeds validated, risk-mitigated plans to parallel-swarm-implementation. Use when starting new features or projects requiring comprehensive planning with <3% failure confidence and evidence-based technology selection.
Find, compare, and research trade shows, exhibitions, expos, and industry events by vertical, region, date, or audience. Use this skill whenever the user wants to discover which trade shows exist for their industry, compare multiple events side-by-side, decide which shows are worth attending or exhibiting at, look up event dates and venues, research exhibitor counts or visitor profiles, or plan an annual trade show calendar. Also triggers on questions like 'what are the best shows for [industry]', 'when is [show name]', 'should we go to [event] or [event]', 'find me exhibitions in Germany for packaging', 'trade show calendar 2026', 'exhibition calendar Europe', 'B2B trade shows', 'what industry events should I attend', 'upcoming trade fairs', or even vague requests like 'we need to get in front of more buyers — what events should we be at'. If the user mentions any specific trade show by name (CES, MEDICA, Hannover Messe, Interpack, SXSW, Bauma, etc.) and wants information about it, use this skill.
How to use it
Take openraiser/nanoresearch-planning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.