Sales Cold Outreach
Sales Cold Outreach is an code AI skill with a core value of High-conversion cold emailing, B2B sales enablement, objection handling, and demo-to-close playbooks. It
helps developers solve real-world problems in the code domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
High-conversion cold emailing, B2B sales enablement, objection handling, and demo-to-close playbooks.
Quick Facts
mkdir -p ./skills/sales-cold-outreach && curl -sfL https://raw.githubusercontent.com/mayurrathi/awesome-agent-skills/main/skills/sales-cold-outreach/SKILL.md -o ./skills/sales-cold-outreach/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 1.4.2 Sales Cold Outreach
This skill defines the standards for outbound prospecting and B2B sales conversion.
1. High-Conversion Cold Email
**Goal:** Get a reply, not a sale.
* **Structure:** Observation (Personal) → Problem (Relevant) → Proof (Case study) → Ask (Interest-based).
* **Personalization:** If you can remove the first line and the email still makes sense, the personalization is too weak.
* **CTA:** Use low-friction asks ("Is this worth a look?") instead of high-friction ones ("Can we talk for 30 mins Thursday?").
* **Sequencing:** 3-5 emails total, each adding a new value angle/resource. Never "just checking in."
2. Sales Enablement Collateral
**Goal:** Arm the "Champion" to sell internally.
* **One-Pagers:** Ultra-scannable (30 sec) summaries covering the Problem, Solution, and 3 Differentiators.
* **Pitch Decks:** 10-12 slides. Focus on "The Shift" in the market and the "ROI" of your solution.
* **Comparison Pages:** Fair "vs" pages that highlight your strengths for specific use cases.
3. Objection Handling
**Goal:** Neutralize concerns with evidence.
* **Framework:** Acknowledge → Clarify → Respond (with Proof) → Confirm.
* **Common Objections:** Price ("ROI calculation"), Timing ("Quick-win scenario"), Competition ("Differentiator card").
* **Battle Cards:** Quick-reference docs for reps to use live on calls.
4. Demo & Closing Playbooks
**Goal:** Show value, then move to next steps.
* **Discovery First:** Never demo a feature until you know the specific pain point it solves for that prospect.
* **The "Check-in":** Ask "Does this solve the problem you mentioned?" after every major feature demo.
* **Trial Gating:** Use proof of value (Skill 14) during the trial to push for the close.
5. Sales-Marketing Handoff (SLA)
* **MQL Criteria:** Fit (Persona) + Engagement (Activity).
* **Response Time:** Sales should respond to high-intent leads within 5 minutes for maximum conversion (lead connect).
🎯 Best For
- Claude users
- Software engineers
- Development teams
- Tech leads
💡 Use Cases
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Sales Cold Outreach to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is Sales Cold Outreach compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for Sales Cold Outreach?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install Sales Cold Outreach?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/sales-cold-outreach/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.