Use when an agent/runner with its OWN training code needs to make a Chronicle run durable and reproducible — phrases like "snapshot the environment", "upload checkpoints as it trains", "resume training from the last checkpoint", "continue the crashed run". It owns three things: capturing an environment snapshot at run start (library/hardware versions + your custom config state), uploading resumable checkpoints during training, and discovering + downloading the latest checkpoint to resume from. It is training-AGNOSTIC — the training loop is the caller's; this skill never writes it. It is the durable-state companion to chronicle-run-variation (which owns the run lifecycle + W&B linking): run-variation marks the run, this skill makes it survive a crash and continue. Distill afterward with chronicle-write-report.
EnglishUse when the user (or an agent flow) wants to take a committed or concluded Chronicle experiment — or a single variation — out of use while preserving the record: phrases like "retract this experiment", "this result turned out to be wrong", "flag this as invalid", "mark these findings as withdrawn", "the bug invalidated those runs". Retraction is a soft flag with a required reason: the row, lineage, and audit trail survive; the experiment's output assets are invalidated; live agent deployments are torn down; the GitHub repo is archived read-only. For deleting an open (uncommitted) draft use chronicle-delete-experiment instead — hard delete is refused once the experiment is committed.
EnglishIncludes Chronicle Checkpoint Resume and Chronicle Retract Experiment.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Chronicle Checkpoint Resume
Use when an agent/runner with its OWN training code needs to make a Chronicle run durable and reproducible — phrases like "snapshot the environment", "upload checkpoints as it trains", "resume training from the last checkpoint", "continue the crashed run". It owns three things: capturing an environment snapshot at run start (library/hardware versions + your custom config state), uploading resumable checkpoints during training, and discovering + downloading the latest checkpoint to resume from. It is training-AGNOSTIC — the training loop is the caller's; this skill never writes it. It is the durable-state companion to chronicle-run-variation (which owns the run lifecycle + W&B linking): run-variation marks the run, this skill makes it survive a crash and continue. Distill afterward with chronicle-write-report.
Chronicle Retract Experiment
Use when the user (or an agent flow) wants to take a committed or concluded Chronicle experiment — or a single variation — out of use while preserving the record: phrases like "retract this experiment", "this result turned out to be wrong", "flag this as invalid", "mark these findings as withdrawn", "the bug invalidated those runs". Retraction is a soft flag with a required reason: the row, lineage, and audit trail survive; the experiment's output assets are invalidated; live agent deployments are torn down; the GitHub repo is archived read-only. For deleting an open (uncommitted) draft use chronicle-delete-experiment instead — hard delete is refused once the experiment is committed.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Chronicle Checkpoint Resume skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.