agentleFS
EarthOnlinePlayer5732EarthOnlinePlayer5732/my-skills/skills/upstream/analyze-results/SKILL.md

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

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

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
  1. Very specific:

    Check figures/, results/, or project-specific output directories

    line 16
  2. Common:

    Delta vs baseline: always compute relative improvement

    line 23
  3. Common:

    If multiple seeds: report mean +/- std, check reproducibility

    line 26
  4. Common:

    If sweeping a parameter: identify trends (monotonic, U-shaped, plateau)

    line 27
  5. Common:

    If findings are significant:

    line 38

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.