User Onboarding & Email Drip Automation

What it does

User Onboarding & Email Drip Automation is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/onboarding-emails. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

Designing automated email sequences that guide newly registered users to their 'Aha!' moment and convert them into paid subscribers.

Welcome series, activation milestones, feature nudges, and upgrade urgency. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is onboarding emails.

Why it exists

Default Cursor has no memory of how your team ships positioning, copy, and launch assets. Founders paste the same conventions into chat, then watch the model drift on the next turn. This skill exists so those conventions live on disk and load only when relevant.

It ships in the Marketing Kit. It is wired to the Email Sequence Specialist (email-marketer) and Direct Response Copywriter (copywriter) agents. It is wired to the /email-sequence: Customer Onboarding & Drip Email Sequence and /landing-page: High-Converting Landing Page Copy Architect commands. That graph is the point: the skill is the standard, the agent is the role, the command is the trigger.

When to use it

• Use User Onboarding & Email Drip Automation when the work is specifically about welcome series, activation milestones, feature nudges, and upgrade urgency.
• Load it before a long session that will touch this surface more than once. A one-line edit does not need the full playbook.
• Use it when you are writing something a buyer will see: landing copy, launch posts, SEO pages, or positioning docs.

When not to use it

• Do not treat the skill as a replacement for a slash command. Skills teach. Commands run a pipeline.
• Do not paste the whole SKILL.md into chat. If Cursor is not loading it, fix the description or invoke the matching command.
• Do not use it to generate spam or spray the same launch post across every channel.

Example workflow

1. Install the Marketing Kit so .cursor/skills/onboarding-emails lands in the repo.
2. Open a new Cursor agent chat pointed at the files this skill governs.
3. Ask the Email Sequence Specialist (email-marketer) to read the skill, or run /email-sequence: Customer Onboarding & Drip Email Sequence.
4. Review the first artifact against the practices below. If it violates one, stop and correct the file. Do not prompt 'just finish it'.
5. Commit the skill-guided files with the rest of the slice so the next session inherits the same standard.

Example usage

Example prompt: "Read .cursor/skills/onboarding-emails and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /email-sequence: Customer Onboarding & Drip Email Sequence. That command is written to load this skill.

Check the output against: Email 1 (Day 0): Immediate welcome, key download links, and one fast victory task

Example output

• The skill itself does not write a single output file. It changes what the agent is allowed to produce in positioning, copy, and launch assets.
• When you run /email-sequence: Customer Onboarding & Drip Email Sequence, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

• Email 1 (Day 0): Immediate welcome, key download links, and one fast victory task
• Email 2 (Day 1): Case study demonstrating 10x workflow speedup with real metrics
• Email 3 (Day 3): Deep dive into powerful advanced features (slash commands, rules)
• Email 4 (Day 5): Overcoming top objections and offering personalized setup support
• Email 5 (Day 7): Upgrade reminder with clear lifetime license value proposition

Common mistakes

• Ignoring "Email 1 (Day 0): Immediate welcome, key download links, and one fast victory task" and hoping a later prompt will clean it up.
• Copying the skill into .cursor/rules as always-on. That burns context and fights Cursor's load-on-match design.
• Running two overlapping skills that contradict each other in the same turn.
• Publishing generated copy without a human pass. The skill is a playbook, not a publisher.