wanshuiyin/auto-claude-code-research-in-sleep

analyze-results

Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results", "compare", or needs to interpret experimental data.

First seen Mar 12, 2026

Installation

$ npx skills add wanshuiyin/auto-claude-code-research-in-sleep --skill analyze-results

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from wanshuiyin/auto-claude-code-research-in-sleep · top by installs.

npx skills add wanshuiyin/auto-claude-code-research-in-sleep

Browse all from wanshuiyin/auto-claude-code-research-in-sleep

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 15.9K
License LICENSE
Default branch main
Open issues 53
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(*), Read, Grep, Glob, Write, Edit
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,660 B
  • docs SUMMARY.md 201 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 436 installs

SKILL.md

Analyze Experiment Results

Analyze: $ARGUMENTS

Workflow

Step 1: Locate Results

Find all relevant JSON/CSV result files:

  • Check figures/, results/, or project-specific output directories
  • Parse JSON results into structured data

Step 2: Build Comparison Table

Organize results by:

  • Independent variables: model type, hyperparameters, data config
  • Dependent variables: primary metric (e.g., perplexity, accuracy, loss), secondary metrics
  • Delta vs baseline: always compute relative improvement

Step 3: Statistical Analysis

  • If multiple seeds: report mean +/- std, check reproducibility
  • If sweeping a parameter: identify trends (monotonic, U-shaped, plateau)
  • Flag outliers or suspicious results

Step 4: Generate Insights

For each finding, structure as:

  1. Observation: what the data shows (with numbers)
  2. Interpretation: why this might be happening
  3. Implication: what this means for the research question
  4. Next step: what experiment would test the interpretation

Step 5: Update Documentation

If findings are significant:

  • Propose updates to project notes or experiment reports
  • Draft a concise finding statement (1-2 sentences)

Output Format

Always include:

  1. Raw data table
  2. Key findings (numbered, concise)
  3. Suggested next experiments (if any)