One-click install
npx skills add https://github.com/dongzhuoyao/deepresearch --skill wandb-csv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wandb-csv
Source: https://github.com/dongzhuoyao/deepresearch/tree/main/.codex/skills/wandb-csv
Command: npx skills add https://github.com/dongzhuoyao/deepresearch --skill wandb-csv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of W&B experiment results being tied to transient UI state and console logs that may be lost or hard to compare across runs, by maintaining a durable workspace-local CSV ledger for all experiment outcomes.

Core Features & Use Cases

  • Consistent Schema Enforcement: Uses a predefined set of required columns including experiment version tracking to prevent stale or inconsistent data entry.
  • Multi-Scenario Support: Handles logging for full runs, dryruns, and multiple hyperparameter variants, with clear rules to avoid confusing dryrun metrics with full-run results.
  • Cross-Run Comparison: Enables easy side-by-side comparison of experiment variants without relying on the W&B UI, by reading directly from the local CSV ledger. Use Case: When running a grid of 10 hyperparameter variants for a computer vision training experiment, use this Skill to log each variant's FID and BPD metrics to the CSV ledger for instant comparison and reporting.

Quick Start

Use the wandb-csv skill to log the latest training run's metrics to the project's experiment results CSV ledger.

Frequently Asked Questions about wandb-csv

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

FAQPage Schema
How do I save W&B experiment results to a CSV file for comparison?

You can save W&B experiment results to a CSV ledger to persist metrics beyond transient UI states. This durable local file enables side-by-side hyperparameter comparison across variants without relying on the W&B UI.

What is the best way to track ML experiment metrics outside of the W&B UI?

Tracking ML experiment metrics outside the W&B UI is best achieved by logging run outcomes directly to a local CSV ledger. This provides a persistent, comparable record of training metrics across multiple hyperparameter variants and dryruns.

How do I avoid confusing dryrun metrics with full-run results in experiment tracking?

You avoid confusing dryrun metrics with full-run results by using a schema-consistent CSV ledger with clear multi-scenario logging rules. This enforces experiment version tracking to separate dryrun outcomes from full-run data.

Can I compare hyperparameter variants across W&B runs without the web interface?

Yes, you can compare hyperparameter variants across W&B runs without the web interface by reading directly from a local CSV ledger. This approach supports instant side-by-side comparison for grids of training variants.

How do I prevent stale or inconsistent data entry when logging ML experiments?

You prevent stale or inconsistent data entry when logging ML experiments by enforcing a predefined schema of required columns in your ledger. This ensures experiment version tracking is maintained and stale data is filtered correctly.