Agent skill
oxygen-deliverability
Diagnose OXYGEN sender health from bounce, authentication, warmup and run evidence, then apply only the requested bounded remediation.
Filed under Outbound email.
From timscheuerai/gtm-architecture-template · 51 skill entries · 13 · pushed 2026-09-17
What it does when it runs
Diagnose OXYGEN sender health from bounce, authentication, warmup and run evidence, then apply only the requested bounded remediation.
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-deliverability" mkdir -p ~/.claude/skills/oxygen-deliverability cp -R "/tmp/gtm-architecture-template/.agents/skills/oxygen-deliverability/." ~/.claude/skills/oxygen-deliverability/
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-deliverability/SKILL.md, which is licensed MIT (repository). 187 words, 1 heading.
Investigate sender health
Read the runtime contract. Discover oxygen capabilities search "deliverability sender health" --json and hydrate the selected mailbox, deliverability, Sequence or egress command.
Start with a read-only fleet summary ordered by operational impact: paused/blocked senders, bounce evidence, authentication faults, warmup state, recent volume, provider errors and affected Sequences. Inspect the relevant mailbox and event/run timeline before assigning a cause.
Distinguish sender health from recipient verification. The kit's enrich_contact_details and prepare_sequence cover contact verification and freshness; they do not certify inbox placement or repair sender authentication.
Use a directional placement test only if it will change a decision. Preview the current scope, price and provider effects before an authorized test. A seed-test result is advisory; it cannot override an authoritative bounce pause or prove production placement.
Recommend the smallest supported action: repair auth/DNS, reduce caps, pause/rotate a sender or observe longer. Apply within the user's authorized remediation scope and current native gates. Never resume a bounce-paused sender simply because one outside test looks healthy.
Return evidence, time window, affected identities, proposed/applied actions and deep-links. Use email infrastructure for setup changes and Sequences for pacing/binding controls.
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.
- deliverability-incident-response by growthenginenowoslawski · 759
- deliverability-test-public by growthenginenowoslawski · 759
- email-deliverability-audit by growthenginenowoslawski · 759
- message-deliverability-optimization by louisblythe · 179
- outreach-deliverability by emelia-io · 17
- deliverability-incident-response by timyakubson · 7
- email-deliverability-audit by timyakubson · 7
- cold-email-deliverability by bcharleson · 6
Need help setting it up?
This page tells you what oxygen-deliverability 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.