oxygen-deliverability
Skill2 starsChanged 2 months agoMITView on GitHub
Diagnose OXYGEN sender health from bounce, authentication, warmup and run evidence, then apply only the requested bounded remediation.
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- context/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- context/CLAUDE.mdCLAUDE.md
- brand-reviewSkill
- brand-systemSkill
- capture-contextSkill
- content-strategySkill
- crm-presync-checkSkill
- flowchartSkill
- graphics-designerSkill
- gtm-startSkill
- launch-videoSkill
- lead-magnet-creatorSkill
- lead-sourcingSkill
- linkedin-copywriterSkill
- long-formSkill
- manim-videoSkill
- newsletter-writerSkill
- outbound-copywriterSkill
- oxygen-dedupeSkill
- oxygen-diagnosticsSkill
- oxygen-email-infraSkill
- oxygen-gtmSkill
- oxygen-knowledgeSkill
- oxygen-linkedin-marketingSkill
- oxygen-quickstartSkill
- oxygen-recipesSkill
- oxygen-sequencer-enrollSkill
- oxygen-sequencerSkill
- oxygen-table-tidySkill
- oxygen-uniboxSkill
- oxygen-workflow-authoringSkill
- personalize-ai-columnSkill
- qmdSkill
- repurpose-contentSkill
- researcherSkill
- setup-workspaceSkill
- shorts-audioSkill
- shorts-cutSkill
- shorts-editSkill
- shorts-motionSkill
- shorts-qaSkill
- signals-sweepSkill
- spin-tagsSkill
- split-test-designerSkill
- video-useSkill
- voice-calibrationSkill
- week-postsSkill
- x-copywriterSkill
- youtube-descriptionSkill
- youtube-publisherSkill
- youtube-scriptSkill
- youtube-thumbnailSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Very specific: line 8
Read the runtime contract.
- Distinctive: line 10
Start with a read-only fleet summary ordered by operational impact: paused/blocked senders, bounce evidence, authentication faults, warmup …
- Distinctive: line 14
Use a directional placement test only if it will change a decision.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
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
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.

