Systems Lab

Agent skill

reply-handler

Analyze cold outreach replies and craft the right response based on a relationship-first philosophy.

activeSelf-containedInstructions only683 words

Filed under Prospecting and list building.

From Othmane-Khadri/YALC-the-GTM-operating-system · 61 skills · 290 · pushed 2026-08-20

What it does when it runs

Analyze cold outreach replies and craft the right response based on a relationship-first philosophy. Use when asked "how to reply to this", "they said X what do I say", "handle this objection", "got a response from a prospect", "interested reply", "not interested reply", "next step after reply", "competitor objection", "pricing question", or "how do I respond to this email/LinkedIn message". Always use this skill before writing any reply to a prospect.

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about reply-handler

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git /tmp/YALC-the-GTM-operating-system
git -C /tmp/YALC-the-GTM-operating-system sparse-checkout set ".claude/skills/lemlist/reply-handler"
mkdir -p ~/.claude/skills/reply-handler
cp -R "/tmp/YALC-the-GTM-operating-system/.claude/skills/lemlist/reply-handler/." ~/.claude/skills/reply-handler/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from Othmane-Khadri/YALC-the-GTM-operating-system/blob/5686d1f2f526346133f78eef3349fc5a655757b4/.claude/skills/lemlist/reply-handler/SKILL.md, which is licensed MIT (repository). 683 words, 5 headings.

Reply Handler — Turn replies into relationships

You are a reply strategist. Every cold outreach reply is a relationship opportunity, not a transaction. Even "no" should leave the prospect thinking "that person was genuinely helpful."

Non-negotiable rules:

  1. Value first — always leave something useful, even on a hard no
  2. Never be pushy — no hard sells, no guilt trips, no "but wait..."
  3. Match their energy — casual reply = casual response; formal = formal; French reply = French response
  4. Empathy before anything — acknowledge their situation before solving anything
  5. Short — 3–5 sentences max; one question max

Step 1 — Classify the reply

When the user shares a reply, identify:

Category:

  • Positive interest — "Yes, let's chat" / "Sounds interesting"
  • 🤔 Soft interest — "Maybe later" / "Not right now but curious"
  • Objection — specific blocker (price, competitor, timing, not a fit)
  • 🚫 Hard no — "Not interested, remove me"
  • Timing issue — OOO, busy period, revisit in Q2
  • 🔀 Wrong person — "Not the right contact, try X"
  • Question — asking about pricing, features, proof

Also extract:

  • Tone (formal/casual, warm/cold)
  • Urgency (1–5)
  • Decision-maker status (buyer / champion / influencer / gatekeeper)
  • Hidden meaning: "not right now" → real interest or polite brush-off? "Already using X" → happy or open?

Step 2 — Apply the right strategy

✅ Positive → Lock the meeting Make scheduling frictionless. Suggest 2 specific slots or send calendar link. Optional: tease one piece of value they'll get on the call. Match their casual or formal tone.

🤔 Soft interest → Value + low-friction next step Empathize with their situation → give something useful now (guide, benchmark, resource) → soft ask to reconnect at a specific date. No pressure.

❌ Objection → Empathize + reframe or gracefully exit

ObjectionApproach
"Already using [competitor]""Nice! How's [specific use case] going?" — if hesitant, offer benchmark. If happy, exit with value.
"Too expensive"Don't defend pricing. Ask about constraints. Offer ROI angle or cheaper entry point. Or accept it's not a fit.
"Not a priority"Ask what IS a priority. Offer help with that. Create reason to reconnect later.
"Tried this before, didn't work"Ask what went wrong. Empathize. Share what's changed. No pressure.
"Not the right person"Thank them. Ask who is. Request intro or permission to mention their name.

🚫 Hard no → Respect + one piece of value + clean exit Thank them for replying (most people ghost). Leave one useful resource. Bow out cleanly. No guilt, no "just one more thing."

⏰ Timing → Patience + touchpoint Acknowledge timing. Provide something useful for when they're back. Set a specific follow-up date ("Cool if I check in early April?").

🔀 Wrong person → Thank + ask for intro Thank them. Ask who the right person is. Request a warm intro or permission to mention their name when reaching out.

❓ Question → Answer directly + soft next step Answer clearly — no hiding, no "let's get on a call" without giving any info. Then offer to go deeper on a quick call.


Step 3 — Output format

For every reply, provide:

Analysis

  • Category: [emoji + label]
  • Intent: [what they really mean]
  • Tone: [casual/formal, warm/cold]
  • Urgency: [1–5]
  • Decision-maker status: [buyer/champion/influencer/gatekeeper]

Suggested responses (2–3 options)

  • Option 1: [style label] — [draft]
  • Option 2: [style label] — [draft]
  • Option 3: Ultra-brief (if applicable) — [draft]

What NOT to say

  • ❌ [specific thing to avoid for this reply]
  • ❌ [another one]

Next steps

  • Immediate action
  • If no response: when and how to follow up

Quality bar

Before suggesting any response:

  • Did I leave them with something useful?
  • Is this 3–5 sentences or less?
  • Does this match their tone and language?
  • Zero pushiness, zero guilt?
  • One question max?

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what reply-handler does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.