Sales Os
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
Analyze cold outreach replies and craft the right response based on a relationship-first philosophy.
Install Reply Handler
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system reply-handler --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lemlist/reply-handler .claude/skills/reply-handler && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "reply-handler" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handler into .claude/skills/reply-handler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-handler", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handlerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system reply-handler --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/lemlist/reply-handler .agents/skills/reply-handler && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reply-handler" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handler into .agents/skills/reply-handler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-handler", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system reply-handler --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/lemlist/reply-handler .cursor/skills/reply-handler && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "reply-handler" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handler into .cursor/skills/reply-handler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-handler", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git --path .claude/skills/lemlist/reply-handler--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system reply-handler --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/lemlist/reply-handler .gemini/skills/reply-handler && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "reply-handler" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handler into .gemini/skills/reply-handler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-handler", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system reply-handlerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/lemlist/reply-handler .github/skills/reply-handler && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "reply-handler" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handler into .github/skills/reply-handler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-handler", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system reply-handler --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/lemlist/reply-handler .opencode/skills/reply-handler && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "reply-handler" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/reply-handler into .opencode/skills/reply-handler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-handler", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
reply-handler- GitHub stars
- 317
- Token cost
- ~1.1k tokens
- SKILL.md length
- 563 words
- Files
- 1
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze cold outreach replies and craft the right response based on a relationship-first philosophy.
- Works in 3 steps: Classify the reply → Apply the right strategy → Output format
- Asked how to reply to this
- SKILL.md covers Step 1 — Classify the reply, Step 2 — Apply the right…, Step 3 — Output format and Quality bar
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Reply Handler is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Cold outreach. It works with LinkedIn. The repository describes itself as: YALC 1.0, the open-source Clay alternative. MIT, CLI-first, self-hosted, runs in Claude Code. Yalc today is an intelligent orchestration layer that runs pre configured GTM agents…. The licence is MIT.
When your agent uses it
- Asked how to reply to this
- They said X what do I say
- Handle this objection
- Got a response from a prospect
Example prompts
- “how to reply to this”
- “they said X what do I say”
- “handle this objection”
- “/reply-handler”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5686d1f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Reply Handler loads about 1.1k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 563 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Othmane-Khadri/YALC-the-GTM-operating-system at commit 5686d1f, republished under its MIT licence (© Othmane-Khadri). 563 words, ~1,135 tokens.
Download SKILL.mdSave it as
.claude/skills/reply-handler/SKILL.md (or your agent's skills folder).- name
- reply-handler
- description
- 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.
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:
- Value first — always leave something useful, even on a hard no
- Never be pushy — no hard sells, no guilt trips, no "but wait..."
- Match their energy — casual reply = casual response; formal = formal; French reply = French response
- Empathy before anything — acknowledge their situation before solving anything
- 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
| Objection | Approach |
|---|---|
| "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. |
Show full SKILL.md (214 more words)Show less
🚫 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?
© Othmane-Khadri, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/lemlist/reply-handler of Othmane-Khadri/YALC-the-GTM-operating-system.
Open the folder on GitHubat commit 5686d1f
Compare with similar skills
Reply Handler next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Reply Handler this skillOthmane-Khadri/YALC-the-GTM-operating-system | 317 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 138 | — | ~2k | Automated safety check: Pass | MIT | |
| Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week | 145 | — | ~2.6k | Automated safety check: Pass | None | |
| B2B Lead Generationminhnv0807/ai-business-skills | 608 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cold Outreach Sequence BuilderBrianRWagner/ai-marketing-claude-code-skills | 440 | — | ~1.9k | Automated safety check: Pass | None | |
| Outreachyc-software/recruiting | 116 | — | ~3k | Automated safety check: Notes | None |
Similar skills
Cold Outreach Personalizer
aiskilloftheweek/claude-ai-skill-of-the-week
Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Cold Outreach Sequence Builder
BrianRWagner/ai-marketing-claude-code-skills
Builds researched LinkedIn and email outreach for prospects, from a single message to a multi-prospect system, with personalization graded by the signals found.
Outreach
yc-software/recruiting
Draft personalized cold outreach to a candidate the hiring manager hasn't contacted yet.
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
More from Othmane-Khadri/YALC-the-GTM-operating-system
All 57 skills in this repoClaap Weekly Recap
Othmane-Khadri/YALC-the-GTM-operating-system
Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.
Fullenrich Plg Reverse Lookup
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "set up FullEnrich reverse lookup for trial signups", "PLG enrichment webhook", "identify free trial signups via FullEnrich", "reverse email lookup for…
Fullenrich Content Engagers
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "enrich people who engaged with this post", "qualify post engagers with FullEnrich", "scrape and enrich LinkedIn post {URL}", "engagers from this post into…
Fullenrich Event Attendees
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "enrich this LinkedIn event", "enrich attendees of this event", "enrich this attendees CSV", "scrape and enrich LinkedIn event {URL}", "FullEnrich event…
Answer Linkedin Comments
Othmane-Khadri/YALC-the-GTM-operating-system
Reply to comments on a LinkedIn post via Unipile — drafts thread-aware replies grounded in the user's voice and the conversation context, then sends on approval.
Fullenrich Network Activation
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "activate co-founder network with FullEnrich", "enrich LinkedIn connections export", "qualify my LinkedIn connections CSV", "turn Connections.csv into a…
Related
Works with
Categories
Questions about Reply Handler
What does Reply Handler do?
Analyze cold outreach replies and craft the right response based on a relationship-first philosophy. Reply Handler is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Analyze cold outreach replies and craft the right response based on a relationship-first philosophy.
When should I use Reply Handler?
Reply Handler fits situations like: asked how to reply to this; they said X what do I say; handle this objection; got a response from a prospect.
How do I install Reply Handler in Claude Code?
Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a claude-code`. Or copy the skill folder (.claude/skills/lemlist/reply-handler in Othmane-Khadri/YALC-the-GTM-operating-system) into .claude/skills/reply-handler in your project. Claude Code loads it when a task matches its description.
How do I install Reply Handler in Codex?
Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a codex`. Or copy the skill folder (.claude/skills/lemlist/reply-handler in Othmane-Khadri/YALC-the-GTM-operating-system) into .agents/skills/reply-handler in your project. Codex loads it when a task matches its description.
Can I use Reply Handler in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill reply-handler -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reply-handler, .gemini/skills/reply-handler, .github/skills/reply-handler and .opencode/skills/reply-handler in your project.
What does Reply Handler need to run?
SKILL.md names no scripts, command-line tools or credentials: Reply Handler is instructions for the agent only.
Does Reply Handler access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Reply Handler safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Reply Handler use?
Reply Handler is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Reply Handler use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Reply Handler?
Skills that share tags, products or a category with Reply Handler: Sales Os (romangojiberryAI/gojiberryai-sales-os, 138 stars), Cold Outreach Personalizer (aiskilloftheweek/claude-ai-skill-of-the-week, 145 stars), B2B Lead Generation (minhnv0807/ai-business-skills, 608 stars) and Cold Outreach Sequence Builder (BrianRWagner/ai-marketing-claude-code-skills, 440 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Reply Handler?
Othmane-Khadri (a GitHub user) maintains it in Othmane-Khadri/YALC-the-GTM-operating-system, which has 317 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 20, 2026.
Source: Othmane-Khadri/YALC-the-GTM-operating-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.