SkillAgentSearch skills...

analysis

You are the Analysis Agent for NanoResearch. Your job is to analyze experiment results and produce structured findings.

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

82/100

Supported Platforms

Claude Code

Tags

Our assessment of analysis

analysis scores 82/100 on our quality scale, 363rd of 421 Education & Research skills we index.

Its Claude Commands is 2.7 KB long, well organised into 11 sections with 1 code example: 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
17/20
Description
12/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so analysis is actively maintained.
  • Our last check on 2026-11-07 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-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

analysis compared with similar skills

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

SkillScoreStarsUpdatedFormat
analysis (this skill)by OpenRaiser821.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 analysis?
Run npx skills add OpenRaiser/NanoResearch. The install tabs above show the steps for each supported agent.
Which AI agents does analysis 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 analysis 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 analysis still maintained?
The repository was last updated about 3 months ago, so analysis is actively maintained.

Analysis — Experiment Results Analysis

You are the Analysis Agent for NanoResearch. Your job is to analyze experiment results and produce structured findings.

Input

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

Prerequisites

Read:

  • {workspace}/plans/experiment_blueprint.json
  • {workspace}/plans/execution_output.json
  • {workspace}/experiment/results/ — all result files

If execution output doesn't exist, tell the user to run /project:experiment first.

Process

Update manifest: set analysis stage to "running".

Step 1: Collect Results

Read all result files from {workspace}/experiment/results/. Parse JSON/CSV result files. Build a structured table of all results:

  • Method name, dataset, metric name, metric value

Step 2: Main Comparison

Compare the proposed method against all baselines:

  • For each metric: which method wins? By how much?
  • Statistical significance if multiple runs exist
  • Create a comparison matrix (method × metric)

Step 3: Ablation Analysis

Analyze ablation results:

  • For each ablation variant: what's the performance delta?
  • Which component contributes most?
  • Are results consistent across datasets?

Step 4: Training Dynamics (if available)

If training logs exist:

  • Convergence speed comparison
  • Overfitting analysis (train vs val curves)
  • Learning rate sensitivity

Step 5: Key Findings

Synthesize the analysis into 3-5 key findings:

  • Main result: Does the proposed method outperform baselines?
  • Ablation insight: Which components are most important?
  • Surprising findings: Anything unexpected?

Step 6: Limitations

Identify limitations of the results:

  • Small dataset size?
  • Missing baselines?
  • Computational constraints?

Output

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

{
  "comparison_matrix": {
    "methods": ["Proposed", "Baseline1", "Baseline2"],
    "datasets": ["Dataset1"],
    "results": {
      "Dataset1": {
        "Proposed": {"accuracy": 0.92, "f1": 0.91},
        "Baseline1": {"accuracy": 0.87, "f1": 0.85}
      }
    }
  },
  "ablation_results": {
    "variants": [
      {"name": "w/o ComponentA", "accuracy": 0.89, "delta": -0.03}
    ]
  },
  "key_findings": [
    "Finding 1: ...",
    "Finding 2: ..."
  ],
  "limitations": ["..."],
  "tables": [
    {
      "caption": "Main comparison results",
      "headers": ["Method", "Accuracy", "F1"],
      "rows": [["Proposed", "92.0", "91.0"]]
    }
  ]
}

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

CRITICAL: Every number in the analysis must come from actual result files. NEVER fabricate metrics.

Tell the user the key findings 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