experiment-tracking

Standardize VLA experiment logging with configurations, results, and insights.

1|3|Updated May 22, 2025
One-click install
npx skills add https://github.com/minuum/vla --skill experiment-tracking-minuum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-tracking
Source: https://github.com/minuum/vla/tree/main/.agent/skills/experiment-tracking
Command: npx skills add https://github.com/minuum/vla --skill experiment-tracking-minuum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic logging of Vision-Language-Action experiments to enable reproducibility and data-driven insights.

Core Features & Use Cases

  • Standardized experiment logs: capture configuration, results, and insights in a single, queryable history.
  • Change-aware analysis: link experiments to artifacts and IDs (e.g., EXP-17) for traceability.
  • Post-hoc reporting: generate tables and summaries for papers, reports, and API-ready results.

Quick Start

Log a completed experiment by updating docs/EXPERIMENT_HISTORY_AND_INSIGHTS.md with a new row detailing the experiment ID, model, epochs, and key metrics.

Frequently Asked Questions about experiment-tracking

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

FAQPage Schema
How do I track VLA experiment configurations for reproducibility?

To track VLA experiment configurations for reproducibility, log a completed experiment by updating docs/EXPERIMENT_HISTORY_AND_INSIGHTS.md with a new row detailing the experiment ID, model, epochs, and key metrics.

What is the best way to log Vision-Language-Action training results systematically?

Logging Vision-Language-Action training results systematically requires a consistent log file at docs/EXPERIMENT_HISTORY_AND_INSIGHTS.md, using a fixed table format to capture experiment IDs, configurations, and key metrics.

Can I generate post-hoc analysis tables for VLA evaluation experiments?

You can generate post-hoc analysis tables for VLA evaluation experiments by applying this standardized logging approach, which captures results and insights in a queryable history to support data-driven decision making.

Do I need a specific file format to maintain experiment history and insights?

You need a consistent markdown log file at docs/EXPERIMENT_HISTORY_AND_INSIGHTS.md to maintain experiment history, requiring a fixed table format for results and a clear claim-evidence structure for insights.

How does change-aware analysis link artifacts to specific experiment IDs?

Change-aware analysis links artifacts to specific experiment IDs, such as EXP-17, by standardizing the logging of training, evaluation, and post-hoc analysis across multiple experiments to ensure traceability and reproducibility.