Skip to content
Skills Library
Sales & customer service · Writing

lead-reply

/lead-reply

Draft high-conversion, charming, consultative, and non-salesy replies to inbound leads and inquiries. Considers real product capabilities, persona, and next steps without AI slop. Use for /lead-reply, "draft reply to lead", or sales inquiries.

Author
scino ↗
Repository
fstack ↗
Licence
MIT
Last repository change
26.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draft high-conversion, charming, consultative, and non-salesy replies to inbound leads and inquiries. Considers real product capabilities, persona, and next steps without AI slop. Use for /lead-reply, "draft reply to lead", or sales inquiries.

Triggers from the description

draft reply to lead
Original author description

Draft high-conversion, charming, consultative, and non-salesy replies to inbound leads and inquiries. Considers real product capabilities, persona, and next steps without AI slop. Use for /lead-reply, "draft reply to lead", or sales inquiries.

How it works

  1. When to Invoke
  2. Core Philosophy: The Anti-SDR Posture
  3. The Workflow
  4. Example Output
Original SKILL.md headings · 77 lines, 564 words
SKILL.md preview
---
name: lead-reply
description: Draft high-conversion, charming, consultative, and non-salesy replies to inbound leads and inquiries. Considers real product capabilities, persona, and next steps without AI slop. Use for /lead-reply, "draft reply to lead", or sales inquiries.
menu-description: draft human, consultative replies to inbound sales leads
---

# Lead Reply

Turn raw inbound lead inquiries, demo requests, and sales emails into authentic, high-converting replies that sound like a passionate, thoughtful founder—not a spammy SDR or automated AI robot.

---

## When to Invoke

Use whenever you need to reply to:
- A potential customer reaching out via contact form or email.
- A prospect asking whether your product supports specific features or integrations.
- An enterprise or SMB asking about pricing, security, or enterprise tiers.
- A warm introduction from an investor or mutual connection.

---

## Core Philosophy: The Anti-SDR Posture

1. **Be a Consultative Builder, Not a Pitch Machine**:
   - Talk founder-to-founder (or engineer-to-engineer).
   - Answer their direct question in the first 2 sentences. Never dodge with *"That's a great question, let's jump on a 30-minute discovery call to discuss your synergies."*
2. **Honesty on Capabilities**:
   - If the product does it: state how simply and clearly.
   - If the product doesn't do it yet: say so plainly (*"We don't support X today because we're focused on nailing Y. If X is a hard blocker for you, we might not be the best fit right now, but here's how some teams work around it..."*). Brutal honesty builds immediate trust.
3. **Zero Robotic Slop**:
   - No *"I hope this email finds you well"*.
   - No *"I would love to pick your brain"*.
   - No *"revolutionary," "game-changing," "seamlessly integrate"*.
   - Use short paragraphs (1-3 sentences max). Write like you type in Slack or Apple Mail on a phone.

---

## The Workflow

### Step 1: Analyze the Inbound
Extract and classify:
1. **Persona**: Are they a solo developer, technical founder, VP Engineering, or procurement manager?
2. **Specific Needs & Pain**: What problem are they trying to solve right now?
3. **Subtext & Urgency**: Are they evaluating 3 competitors? Do they have a deadline?

### Step 2: Cross-Reference Product Reality
Check the current project state (README, documentation, pricing, code):
- What is supported in production today?
- What requires custom enterprise setup?
- What is out of scope?

### Step 3: Draft the Response
Structure:
1. **Direct Greeting**: First name only (*"Hey Alex,"*).
2. **Direct Answer First**: Address their main question immediately.
3. **Context / Proof**: 1-2 sentences on how existing users or you personally use it.
4. **Low-Friction Next Step**:
   - Don't push a heavy calendar link if an async answer suffices.
   - Give an option: *"Happy to spin up a quick sandbox for you to test, or if you prefer a 15-min walkthrough, grab any slot here [link]."*
5. **Sign-off**: Warm, informal (*"Best, / Cheers, / Talk soon,"* + Founder Name).

### Step 4: Polish with `/unslop-email`
Pass the draft through the unslop email principles to remove any residual corporate stiffness.

---

## Example Output

```markdown
Hey Sarah,

Yes, we handle Webhook retries with exponential backoff out of the box. If your endpoint is down, we buffer events for up to 72 hours and alert you in Slack.

Regarding SOC2: we're currently Type I certified and our Type II audit finishes in Q3. I can share our security packet and bridge letter if you need them for compliance.

If you'd like to test it out on a staging project, here's a link to skip the waitlist [link]. Or if you prefer a quick 15-min technical walkthrough, feel free to grab a time that works for you: [link].

Best,
Fabio
```

Versions

The database has no other skills named lead-reply.

Database snapshot: 13.11.2026 · package version 6147d334bc65 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100speed-to-lead
    Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to…
  • 100gmail-lead-desk
    Gmail Lead Desk — standalone sales/CS Gmail skill via the AISA gateway: OAuth connect, scan unread leads, summarize threads, draft template replies (default draft-only), archive with labels. Keywords: Gmail Lead Desk, Gmail, lead desk, sales, customer support, follow-up, unread,…
  • 90posthog-inbound-leads
    Evaluate and respond to inbound PostHog sales leads from Salesforce. Use this skill when any PostHog TAE needs to triage an inbound lead — deciding whether to qualify for a call, route to self-serve, or disqualify — and then draft an appropriate response email. Checks Vitally…
  • 100kai-sdr-reply-triage
    Triage SDR replies and turn inbound responses into safe next actions, CRM handoff notes, suppression updates, objection responses, referrals, and meeting prep triggers. Use when "SDR reply", "triage replies", "outbound replies", "interested reply", "objection reply", "not…
  • 100conversational-sales
    Run private-traffic (私域) sales with overseas customers on WhatsApp, Instagram and Messenger DMs, Telegram and email: lead intake and registration, lead qualification and scoring, chat scripts (话术) from first reply to close and follow-up, and an FAQ library. Use when the user…
  • 100im-reply
    Handle the comments under the user's own reels and posts - draft replies to the ones worth answering, sorted by which ones are. Use when the user pastes their comments, says "reply to these", "handle my comments", "someone said X on my reel", or is dealing with a critic, a hater…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.