oxygen-sequencer
Operate OXYGEN Sequences for net-new LinkedIn outreach, including one recipient and one step, and for multistep email, LinkedIn, WhatsApp, call, or CRM-task programs. Covers sender readiness, versions, cadence, enrollment, suppression, reply-stop, preview, bounded dispatch, and recovery. Existing-thread replies and direct email use Messages.
How do I install this agent skill?
npx skills add https://oxygen-agent.com --skill oxygen-sequencerIs this agent skill safe to install?
No partner audit is available yet. Read the source before installing.
What does this agent skill do?
OXYGEN Sequencer
Sequences own outreach initiation and cadence, preserving sender binding, pacing, suppression, reply-stop, retries, provider IDs, and run provenance.
Boundary
- New LinkedIn conversation, even one person/one message: Sequence. The one-step gateway is
sequences send/oxygen_sequences_send. - Multi-recipient or multistep email, LinkedIn, WhatsApp, call, or CRM-task motion: Sequence.
- Reply in an existing email/LinkedIn/WhatsApp thread: Messages/Unibox.
- New direct email with no cadence: Messages via
email send. - Deterministic automation around a campaign: Workflow outside, Sequence inside. A Workflow may enroll a draft, active, or paused Sequence; draft/paused recipients stay pending. It never sends raw provider messages.
Confirm this route with oxygen capabilities search "<outreach goal>" --json, then hydrate the selected command with oxygen commands get or MCP schema discovery.
Objects to inspect
- Sender pool: connected accounts/mailboxes, health, warmup, channel limits, and stable person-to-sender binding. Prefer sender profiles — one person's accounts and inboxes under one name and photo — as the selection unit, so a lead hears from the same human on every channel. A profile also supplies the name and photo
managed-inboxes --senderstamps PERMANENTLY on ordered inboxes: never guess a missing name half or ship a non-durable photo (oxygen-email-infra). - Definition/version: ordered steps, delays, variants, conditions, tracking, send windows, and channel fallbacks.
- Enrollment: recipient identity, mapped variables, exclusions, suppressions, prior-contact rules, and tags.
- Dispatch policy: daily caps, ramp, sender rotation/failover, ESP matching, bounce policy, and reply-stop.
- Run state: previews, sends, skips, failures, replies, costs, and reconciliation evidence.
Common gateways: sequences create|enroll|start|list|events|reconcile|hubspot-list-import.
HubSpot saved-list enrollment
For recurring HubSpot segment enrollment use sequences hubspot-list-import lists|configure (MCP oxygen_sequences_hubspot_lists / ..._hubspot_list_import). Preview first; live needs approval plus its fingerprint. The Workflow applies complete DNC before enrollment and keeps draft/paused recipients pending. Never recreate paging, storage, DNC, or enrollment locally — use the HubSpot runbook.
Performance attribution
Campaign-attributed native email facts:
sequences analytics --range 30d --json: every campaign plusanalytics.emailAttribution.byMailbox,.byDomain,.unattributed, workspace-wide.sequences variants <sequence> --json: the same facts for one campaign, with its A/B results.sequences events <sequence> --json: the per-lead ledger; email events carrymailboxEmail/sendingDomainwhen the durable event preserved them.
Mailbox/domain rows report sent, replied, positive-reply, bounced, and failed counts, reply/bounce rates, reply-type counts, and campaign counts (domain rows add mailbox count). A fact with a known campaign but no preserved sending identity stays unattributed — never infer a mailbox by joining campaign totals to the configured pool.
Narrower than the unified Message ledger on purpose: messages stats covers Unibox conversations, mailboxes get/domains get|list cover sending infrastructure. A send with no native Sequence id — direct, or provider-owned like Salesforge — becomes campaign/mailbox attribution only once its telemetry is normalized into Oxygen's native action/message ledgers, never merely because an integration is connected.
Safe run loop
- Inspect channel and sender readiness; do not treat “connected” as “safe to send.”
- Create or revise the hosted Sequence definition.
- Preview enrollment and dispatch with the exact recipient scope, sender pool, exclusions, and current live credit estimate.
- Show both ceilings — the Sequence's lifetime budget and the current live-run cap; neither substitutes for the other.
- Obtain explicit approval for the external write and bounded spend.
- Enroll, then start. Keep the returned run and Sequence deep-links.
- Monitor events, failures, bounce/reply stops, and sender health. Reconcile an ambiguous provider outcome before any retry.
Never bypass Sequences with raw LinkedIn chat/provider actions, local loops, or a generic integration action. Never resend an ambiguous LinkedIn action until reconciliation proves the provider did not accept it.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/oxygen-agent.com/oxygen-sequencer">View oxygen-sequencer on skillZs</a>