agentleFS
Sign inStart free
fw-aifw-ai/cookbook/skills/debug/SKILL.md

debug

Skill241 starsChanged 32 days agoApache-2.0View on GitHub

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.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-discord, add-slack and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • +10 more from microsoft

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default to concise: evidence, likely cause, next step.

    line 23
  2. Distinctive:

    Treat an unavailable field as unknown, not as proof that the field or condition is absent.

    line 24
  3. Very specific:

    Check firectl skill-journey record --help once.

    line 61
  4. Distinctive:

    Never send raw errors, customer prose, credentials, datasets, or paths as journey telemetry.

    line 65
  5. Distinctive:

    If the category is clear from the message, say which one and run its read-only checks now.

    line 71
  6. Distinctive:

    Follow the ordered read-only checks for that category.

    line 74
  7. Distinctive:

    Use the detailed carrier references listed below.

    line 76
  8. Distinctive:

    After three failed hypotheses on the same issue:

    line 80
  9. Distinctive:

    Use AskQuestion one question at a time, then stop.

    line 108
  10. Distinctive:

    Use plain customer language.

    line 110
  11. Distinctive:

    Do not retry or create resources from debug.

    line 112

“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

SignalRoute
New training or approved retryconfigure
Unclear method, data, or starting exampleresearch
Failure, stall, bad quality, resume, or serving issuestay 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

  1. Read references/triage-paths.md.
  2. 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.
  3. Follow the ordered read-only checks for that category.
  4. Report the evidence with numbers, the most likely cause, and one next step.
  5. Use the detailed carrier references listed below.

Three-strike rule

After three failed hypotheses on the same issue:

  1. Stop guessing.
  2. 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.
  3. Redact credentials and customer data.
  4. State what the evidence supports and what remains unknown.

Handoff

  1. Route to configure only when the user wants a new or retry run.
  2. Route to research when the starting example or method is wrong.
  3. On resolution without new spend, record debug_resolved and stop.

Progressive references

NeedReference
Triage categoriesreferences/triage-paths.md
Error catalog../fireworks-training/references/error-reference.md
TITO parsing, local traces, and transport errorsreferences/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

  1. Use AskQuestion one question at a time, then stop. Skip questions the message already answers.
  2. Use plain customer language.
  3. The category question, when asked, uses its five registered options.
  4. Do not retry or create resources from debug.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free