Skip to content
Back to skills

Ls Email Sequence Builder

ASecurity

Guide email sequence planning and writing. Use for lifecycle, onboarding,

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgitapi

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add CruxExperts/LocalSetup --skill ls-email-sequence-builder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ls Email Sequence Builder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ls Email Sequence Builder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cruxexperts-ls-email-sequence-builder/badge)](https://www.skillsdirectory.com/skills/cruxexperts-ls-email-sequence-builder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ls-email-sequence-builder
description: Guide email sequence planning and writing. Use for lifecycle, onboarding,
  nurture, launch, winback, and sales email sequences.
metadata:
  version: '1.0'
extensions:
  external_skill:
    source_kind: native-reference
    source_url: https://github.com/coreyhaines31/marketingskills
    source_path: <repository inventory>
    source_commit: 30dbd7f793b86f0ec2f007757b333afac93c24db
    source_ref: main
    source_sha256: 036b2241f8c6f28265fa744299392bc44df19b86e14ddd96f6ca87738a6ec823
    license: MIT
    import_date: '2026-07-03'
    vetting_status: provenance-recorded-no-bundled-tooling-executed
---

# Email Sequences

Use this skill when working on email sequences tasks.

## Workflow

- Define audience, trigger, promise, cadence, exit conditions, and measurable outcome before drafting.
- Keep each email focused on one job with clear subject, preview text, body, CTA, and suppression logic.
- Check consent, unsubscribe, segmentation, deliverability, and brand voice before launch.

## Boundaries

- Inspect the target repository before making changes.
- Prefer existing project patterns, declared package managers, and documented validation commands.
- Do not expose secrets, credentials, private user data, or production account identifiers in source, examples, or logs.
- When external APIs or current vendor behavior matter, verify against official docs before implementation.

## Provenance

- Source: `https://github.com/coreyhaines31/marketingskills`
- Ref: `main` at `30dbd7f793b86f0ec2f007757b333afac93c24db`
- Source path: `<repository inventory>`
- License classification: `MIT`
- Source SHA-256: `036b2241f8c6f28265fa744299392bc44df19b86e14ddd96f6ca87738a6ec823`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.