Email sequence
Draft a 3 to 5 email sequence (onboarding, nurture or win-back) with one goal, the timing, and a single ask per email. Drafts only; never sends.
In Lobstack: Skills › Library › Add
What your agent will do.
People sign up, go quiet or reach the end of a trial, and someone wants a short run of emails that moves them to one next step.
- 01
Pin down three things, and ask if they are not given: who receives it, what event starts it, and the one action that counts as success.
- 02
Plan before writing: 3 to 5 emails, the day each goes out after the event, and what each one is for. Each email moves the reader one step.
- 03
Give every email one ask and one link. Two calls to action halve both.
- 04
Write subject lines that say what is inside. Keep bodies short — most under 150 words — with the ask near the top.
- 05
Say when someone leaves the sequence: they took the action, replied, or unsubscribed.
- 06
Use only facts about the product from the files. No made-up testimonials, discounts, deadlines or urgency.
- 07
Post a document: the plan as a table, then each email with its subject, preview line and body, including the unsubscribe line.
Never send, schedule or add anyone to a list. Loading the sequence into an email tool is a person's decision; ask first.
The whole SKILL.md: 32 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: email-sequence-draftdescription: "Draft a 3 to 5 email sequence (onboarding, nurture or win-back) with one goal, the timing, and a single ask per email. Drafts only; never sends."metadata: title: "Email sequence" category: marketing tags: [email, lifecycle]--- ## When to use this People sign up, go quiet or reach the end of a trial, and someone wants a shortrun of emails that moves them to one next step. ## How 1. Pin down three things, and ask if they are not given: who receives it, what event starts it, and the one action that counts as success.2. Plan before writing: 3 to 5 emails, the day each goes out after the event, and what each one is for. Each email moves the reader one step.3. Give every email one ask and one link. Two calls to action halve both.4. Write subject lines that say what is inside. Keep bodies short -- most under 150 words -- with the ask near the top.5. Say when someone leaves the sequence: they took the action, replied, or unsubscribed.6. Use only facts about the product from the files. No made-up testimonials, discounts, deadlines or urgency.7. Post a document: the plan as a table, then each email with its subject, preview line and body, including the unsubscribe line. Never send, schedule or add anyone to a list. Loading the sequence into an emailtool is a person's decision; ask first.
- Marketing
SEO page audit
Audit named pages for how well search engines and AI answers can find and understand them: titles, headings, meta, links, structured data and speed. Ranked fixes.
SKILL.md · App - Marketing
Tracked links per channel
Give every channel in a launch its own tracked link — source, medium, campaign — so the results can be read per channel instead of guessed.
SKILL.md · App - Marketing
Receipt for every post
After each approved post goes out, write one row to the Distribution table: channel, live link, tracked link, who approved it and when, so what was published is a record, not a claim.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App