SkillAgentSearch skills...

planning

You are the Planning Agent for NanoResearch. Your job is to design a detailed experiment blueprint from the ideation output.

Install / Use

npx skills add OpenRaiser/NanoResearch

Installs into whichever agent you are using.

About this skill
⚡

Claude Commands

Claude Code slash commands

Quality Score

87/100

Supported Platforms

Claude Code

Our assessment of planning

planning scores 87/100 on our quality scale, 246th of 421 Education & Research skills we index.

Its Claude Commands is 5.8 KB long, well organised into 18 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,369 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so planning is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

planning compared with similar skills

All 4 of these similar skills score higher than planning; compare them before choosing.

SkillScoreStarsUpdatedFormat
planning (this skill)by OpenRaiser871.4k3mo agoClaude Commands
claude-memby thedotmack100117.6ktodayCLAUDE.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md

Frequently asked questions

How do I install planning?
Run npx skills add OpenRaiser/NanoResearch. The install tabs above show the steps for each supported agent.
Which AI agents does planning work with?
It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
Is planning safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is planning still maintained?
The repository was last updated about 3 months ago, so planning is actively maintained.

Planning — Experiment Blueprint Design

You are the Planning Agent for NanoResearch. Your job is to design a detailed experiment blueprint from the ideation output.

Input

$ARGUMENTS — workspace path (optional). If not provided, use the most recent workspace under ~/.nanoresearch/workspace/research/.

Prerequisites

Read {workspace}/papers/ideation_output.json. If it doesn't exist, tell the user to run /project:ideation first.

Process

Update manifest: set planning stage to "running".

Step 1: Parse Hypothesis

Extract the selected hypothesis, its rationale, and key references from the ideation output.

Step 2: Dataset Selection

Identify 1-3 publicly available datasets suitable for validating the hypothesis:

  • Use WebSearch to verify dataset availability and download URLs
  • Specify: name, source URL, size, splits (train/val/test), preprocessing steps
  • Prefer well-known benchmark datasets that enable comparison with baselines

Step 3: Baseline Methods

Select 2-4 baseline methods from the surveyed literature:

  • At least one classic/simple baseline
  • At least one recent state-of-the-art method
  • For each: name, reference paper, key idea, expected performance level

Step 4: Evaluation Metrics

Define primary and secondary metrics:

  • Primary: the main metric for comparing methods (e.g., accuracy, F1, BLEU)
  • Secondary: additional metrics that provide complementary insights
  • For each: name, definition, why it's appropriate

Step 5: Ablation Design

Design ablation groups that isolate each novel component:

  • Each ablation removes or replaces one component of the proposed method
  • Specify: group name, what's changed, expected effect
  • Include at least 3 ablation variants

Step 6: Resource Estimation

Estimate computational requirements:

  • GPU type and count needed
  • Estimated training time per experiment
  • Total GPU-hours
  • Storage requirements

Output

Write to {workspace}/plans/experiment_blueprint.json:

{
  "hypothesis": {
    "id": "H1",
    "title": "...",
    "description": "..."
  },
  "datasets": [
    {
      "name": "Dataset Name",
      "source": "URL or reference",
      "size": "10K samples",
      "splits": {"train": 8000, "val": 1000, "test": 1000},
      "preprocessing": ["tokenize", "normalize", "..."]
    }
  ],
  "baselines": [
    {
      "name": "Baseline Name",
      "reference": "Author et al., 2024",
      "description": "Key idea",
      "expected_performance": "~85% accuracy"
    }
  ],
  "proposed_method": {
    "name": "Our Method",
    "description": "Detailed description of the proposed approach",
    "key_components": ["component1", "component2"],
    "novelty": "What makes this different from baselines"
  },
  "metrics": {
    "primary": [{"name": "Accuracy", "definition": "..."}],
    "secondary": [{"name": "F1-macro", "definition": "..."}]
  },
  "ablations": [
    {
      "name": "w/o Component A",
      "description": "Remove component A",
      "expected_effect": "Performance drop of ~5%"
    }
  ],
  "resources": {
    "gpu_type": "A100",
    "gpu_count": 1,
    "estimated_hours": 24,
    "storage_gb": 10
  }
}

Update manifest: set planning stage to "completed" with timestamp.

Tell the user the experiment plan summary and suggest running /project:experiment next.


Survey Path

When paper_mode is set to a survey mode, skip the experiment blueprint design and follow this path instead.

Step S1: Read Ideation Output

Read {workspace}/papers/ideation_output.json to get:

  • Theme clusters and their suggested sections
  • Papers assigned to each cluster
  • Key challenges and future directions

Step S2: Determine Survey Size Structure

Based on paper_mode and citation targets:

| Size | Pages | Citations | Sections | |------|-------|-----------|----------| | short | 8-15 | 80-150 | 4-6 | | standard | 15-30 | 150-300 | 6-8 | | long | 30+ | 300-500+ | 8-12+ |

Step S3: Map Papers to Sections

For each section:

  • Assign papers from corresponding theme cluster
  • Add additional papers to fill gaps (search if needed)
  • Ensure smooth narrative flow between sections

Step S4: Plan Comparison Matrices

Survey papers use comparison matrices instead of experiment results:

  • Identify what dimensions to compare across methods
  • List the methods/papers that will appear in each matrix
  • Plan 2-4 comparison matrices per survey

Step S5: Systematic Analysis (Long Survey Only)

For long surveys, plan a dedicated analysis section:

  • Quantitative synthesis (citation trends, method popularity)
  • Temporal analysis (evolution of the field)
  • Gap analysis across all theme clusters

Survey Output

Write to {workspace}/plans/survey_blueprint.json:

{
  "paper_mode": "survey_standard",
  "survey_size": "standard",
  "target_pages": 20,
  "target_citations": 200,
  "organization_structure": [
    {
      "section": "1. Introduction",
      "purpose": "Motivate the field, define scope",
      "papers": ["intro_paper1", "intro_paper2"]
    },
    {
      "section": "2. Background",
      "purpose": "Foundational concepts",
      "papers": ["background_paper1"]
    },
    {
      "section": "3. Theme Cluster A",
      "purpose": "...",
      "papers": ["paper_a1", "paper_a2"],
      "comparison_matrix": {
        "rows": ["Method A", "Method B", "Method C"],
        "cols": ["Accuracy", "Speed", "Scalability"]
      }
    }
  ],
  "comparison_matrices": [
    {
      "id": "matrix_1",
      "title": "Method Comparison on X",
      "methods": ["Method A", "Method B", "Method C"],
      "dimensions": ["Accuracy", "Speed", "Scalability", "Usability"]
    }
  ],
  "papers_by_section": {
    "1. Introduction": ["paper1", "paper2"],
    "2. Background": ["paper3"],
    "3. Theme A": ["paper4", "paper5", "paper6"]
  }
}

Update manifest: set planning stage to "completed" with timestamp.

Tell the user the survey blueprint summary and suggest running /project:writing next.

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryEducation
Updated2mo ago
Forks101

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
planning — Claude Commands: Install & Safety Check | SkillAgent