EmailsInformation

Package notes

Draft the flow.
Review the handoff.

Emails is an instruction-based lifecycle writing Skill for marketing, growth and customer-success teams. It creates complete welcome, onboarding, nurture or re-engagement sequences from supplied customer and product facts, with one useful action in each email.

VersionOriginal Skill 2.1.2
LicenseMIT, Corey Haines, 2025
RuntimeAssistant supporting Agent Skills
DeliveryText drafts and implementation rules

Start with an approved brief

Load the package in an assistant supporting Agent Skills. Paste or attach product facts and customer-stage context that the host can read, then name the sequence and desired next action. Your existing AI host supplies the model; its normal access and usage costs still apply even though drafting needs no separate API key.

Use authorized, appropriately redacted material. The Skill is suitable for reviewable lifecycle copy; it is unsuitable for generating consent, inventing customer proof, or automatically sending messages.

What to provide

Product benefits, audience and stage, entry event, desired action, real destinations, permitted offers or proof, available behavior data, sender voice, and other emails already running.

An existing product-marketing context file is used when present. Missing proof and links should stay marked rather than being fabricated.

What you receive

A sequence overview with triggers, timing and exits; full subject, preview and body copy for each email; one primary CTA and destination; segment or skip rules; a metrics plan.

Use the draft for review before implementing it in your chosen platform.

Included in the package

Dependencies and boundaries

Supplied-material drafting needs the user's existing AI host. It does not need an email-provider account or separate API key. The package does not include a model service, document reader, export program, or automatic sending application.

Provider setup, permissions, subscriber data, suppression handling, link verification, automation deployment, and analytics require separate tools and authorization. Cold outreach and full in-app onboarding are separate scopes.

What has been demonstrated

On October 11, 2026, one Codex instruction-guided task produced five complete paid-member welcome drafts for fictional Papertrail Studio. The saved output included timing, exit and skip rules, full per-email fields, unresolved-link markers and a metrics plan. The authoring assistant reviewed copy and structure; mechanical field, length and schedule checks were recorded separately.

Installed-client activation, an independent evaluator, the seven-eval suite, provider branch execution, inbox previews, deliverability and activation lift were not tested. No provider was connected and no message was sent. Benchmark and Showcase provide the detailed scope and artifact evidence.

Provenance

Organized from coreyhaines31/marketingskills, skills/emails, fixed commit b9ba399dd88b082b926e261e8ccfb843d20aa066. Original Skill, references, eval definitions, shared reference, and license were retained. Copyright (c) 2025 Corey Haines; upstream endorsement is not implied.