Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dicklesworthstone/wandb-experiment-logger
Execute wandb experiment logger operations. Auto-activating skill for ML Training.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
In my training loop, training loss is computed every step, while validation metrics are computed every 500 steps. Calling wandb.log({'val_loss': val_loss}) without parameters causes the internal step counter to jump out of sync with training iterations. Someone suggested storing validation loss in a list and logging it at training completion. How should metrics evaluated at specific steps be explicitly aligned?
| Checked | Without skill | With skill |
|---|---|---|
| Passes step parameter explicitly to wandb.log | Missed | Passed |
The instructions your model reads when the skill loads.
This skill provides automated assistance for wandb experiment logger tasks within the ML Training domain.
This skill activates automatically when you:
Example: Basic Usage Request: "Help me with wandb experiment logger" Result: Provides step-by-step guidance and generates appropriate configurations
test cases passed, vs 21 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.