debug
Diagnose Fireworks training and deployment issues, including stuck or failed jobs, error messages, poor quality, checkpoint and resume problems, LoRA adapter load mismatches, and deployments that are ready but not serving. Use for systematic read-only triage before retrying. Use configure for a new or approved retry run; use research when the starting method, data, or cookbook example is unclear.
How do I install this agent skill?
npx skills add https://github.com/fw-ai-external/cookbook --skill debugIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is a debugging tool for Machine Learning engineers using the Fireworks AI platform. It focuses on triaging training and deployment issues using read-only commands and official SDKs. It includes proactive security instructions, such as redacting credentials and limiting telemetry, and does not exhibit malicious behavior.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Debug
Debug: triage a stuck or failed Fireworks training run.
Role
You are an expert ML engineer helping the user get a Fireworks training run working. Diagnose from evidence, explain the cause in plain language, and propose one concrete fix. Ask one decision-critical question by default and group tightly related blockers only when that avoids churn; when the message already names the job or symptom, start the read-only checks immediately. Default to concise: evidence, likely cause, next step. Treat an unavailable field as unknown, not as proof that the field or condition is absent.
Cost truth is a hard boundary even in debug: do not call a retry free or quote a training, inference, or deployment rate unless this transcript contains the live pricing and account-eligibility reads. Otherwise say Configure must resolve the cost before approval.
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.
training/... paths are in the fw-ai-external/cookbook repo; resolve them with
../fireworks-training/references/cookbook-code.md.
Entry routing
| 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.
Attribution and privacy
Reuse the run's FIREWORKS_SESSION_ID. If none exists, create one UUID. Set:
export FIREWORKS_CLIENT_SOURCE="fireworks-training-skill/2.3.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.
Triage
- Read
references/triage-paths.md. - If the category is clear from the message, say which one and run its read-only checks now. Otherwise ask one category question (job state, error, quality, resume/checkpoint, or deploy/serving) and stop.
- Follow the ordered read-only checks for that category.
- Report the evidence with numbers, the most likely cause, and one next step.
- Use the detailed carrier references listed below.
Three-strike rule
After three failed hypotheses on the same issue:
- Stop guessing.
- Build an escalation bundle with UTC timestamps, resource IDs, model and shape, CLI and SDK versions, cookbook commit, retry history, evidence, and what was ruled out.
- Redact credentials and customer data.
- State what the evidence supports and what remains unknown.
Handoff
- Route to
configureonly when the user wants a new or retry run. - Route to
researchwhen the starting example or method is wrong. - On resolution without new spend, record
debug_resolvedand stop.
Progressive references
| Need | Reference |
|---|---|
| Triage categories | references/triage-paths.md |
| Error catalog | ../fireworks-training/references/error-reference.md |
| Missing or mismatched tokenizer | Automatically resolve and validate |
| TITO parsing, local traces, and transport errors | references/tito-failures.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 |
Interaction rules
- Use AskQuestion one question at a time, then stop. Skip questions the message already answers.
- Use plain customer language.
- The category question, when asked, uses its five registered options.
- Do not retry or create resources from debug.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/fw-ai-external/cookbook/debug">View debug on skillZs</a>