ClaudeSuperPower
SubmitLog in

outreach-research

Skill

Build a portable outreach positioning brief (what you sell, to whom, how you differentiate) before drafting multi-touch B2B sequences. Use when the user says "help me draft outreach", "build my positioning brief", "outreach research", "what should I say to prospects", "lusha outreach brief", or any

0Writing

Install

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

What is outreach-research?

Build a portable outreach positioning brief (what you sell, to whom, how you differentiate) before drafting multi-touch B2B sequences. Use when the user says "help me draft outreach", "build my positioning brief", "outreach research", "what should I say to prospects", "lusha outreach brief", or any request to capture positioning before outreach copy. Stage 1 only — not for drafting sequences (use outreach-sequence once a brief exists).

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

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

Documentation

README · ~13 min read

Outreach Research

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 sequences to contacts they have already shortlisted with Lusha, or to a small audience they paste or describe directly.

You are not pitching Lusha. You are pitching the user's own product on their behalf, in their voice. Every sequence draws on three things: the user's positioning (what they sell, to whom, against which competitors), the prospect's identity and the freshest signals available about them, and the user's stated goal for this outreach (book a call / drive a trial signup / warm intro / share a 1-pager / etc.).

This skill runs in two stages:

  • Stage 1 — Positioning intake (this skill). Gathers a portable positioning brief once per customer per session. The brief captures what the customer sells, who they target, and how they differentiate; it is saved as a markdown file the user can hand-edit between sessions and reload to skip intake next time.
  • Stage 2 — Drafting (outreach-sequence). Consumes the brief plus an audience and produces handoff-ready outreach copy.

This skill implements Stage 1 only. It is a text-only workflow — do not invoke any Lusha MCP tools. After the brief is saved, hand off to outreach-sequence for copy drafting (optionally run prospect first if the user still needs a contact list).

Step 1 — Parse Session Intent

Read the user's message for context — company name, product, or a later goal (e.g. "book 15-min discovery calls with RevOps directors").

If a valid brief is already in the conversation and the user wants sequence drafting (paste contacts, attach a CSV, "draft email 1 for this list", etc.) — do not run intake. Point them to outreach-sequence with the brief and audience. Mention prospect only if they still need a contact list.

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