analyze-results
Skill17 starsChanged 3 months agoMITView on GitHub
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results", "compare", or needs to interpret experimental data.
11 other projects use a version of this, 5 of them edited.
How people change it
All 5 edited versions we compared keep every one of its 5 rules.
Of the 5 edited versions we compared: 5 keep every rule.
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- AfonsoZhang/auto-research-systemtheir own version, first seen Nov 15, 2026
- Seraght/claude-skillstheir own version, first seen Oct 25, 2026
- MacroMan5/autotrain-yolotheir own version, first seen Oct 25, 2026
- yvesory/academic-research-suiteedited, first seen Oct 9, 2026
- talhaMah56/claude_skillsword for word, first seen Sep 12, 2026
- wanshuiyin/Auto-claude-code-research-in-sleepword for word, first seen Jul 15, 2026
Other versions11 projects use a version of this.
Word for word · 2
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19k100% same
- talhaMah56/claude_skills★ 0100% same
Edited · 5
- zjunlp/Mechanist★ 7598% same
- Chanw-research/claude-code-paper-writing★ 4298% same
- yvesory/academic-research-suite★ 9100% same
- Yusong-Enceladus/claude-skills★ 898% same
- raja21068/AutoResearch★ 298% same
Wrote their own version · 4
- sunnnybala/Rstack★ 69same name
- MacroMan5/autotrain-yolo★ 8same name
- AfonsoZhang/auto-research-system★ 1same name
- Seraght/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- ai4ai-model-optimizerSkill
- auto-discovery-loggerSkill
- cross-model-verifierSkill
- handoffSkill
- research-context-checkpointSkill
- auto-review-loopSkill
- collaborating-with-codexSkill
- idea-discoverySkill
- monitor-experimentSkill
- research-litSkill
- research-reviewSkill
The file
We split this skill into the rules it gives an agent
5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.
4
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Check figures/, results/, or project-specific output directories
- Common: line 23
Delta vs baseline: always compute relative improvement
- Common: line 26
If multiple seeds: report mean +/- std, check reproducibility
- Common: line 27
If sweeping a parameter: identify trends (monotonic, U-shaped, plateau)
- Common: line 38
If findings are significant:
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Observation: what the data shows (with numbers)
- Interpretation: why this might be happening
- Implication: what this means for the research question
- 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:
- Raw data table
- Key findings (numbered, concise)
- Suggested next experiments (if any)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

