research-results-analysis

Analyze experiment outputs and convert metrics into traceable, conservative research claims.

2|Updated May 22, 2026
One-click install
npx skills add https://github.com/CDUTAKL/research-workflow-kit --skill research-results-analysis-cdutakl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-results-analysis
Source: https://github.com/CDUTAKL/research-workflow-kit/tree/main/skills/research-results-analysis
Command: npx skills add https://github.com/CDUTAKL/research-workflow-kit --skill research-results-analysis-cdutakl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Raw experiment outputs such as logs, CSVs, JSON metrics, and ablation tables are hard to turn into defensible paper claims without auditing data quality, baselines, splits, and statistical support. This Skill structures that analysis so results are traceable to artifacts before they become prose. ## Core Features & Use Cases - Automated Result Scanning: The bundled scan_results.py script recursively parses JSON, CSV, TSV, TXT, and LOG files to extract common metrics (accuracy, F1, precision, recall, loss, AUC, RMSE, MAE, R2) with anomaly and scale warnings. - Registry Candidate Generation: result_scan_to_registry.py converts scan output into review-only EXP-AUTO-* rows in an experiment registry, keeping unreviewed results separate from thesis evidence. - Claim Auditing Workflow: Classifies claims as supported, weak, unsupported, or missing, with EDA gates, statistical test selection guidance, and experiment integrity checks (leakage, metric mismatch, dead metric code). - Use Case: After a training run produces scattered result folders, scan the directory, review candidate metrics, compare against baselines, and produce a claim table plus figure handoff for the paper. ## Quick Start Use the research-results-analysis skill to scan my experiment results folder and summarize which paper claims the metrics actually support.

Frequently Asked Questions about research-results-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan experiment result files for metrics automatically?

Run the bundled scan_results.py script with a root directory and output folder. It recursively parses JSON, CSV, TSV, TXT, and LOG files, extracts metrics like accuracy, F1, loss, and AUC, and writes a summary Markdown file plus a traceable CSV table.

How to turn experiment results into paper claims?

Inventory artifacts first, run an exploratory data quality gate, normalize metrics and splits, then classify claims as supported, weak, unsupported, or missing. Only promote results to claims after integrity checks for leakage, metric mismatch, and baseline comparability pass.

What file formats does the result scanner support?

The scanner supports .json, .csv, .tsv, .txt, and .log files. It recognizes common metric names including accuracy, f1, macro_f1, precision, recall, loss, auc, rmse, mae, and r2, and flags values outside valid ranges.

When should I report statistical significance for experiment results?

Only when the design supports it: multiple seeds allow mean and variability summaries, paired samples allow paired tests, and independent groups allow t-tests or non-parametric alternatives. Single-run results should be reported descriptively without significance language.

What are the limitations of automated metric extraction from logs?

Scanner output is an initial inventory, not final evidence. Metric scale, dataset split, seed, and evaluation protocol must be reviewed manually before citing values, and candidate EXP-AUTO registry rows should never be cited directly in a paper.