SKILL.md
OXYGEN Diagnostics
Choose one question; do not dump every log surface.
| Question |
Read |
| Where did this value come from, or why is this cell stuck? |
[table-trace.md](table-trace.md) |
| Which rows/runs failed, and which are safe to retry? |
[error-sweep.md](error-sweep.md) |
| Why did credits increase, and how can spend be reduced? |
[optimize-credits.md](optimize-credits.md) |
Use oxygen capabilities search "diagnose <symptom>" --json to identify Tables, Records, Workflows, Sequences, Agents, or Observability, then hydrate the exact read command/schema.
Evidence order
- Inspect the user-visible object and its deep-link.
- Read the owning run, item/cell state, provenance, provider, attempt, credits, and structured error.
- Correlate through Observability only as far as needed.
- Distinguish pending/leased/retryable/blocked/approval-required from a product bug.
- Preview a bounded retry or repair and explain whether it can spend credits or repeat an external write.
- Execute a retry only with the applicable approval; never retry an ambiguous external send without reconciliation.
If the evidence shows a general product defect, file it through oxygen-feedback with the relevant run/table/workflow IDs and transcript. Do not compensate with hidden local state or an alternate provider.