gen-report-concise

Generate concise experiment reports from training run artifacts and logs.

7|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/gyy0592/claude-config --skill gen-report-concise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-report-concise
Source: https://github.com/gyy0592/claude-config/tree/main/skills/gen-report
Command: npx skills add https://github.com/gyy0592/claude-config --skill gen-report-concise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creation of compact, reproducible experiment reports by extracting key metrics, configuration, and provenance from training run artifacts so engineers and researchers can quickly understand results and trade-offs without manual log parsing.

Core Features & Use Cases

  • Automated data collection: Parallel read of training logs, snapshot model configs, training toml files, CSV metrics, and artifacts to gather numeric and contextual data.
  • Provenance-first metrics: Every reported metric includes mathematical definition, physical meaning, and exact data source with file path, line number, and step identifier.
  • Structured concise output: Fills a four-section report template that includes takeaway, motivation, reproducibility, and results with a final trade-off table.
  • Use case: Summarize flame_moonshot training runs for quick handoff, postmortem, or performance comparison across experiments.

Quick Start

Generate a concise experiment report for experiment kda_680M in /nfs/ridgerzhu/flame_moonshot/exp/ by invoking the gen-report-concise skill and include logs, configs, and metrics for provenance.

Frequently Asked Questions about gen-report-concise

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

FAQPage Schema
How do I generate a concise experiment report from training logs and model configs?

Provenance-first experiment reporting tracks the exact data source by attaching file paths, line numbers, and step identifiers to every metric. This ensures reproducible analysis by mathematically defining metrics and linking them directly to training logs and artifacts.

How do I extract metrics and provenance from flame_moonshot training run artifacts?

The structured experiment report output includes four sections: takeaway, motivation, reproducibility, and results. It concludes with a final trade-off table to summarize performance comparisons across different training runs for quick handoff.

Can I use automated report generation for training toml and CSV metrics without manual parsing?

Use automated experiment reporting when you need to summarize training runs for quick handoff, postmortem, or performance comparison. It is needed when manual extraction of metrics, configs, and provenance from training logs becomes too time-consuming.

What is the best way to summarize model training runs for postmortem and performance comparison?

Yes, the experiment reporting skill handles CSV metrics and training toml files by reading them in parallel alongside snapshot model configs. This compatibility allows it to gather both numeric metric data and contextual configuration for the final report.