Terminal
Terminal/Skill
Read-only triage of failed or stuck Fireworks training jobs and deployments that are not serving, before any retry.
By Fireworks AI
Works with
npx skills add fw-ai/cookbook --skill debugDebug: triage a stuck or failed Fireworks training run.
Debug is read-only by default. Do not create jobs, upload data, or spend without
an explicit handoff to configure and a new approved plan.
| Signal | Route |
|---|---|
| New training or approved retry | configure |
| Unclear method, data, or starting example | research |
| Failure, stall, bad quality, resume, or serving issue | stay in debug |
Research owns the welcome-entry question and its privacy notice. Route a
vague first message there instead of asking a second welcome question.
Reuse the run's FIREWORKS_SESSION_ID. If none exists, create one UUID. Set:
export FIREWORKS_CLIENT_SOURCE="fireworks-training-skill/2.2.0"
Record entry_skill: debug in the private run manifest. Before the first
structured question, show
../fireworks-training/references/telemetry-notice.md.
Check firectl skill-journey record --help once. When available, record only
registered IDs through ../fireworks-training/references/telemetry.md. If it is
unavailable or the user opts out, keep local run state and continue.
Never send raw errors, customer prose, credentials, datasets, or paths as journey telemetry.
references/triage-paths.md.After three failed hypotheses on the same issue:
configure only when the user wants a new or retry run.research when the starting example or method is wrong.debug_resolved and stop.| Need | Reference |
|---|---|
| Triage categories | references/triage-paths.md |
| Error catalog | ../fireworks-training/references/error-reference.md |
| Resume and idempotency | ../fireworks-training/references/run-state-and-reporting.md |
| Deployment proof | ../fireworks-training/references/deploy-and-troubleshoot.md |
| Journey telemetry | ../fireworks-training/references/telemetry.md |