Agent skill
oxygen-diagnostics
Trace OXYGEN cells and runs, explain failures or credit spend, and plan reconciled retries from native provenance.
From timscheuerai/gtm-architecture-template · 51 skill entries · 13 · pushed 2026-09-17
What it does when it runs
Trace OXYGEN cells and runs, explain failures or credit spend, and plan reconciled retries from native provenance.
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/timscheuerai/gtm-architecture-template.git /tmp/gtm-architecture-template git -C /tmp/gtm-architecture-template sparse-checkout set ".agents/skills/oxygen-diagnostics" mkdir -p ~/.claude/skills/oxygen-diagnostics cp -R "/tmp/gtm-architecture-template/.agents/skills/oxygen-diagnostics/." ~/.claude/skills/oxygen-diagnostics/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from timscheuerai/gtm-architecture-template/blob/2c312c9398064ad3730c786647293458cb89632c/.agents/skills/oxygen-diagnostics/SKILL.md, which is licensed MIT (repository). 253 words, 1 heading.
Explain one operational failure
Read the runtime contract. Identify the visible Table/row/cell, Workflow, Sequence or message and the user's symptom. Discover oxygen capabilities search "diagnose failed table run" --json using the actual symptom, then hydrate the narrow read command.
| Question | Evidence to collect |
|---|---|
| Wrong or missing cell | Input values, dependencies, column definition/version, cell/run envelope, sources |
| Failed or stuck work | Status, attempts, lease/retry time, structured error, approval/integration state |
| Unexpected credits | Row count, provider/model operation, attempts, caps, estimated versus charged receipts |
| Ambiguous external effect | Native action/message ID, provider ID, delivery state and reconciliation result |
Distinguish pending, leased, deferred, approval-required, retryable and failed work. Missing output may mean the step never ran; an empty view may be scoped or stale. Read envelopes and timestamps instead of assuming a raw string is the final result.
Use run and item provenance to connect the symptom to its owner. Avoid dumping every workspace log or joining unrelated runs solely by time. A cost estimate, reservation and settled charge are not interchangeable.
Before a retry, identify exact items, possible duplicate effects and incremental cost. Reconcile an ambiguous send or write first. Preview the bounded repair and execute only within the authorized scope; do not switch providers or build hidden local recovery state.
Return the most likely cause, supporting IDs/links, remaining uncertainty and verified repair state. If a product defect remains, prepare a reproducible report locally; sending feedback or transcripts requires the user's request.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- cpa-diagnostics by irinabuht12-oss · 4,293
- cargo-diagnostics by getcargohq · 19
Need help setting it up?
This page tells you what oxygen-diagnostics does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.