executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
checkpointing-and-trackingSave and resume Accelerate training state, register checkpoint hooks and custom state, log safely across processes, use experiment trackers, profile runs, and clean up memory.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task involves Accelerate checkpoint save/load, model export, tracker initialization/logging, distributed-safe logging, profiling, state/RNG handling, or memory cleanup around those workflows.
skip_first_batches, use ../training-loop-integration/.../distributed-training-backends/.Accelerator.save_state() and Accelerator.load_state(); see references/checkpointing.md.ProjectConfiguration; see references/checkpointing.md.references/checkpointing.md.Accelerator(log_with=...), init_trackers(), log(), get_tracker(), and end_training(); see references/tracking-and-logging.md.accelerate.logging.get_logger() for multiprocess-safe logs and ordered rank logs; see references/tracking-and-logging.md.ProfileKwargs and accelerator.profile(); see references/tracking-and-logging.md.references/troubleshooting.md before changing training code.python scripts/checkpoint_tracker_smoke.py --help for usage.python scripts/checkpoint_tracker_smoke.py to verify a CPU-only tiny save/load/custom-tracker/logging smoke test without any external tracker service.save_state()/load_state() are for resuming the same training script shape, not arbitrary model conversion between unrelated scripts.state_dict() and load_state_dict().accelerator.unwrap_model(), accelerator.get_state_dict(), accelerator.save(), or accelerator.save_model() rather than treating a training-state checkpoint as a deployment artifact.