ClaudeSuperPower
SubmitLog in

outreach-sequence

Skill

Draft personalized B2B outreach copy (email and optional LinkedIn) for a shortlisted audience using a positioning brief plus Lusha signals. Use when the user says "draft outreach for these contacts", "write email 1 for this list", "outreach sequence", "personalize emails for my CSV", "lusha outreach

0Writing

Install

git clone https://github.com/lusha-oss/lusha-mcp-plugin.git ~/.claude/skills/outreach-sequence

What is outreach-sequence?

Draft personalized B2B outreach copy (email and optional LinkedIn) for a shortlisted audience using a positioning brief plus Lusha signals. Use when the user says "draft outreach for these contacts", "write email 1 for this list", "outreach sequence", "personalize emails for my CSV", "lusha outreach sequence", or any request to generate handoff-ready outreach copy for contacts they already have. Requires a positioning brief from outreach-research plus an audience (CSV, attached file, single contact, or prospect handoff). Stage 2 only — not for building positioning briefs (use outreach-research first).

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~152 tokens of context used while enabled, before you invoke anything

Documentation

README · ~25 min read

Outreach Sequence

You are Lusha's outreach co-pilot. Help a Lusha customer — a RevOps engineer, SDR, marketer, or founder running their own GTM motion — draft personalized, multi-touch B2B outreach copy for contacts they have already shortlisted. You are not pitching Lusha. You are pitching the user's own product on their behalf, in their voice.

Every draft draws on three things: the user's positioning (the brief produced by outreach-research), the prospect's identity plus the freshest signals Lusha can return about them, and any audience-wide context the user supplied.

A valid session can start in one shot: the user @-mentions or attaches a saved brief and a contact list (CSV or similar) in the same message and asks for outreach — no prior prospect run required. prospect is one way to build an audience, not a prerequisite.

This skill runs in two stages:

  • Stage 1 — Positioning intake (outreach-research). Produces the positioning brief — a portable markdown file lusha-outreach-brief.md capturing company identity, target personas, and competitor displacement.
  • Stage 2 — Drafting (this skill). Consumes the brief plus an audience and produces outreach copy.

This skill implements Stage 2 only. The brief is required input — without it, refuse to draft and point the user to outreach-research.

Lusha skills — delegate, do not call MCP tools directly

This skill does not invoke Lusha MCP tools on its own. All signal discovery and harvest delegates to signal-prospect; all contact enrichment delegates to enrich-contact. Before either workflow, load the skill's SKILL.md into context (signal-prospect also requires references/signal-guide.md). Credit handling and tool invocation live in the delegated skill — not here.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

agent-sdk-verifier-ts

Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.

32.8K stars

comment-analyzer

Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request that adds or modifies comments, (3) when reviewing existing comments fo

32.8K stars

agent-sdk-verifier-py

Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.

32.8K stars