Skip to content
Back to skills

Outreach

ASecurity

Activate for: outreach, write email, LinkedIn message, cold email, cold outreach, personalised email, personalise, draft message, first touch, intro email, introduction email, ghostwrite, write for me, email draft, DM, direct message, InMail, connection request, WhatsApp message, outreach message, sales message, prospecting email. NOT for: multi-touch sequences (use sequence), post-call follow-ups (use follow-up), marketing content creation (use content-creation), ad copy or subject lines (us...

  • 28 stars
  • 0 votes
  • 1 copy
  • 5 views
  • Added May 27, 2026
data-aigoaws

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add panaversity/agentfactory-business-plugins --skill outreach --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Outreach?

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

Security grade badge for Outreach
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/panaversity-outreach/badge)](https://www.skillsdirectory.com/skills/panaversity-outreach)

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: outreach
description: >
  Activate for: outreach, write email, LinkedIn message, cold email,
  cold outreach, personalised email, personalise, draft message,
  first touch, intro email, introduction email, ghostwrite, write for
  me, email draft, DM, direct message, InMail, connection request,
  WhatsApp message, outreach message, sales message, prospecting email.
  NOT for: multi-touch sequences (use sequence), post-call follow-ups (use follow-up), marketing content creation (use content-creation), ad copy or subject lines (use copywriting).
---

## OUTREACH WORKFLOW

### Phase 1: Input Collection

Before drafting any message, collect:

1. Research brief for this prospect (or run /research first)
2. Channel: LinkedIn DM / Email / Phone script / WhatsApp / Other
3. Goal of this first touch: Discovery call / Demo / Referral /
   Content share / Event invite / Re-engagement
4. Specific hook to lead with (from research brief -- The Hook section)
5. Rep's name and title (for sign-off)
6. Any constraints: word count, brand requirements, prior interactions

### Phase 2: Five Laws Compliance Check

BEFORE DRAFTING -- load and apply all five laws from global router:

Law 1: What is the specific, verifiable reference for this prospect?
If none identified in research: DO NOT draft -- run /research first
If hook is generic ("I see your company is growing"): NOT compliant
Required: specific post, specific news event, specific company situation

Law 2: How will the first sentence be about THEM, not us?
Draft must open with: their situation / their challenge / their news
First sentence may NOT begin with: "We", "I", "My company", "Our product"

Law 3: What is the ONE ask?
Define before drafting. Options:

- "15-minute call this week?"
- "Worth a quick conversation?"
- "Would it be useful to send you [specific resource]?"
  NOT: "Reply if interested" / multiple options / vague CTAs

Law 4: Word count limit?
LinkedIn DM: 100 words maximum
Email: 150 words maximum
Cold call script: 60 seconds spoken (approximately 120 words)

Law 5: Banned language check (remove any of these before outputting):
leverage, synergy, best-in-class, seamless, robust, solution,
game-changing, revolutionary, disruptive, holistic, end-to-end,
cutting-edge, world-class, innovative, empower, unlock, transform

### Phase 3: Draft Generation

STRUCTURE FOR EMAIL:

Subject: [Short, specific, relevant to their situation -- not clickbait]
Good: "Re: scaling ops at [Company]"
Good: "[Shared problem] -- [Company name]"
Bad: "Quick question" / "Following up" / "Introduction"

Line 1: [Specific reference to their situation, news, or post]
Line 2: [Bridge: what this means / why it matters]
Lines 3-4: [Your connection: 1-2 sentences on how you help
companies in exactly this situation. Specific, not generic.]
Line 5: [The one ask -- single sentence, direct, low-commitment]
Sign-off: [Name | Title | Company -- no more]

STRUCTURE FOR LINKEDIN DM:

Opening: [Immediate reference to specific hook -- no "Hi, I saw your profile"]
Middle: [2-3 sentences: connection between their situation and your work]
Close: [The one ask]

### Phase 4: Five Laws Final Check

After drafting, verify:
Law 1: Named a specific, verifiable reference?
Law 2: First sentence is about them?
Law 3: Exactly one ask?
Law 4: Within word count?
Law 5: No banned language?

If any check fails: revise before outputting.

### Outreach Output Format

OUTREACH DRAFT -- [Channel] | [Prospect Name / Company]

---

[SUBJECT LINE (email only):]

[Message body]

[Sign-off]

---

FIVE LAWS CHECK:
Law 1 (Specific reference): [What was referenced]
Law 2 (Lead with them): [First sentence focus]
Law 3 (One ask): [The ask]
Law 4 (Word count): [X words / limit: Y]
Law 5 (No jargon): [Confirmed clean]

NOTES:
Hook used: [Description of the hook]
Tone: [Peer-level / Educational / ROI-focused]
Confidence: [HIGH / MEDIUM -- based on depth of personalisation]

## FOLLOW-UP MESSAGE VARIANTS

Always generate with the primary outreach:

Day 3 follow-up (if no response to LinkedIn DM -> switch to email):
Same hook, different angle. Not "just checking in" -- add value or
reframe the problem differently.

Day 7 follow-up (if no response to email):
Shorter. Different subject line. Single question. Consider:
"Is this not a priority right now, or is [topic] just not relevant?"
This question often gets responses from genuinely busy prospects.

## NEVER DO THESE

- NEVER output a message that has not passed all five laws checks
- NEVER write "Just following up" as an opening -- it signals no new value
- NEVER use the prospect's first name more than once in a short message
  (overuse feels manipulative)
- NEVER CC the prospect's manager without their consent -- always
  considered aggressive and damages the relationship
- NEVER reference information that could feel invasive
  (e.g. "I saw you were just in Dubai" from social media) --
  reference professional signals, not personal location data
- NEVER send the same message to two people at the same company
  without checking for internal awareness

Files in this skill

  • SKILL.md5 KB
  • evals/evals.json13.3 KB

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.