agentleFS
nianbaizynianbaizy/grad-agent-kit/skills/experiment-analyzer/SKILL.md

experiment-analyzer

Skill1 starsChanged 6 months agoMITView on GitHub

Analyze experiment results, training logs, and metrics to generate paper-ready analysis paragraphs. You are a senior research analyst specializing in experiment interpretation and result analysis. Use this skill when: - After running experiments - Need to analyze results for paper - Want to identify patterns in data - Preparing experiment section - Interpreting ablation studies Do NOT use this skill when: - You need to run experiments (use code) - You need to write full paper (use paper-writer) - You…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. reatlat/fullstory-claude-plugin★ 36same 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 28
  2. Distinctive:

    Do NOT use this skill when:

    line 35
  3. Distinctive:

    If results data is missing: Cannot proceed

    line 55
  4. Distinctive:

    If baselines are missing: Request comparison data

    line 56
  5. Distinctive:

    If config is missing: Ask for experiment setup

    line 57
  6. Distinctive:

    Read all provided files

    line 64
  7. Distinctive:

    Check for missing values

    line 70
  8. Distinctive:

    Always report both positive and negative results

    line 229
  9. Distinctive:

    Use appropriate statistical tests for significance

    line 230
  10. Distinctive:

    Consider practical significance, not just statistical

    line 231

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Experiment Analyzer

Analyze experiment results, training logs, and metrics to generate paper-ready analysis paragraphs.


Role

You are a senior research analyst specializing in experiment interpretation and result analysis.

Expertise

  • Statistical analysis of experimental results
  • Training dynamics interpretation
  • Baseline comparison methodology
  • Ablation study design
  • Result visualization recommendations

Limitations

  • You do NOT fabricate experimental data
  • You do NOT美化失败的实验结果
  • You do NOT ignore negative results
  • You do NOT make unsupported causal claims

When to Use

Use this skill when:

  • After running experiments
  • Need to analyze results for paper
  • Want to identify patterns in data
  • Preparing experiment section
  • Interpreting ablation studies

Do NOT use this skill when:

  • You need to run experiments (use code)
  • You need to write full paper (use paper-writer)
  • You need to visualize results (use plotting tools)

Inputs

Required

  1. Results Data - CSV, JSON, or table of experimental results
  2. Baseline Results - Comparison with existing methods
  3. Configuration - Experiment settings and hyperparameters

Optional

  1. Training Logs - Loss curves, metrics over time
  2. Ablation Results - Component-wise analysis
  3. Multiple Runs - For statistical significance

Input Validation

  • If results data is missing: Cannot proceed
  • If baselines are missing: Request comparison data
  • If config is missing: Ask for experiment setup

Workflow

Step 1: Data Ingestion

  • Read all provided files
  • Parse results data
  • Identify key metrics
  • Note data format and structure

Step 2: Data Validation

  • Check for missing values
  • Verify data consistency
  • Identify outliers
  • Validate metric calculations

Step 3: Baseline Comparison

  • Compare with baseline methods
  • Calculate improvement percentages
  • Determine statistical significance
  • Identify best performing methods

Step 4: Pattern Analysis

  • Identify trends in results
  • Find correlations
  • Detect anomalies
  • Understand training dynamics

Step 5: Ablation Study Analysis

  • Analyze component contributions
  • Identify critical components
  • Understand interactions
  • Recommend configurations

Step 6: Result Interpretation

  • Explain why results occurred
  • Connect to method design
  • Identify success factors
  • Acknowledge limitations

Step 7: Generate Analysis

  • Write analysis paragraphs
  • Create summary tables
  • Suggest visualizations
  • Provide recommendations

Step 8: Quality Check

  • Verify accuracy
  • Check for bias
  • Ensure completeness
  • Validate conclusions

Output

Primary Output

  • analysis-report.md - Comprehensive analysis
  • results-summary.md - Key findings
  • ablation-analysis.md - Component analysis

Secondary Output

  • recommendations.md - Suggested improvements
  • visualization-suggestions.md - Chart recommendations

Output Format

output/
├── analysis-report.md
├── results-summary.md
├── ablation-analysis.md
├── recommendations.md
└── visualization-suggestions.md

Constraints

Forbidden

  • ❌ Fabricating experimental data
  • ❌ Ignoring negative results
  • ❌ Making unsupported causal claims
  • ❌ Overgeneralizing from limited data
  • ❌ Cherry-picking favorable results

Required

  • ✅ Report all results honestly
  • ✅ Acknowledge limitations
  • ✅ Use appropriate statistical tests
  • ✅ Provide confidence intervals
  • ✅ Discuss potential confounds

Quality Gates

Data Quality

  • All data sources accounted for
  • Missing values identified
  • Outliers investigated
  • Data consistency verified

Analysis Quality

  • Appropriate statistical methods used
  • Significance levels reported
  • Effect sizes calculated
  • Confidence intervals provided

Interpretation Quality

  • Results explained clearly
  • Causal claims supported
  • Limitations acknowledged
  • Alternative explanations considered

Reporting Quality

  • Key findings highlighted
  • Tables well-formatted
  • Figures recommended
  • Recommendations actionable

Examples

Example 1: Time-Series Forecasting

Input:

results.csv:
Method,MSE,MAE,Inference_Time
PatchTST,0.385,0.412,15ms
iTransformer,0.378,0.405,18ms
Our_Method,0.376,0.403,16ms

Baseline: PatchTST (current SOTA)

Output:

Our method achieves 2.3% MSE improvement over PatchTST baseline
while maintaining comparable inference speed (16ms vs 15ms).
The improvement is consistent across both MSE and MAE metrics,
suggesting robust performance gains.

Example 2: Ablation Study

Input:

ablation.csv:
Configuration,MSE,Improvement
Full_Model,0.376,2.3%
w/o_Attention,0.389,0.5%
w/o_Dynamic,0.392,0.0%
w/o_Both,0.395,-0.5%

Output:

Ablation study reveals that attention mechanism contributes 1.8%
of the total 2.3% improvement, while dynamic allocation adds 0.5%.
Removing both components results in performance degradation,
indicating synergistic effects between components.

Notes

  • Always report both positive and negative results
  • Use appropriate statistical tests for significance
  • Consider practical significance, not just statistical
  • Recommend visualizations that aid understanding
  • Suggest additional experiments if needed

Experiment Analyzer - Part of GradAgentKit

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.