oxygen-email-infra
Skill2 starsChanged 2 months agoMITView on GitHub
Set up and inspect OXYGEN sender profiles, domains, mailboxes, authentication, warmup and Sequence attachment using native previews.
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-deliverabilitySkill
- oxygen-diagnosticsSkill
- 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 13
Check OAuth and compatibility for every exact address.
- Distinctive: line 15
Read health, auto-pause, capacity and egress settings, then attach eligible senders to the intended Sequence.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Prepare native senders
Read the runtime contract. Discover oxygen capabilities search "email infrastructure setup" --json; hydrate the relevant sender, domain, mailbox, managed-inbox or integration command. This procedure does not require a named third-party mailbox vendor.
- Inspect existing sender profiles and exact mailbox addresses. Reuse the real person's identity; do not infer a name/photo from another customer or invent a sender.
- For provisioning or subscriptions, preview the exact resources, current quote, recurring terms and included services. Execute only the authorized scope.
- Inspect DNS and authentication: nameservers, MX, SPF, DKIM, DMARC and any configured tracking. Preserve unrelated domain services.
- Check OAuth and compatibility for every exact address. One token or a domain-level success does not prove every mailbox is ready. Follow the returned remedy and retry timing.
- Inspect native warmup truth, enrollment state, ramp and cost. Warmup included in an approved order needs no second permission request; unrelated enrollment needs its own scope.
- Read health, auto-pause, capacity and egress settings, then attach eligible senders to the intended Sequence.
An active subscription, configured DNS and actual working authentication are distinct states. Surface which one failed. Use live quotes instead of stored prices or a universal sends-per-day rule.
For a requested disconnection or cancellation, preview effects on sending, credentials, history, renewals and affected Sequences. Removing a connection, ending warmup and canceling managed provisioning are different operations. Honor the native confirmation mechanism and read back state; do not delete external mailbox accounts through an inferred cleanup.
Return sender/mailbox links, authentication and warmup states, actual charges if incurred, and any unresolved readiness. Infrastructure setup and warmup do not authorize outreach.
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.

