Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills Aโ€“Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Crm Lead Tracking Outreach Automation

ASecurity

CRM integration, lead tracking, outreach automation, and pipeline management. Transform your AI agent into a sales assistant that never lets leads slip through the cracks.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsrustgobashapidocumentation

Works with

cliapi

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill crm-lead-tracking-outreach-automation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Crm Lead Tracking Outreach Automation?

Add the live security badge to your README โ€” it updates automatically with every re-scan.

Security grade badge for Crm Lead Tracking Outreach Automation
[![Security: A โ€” Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-crm-lead-tracking-outreach-automation/badge)](https://www.skillsdirectory.com/skills/rondoflow-crm-lead-tracking-outreach-automation)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: crm-lead-tracking-outreach-automation
description: "CRM integration, lead tracking, outreach automation, and pipeline management. Transform your AI agent into a sales assistant that never lets leads slip through the cracks."
category: "AI & Agents"
author: community
version: "1.0.0"
icon: bot
---

# Sales Skill ๐Ÿ’ผ

**Turn your AI agent into an elite sales operations partner.**

Track leads, manage pipelines, automate outreach, and never lose a deal to poor follow-up again.

---

## What This Skill Does

โœ… **Lead Tracking** โ€” Capture, qualify, and track leads through your pipeline
โœ… **CRM Integration** โ€” Work with your existing CRM or use built-in tracking
โœ… **Outreach Automation** โ€” Generate personalized outreach sequences
โœ… **Pipeline Management** โ€” Track deals, forecast revenue, identify bottlenecks
โœ… **Follow-up Automation** โ€” Never miss a follow-up again
โœ… **Sales Analytics** โ€” Track conversion rates, velocity, and win/loss reasons

---

## Quick Start

1. Set up your sales workspace:
```bash
./scripts/sales-init.sh
```

2. Configure your preferences in `TOOLS.md`:
```markdown
### Sales
- CRM: [HubSpot/Salesforce/Notion/Built-in]
- Default pipeline stages: [Stages]
- Follow-up cadence: [Days between touchpoints]
- Meeting booking link: [URL]
```

3. Start tracking leads!

---

## Lead Management

### Lead Qualification Framework (BANT)

| Criteria | Question | Weight |
|----------|----------|--------|
| **Budget** | Can they afford it? | 25% |
| **Authority** | Are they the decision-maker? | 25% |
| **Need** | Do they have a real problem you solve? | 30% |
| **Timeline** | When do they need a solution? | 20% |

**Lead Score Thresholds:**
- 80-100: Hot ๐Ÿ”ฅ โ€” Contact immediately
- 60-79: Warm โ€” Nurture actively
- 40-59: Cool โ€” Keep in nurture sequence
- 0-39: Cold โ€” Low priority

### Lead Capture Template

```markdown
# Lead: [Company Name]

## Contact Info
- **Name:** [Full Name]
- **Title:** [Job Title]
- **Email:** [Email]
- **Phone:** [Phone]
- **LinkedIn:** [URL]
- **Company:** [Company]
- **Website:** [URL]

## Qualification (BANT)
- **Budget:** [Yes/No/Unknown] โ€” [Notes]
- **Authority:** [Decision-maker/Influencer/User] โ€” [Notes]
- **Need:** [Strong/Moderate/Weak] โ€” [Notes]
- **Timeline:** [Immediate/1-3mo/3-6mo/6mo+] โ€” [Notes]
- **Lead Score:** [X/100]

## Source
- **How they found us:** [Source]
- **First touchpoint:** [Date]
- **Initial interest:** [What they asked about]

## Notes
[Relevant context, pain points, opportunities]

## Next Action
- [ ] [Action] โ€” Due: [Date]
```

---

## Pipeline Management

### Standard Pipeline Stages

| Stage | Definition | Typical Actions |
|-------|------------|-----------------|
| **Lead** | Initial contact, not yet qualified | Qualify, research, initial outreach |
| **Qualified** | BANT criteria met | Discovery call, needs analysis |
| **Discovery** | Understanding needs | Demo prep, stakeholder mapping |
| **Demo/Proposal** | Presenting solution | Demo, proposal creation |
| **Negotiation** | Terms discussion | Handle objections, negotiate |
| **Closed Won** | Deal signed | Onboarding handoff |
| **Closed Lost** | Deal lost | Loss analysis, nurture |

### Pipeline Tracking Template

```markdown
# Sales Pipeline โ€” [Month]

## Summary
- Total pipeline value: $[X]
- Weighted pipeline: $[X]
- Deals in pipeline: [X]
- Expected closes this month: [X]

## By Stage

### Lead ([X] deals, $[X])
| Company | Value | Owner | Last Activity | Next Step |
|---------|-------|-------|---------------|-----------|
| [Name] | $[X] | [You] | [Date] | [Action] |

### Qualified ([X] deals, $[X])
...

### Demo/Proposal ([X] deals, $[X])
...

### Negotiation ([X] deals, $[X])
...

## Stale Deals (>14 days no activity)
| Company | Stage | Last Activity | Recommended Action |
|---------|-------|---------------|-------------------|
```

### Pipeline Velocity Metrics

| Metric | How to Calculate | Target |
|--------|------------------|--------|
| **Win Rate** | Won รท (Won + Lost) | >25% |
| **Average Deal Size** | Total Won รท # Won | Track trend |
| **Sales Cycle** | Avg days from Lead โ†’ Won | <30 days |
| **Pipeline Coverage** | Pipeline รท Quota | 3x+ |

---

## Outreach Automation

### Cold Outreach Sequence

**Day 1: Initial Email**
```
Subject: [Personalized hook based on research]

Hi [Name],

[Observation about their company/role โ€” show you did research].

[One sentence about what you do and why it's relevant to them].

[Specific question or soft CTA].

Best,
[Your name]
```

**Day 3: Follow-up 1**
```
Subject: Re: [Original subject]

Hi [Name],

Wanted to make sure this didn't get buried โ€” [brief restate of value].

[New angle or additional value point].

Worth a quick chat?

[Your name]
```

**Day 7: Follow-up 2 (Value Add)**
```
Subject: [Related resource or insight]

Hi [Name],

Found this [article/resource/insight] and thought of you: [link]

[Brief explanation of why it's relevant].

If this resonates, happy to share how we helped [similar company] with [similar challenge].

[Your name]
```

**Day 14: Break-up Email**
```
Subject: Should I close your file?

Hi [Name],

I haven't heard back, so I'm assuming the timing isn't right.

No worries โ€” I'll close out my notes for now.

If things change, feel free to reply anytime.

[Your name]
```

### Personalization Research Checklist

Before outreach, gather:
- [ ] Recent company news (funding, launch, hire)
- [ ] LinkedIn activity (posts, comments, likes)
- [ ] Company blog/newsletter
- [ ] Mutual connections
- [ ] Tech stack (if relevant)
- [ ] Competitors they might use

---

## Follow-up System

### Never Miss a Follow-up

**The Rule:** Every deal has a next action with a due date. No exceptions.

**Follow-up Cadence by Stage:**
| Stage | Check-in Frequency |
|-------|--------------------|
| Lead | Every 3-5 days |
| Qualified | Every 2-3 days |
| Demo/Proposal | Every 1-2 days |
| Negotiation | Daily |

### Follow-up Reminder Template

```markdown
# Daily Follow-up Queue

## Due Today
| Lead | Stage | Last Contact | Reason | Next Action |
|------|-------|--------------|--------|-------------|
| [Co] | [Stage] | [Date] | [Context] | [Action] |

## Overdue
| Lead | Stage | Days Overdue | Priority |
|------|-------|--------------|----------|
| [Co] | [Stage] | [X] days | ๐Ÿ”ฅ/โš ๏ธ |
```

---

## Meeting Management

### Pre-Meeting Research Template

```markdown
# Meeting Prep: [Company]
**Date:** [Date/Time]
**Attendees:** [Names, titles]

## Company Research
- Founded: [Year]
- Size: [Employees]
- Funding: [Stage/Amount]
- Recent news: [Key items]

## Attendee Research
- [Name 1]: [Background, relevant info]
- [Name 2]: [Background, relevant info]

## Their Likely Pain Points
1. [Pain point based on research]
2. [Pain point based on research]

## Questions to Ask
1. [Discovery question]
2. [Discovery question]
3. [Qualification question]

## Our Value Proposition for Them
[Customized pitch based on research]

## Objections to Expect
1. [Likely objection] โ†’ [Response]
2. [Likely objection] โ†’ [Response]

## Meeting Goals
1. [Specific goal]
2. [Specific goal]
```

### Post-Meeting Notes Template

```markdown
# Meeting Notes: [Company] โ€” [Date]

## Attendees
- [Name, Title]

## Key Takeaways
1. [Insight]
2. [Insight]

## Pain Points Confirmed
- [Pain point]

## Decision Process
- Decision maker: [Name]
- Influencers: [Names]
- Timeline: [When]
- Budget: [Range if discussed]

## Objections Raised
- [Objection]: [How we handled it]

## Next Steps
- [ ] [Action] โ€” Owner: [Name] โ€” Due: [Date]
- [ ] [Action] โ€” Owner: [Name] โ€” Due: [Date]

## Follow-up Email
[Draft the follow-up email here]
```

---

## Objection Handling

### Common Objections & Responses

| Objection | Response Framework |
|-----------|-------------------|
| **"Too expensive"** | Explore value vs cost: "What's the cost of NOT solving this?" |
| **"We use [competitor]"** | "What made you choose them? What's working/not working?" |
| **"Not the right time"** | "What would make it the right time? Can we reconnect then?" |
| **"Need to think about it"** | "Of course. What specifically do you want to think through?" |
| **"Send me info"** | "Happy to. What specifically would be most helpful to see?" |
| **"We're too small"** | "That's actually perfect for [reason]. [Similar customer example]" |

### Objection Documentation

Track objections to improve pitch:
```markdown
# Objection Log

| Date | Company | Objection | Our Response | Result |
|------|---------|-----------|--------------|--------|
| [Date] | [Co] | [Objection] | [Response] | Won/Lost |
```

---

## Sales Analytics

### Weekly Sales Report Template

```markdown
# Sales Report โ€” Week of [Date]

## Summary
- New leads: [X]
- Deals advanced: [X]
- Deals closed won: [X] ($[X])
- Deals closed lost: [X]

## Pipeline Health
- Total pipeline: $[X]
- Change from last week: +/-[X]%
- Weighted pipeline: $[X]
- Forecast this month: $[X]

## Activity Metrics
- Outreach sent: [X]
- Meetings held: [X]
- Proposals sent: [X]
- Follow-ups completed: [X]

## Wins
| Company | Value | Time to Close | Key Factor |
|---------|-------|---------------|------------|
| [Name] | $[X] | [X] days | [What won it] |

## Losses
| Company | Value | Stage Lost | Reason |
|---------|-------|------------|--------|
| [Name] | $[X] | [Stage] | [Why] |

## Focus for Next Week
1. [Priority]
2. [Priority]
```

### Win/Loss Analysis

```markdown
# Win/Loss Analysis โ€” [Quarter]

## Win Patterns
- Common traits of won deals: [Patterns]
- Average deal size: $[X]
- Average sales cycle: [X] days
- Top win reasons:
  1. [Reason]
  2. [Reason]

## Loss Patterns
- Where deals die: [Stage]
- Common objections: [List]
- Top loss reasons:
  1. [Reason]
  2. [Reason]

## Insights & Actions
- [Insight] โ†’ [Action to take]
```

---

## Scripts

### sales-init.sh
Initialize your sales workspace with templates and tracking.

### lead-tracker.sh
CLI tool for quick lead management.

```bash
# Add new lead
./scripts/lead-tracker.sh add "Company Name" "Contact Name" "email@company.com"

# List all leads
./scripts/lead-tracker.sh list

# Update lead stage
./scripts/lead-tracker.sh update "Company Name" --stage "demo"

# Get daily follow-ups
./scripts/lead-tracker.sh followups
```

### pipeline-report.sh
Generate pipeline reports.

```bash
# Weekly pipeline summary
./scripts/pipeline-report.sh weekly

# Monthly forecast
./scripts/pipeline-report.sh forecast
```

---

## CRM Integration

### Built-in Tracking

If you don't use an external CRM, use markdown files:

```
sales/
โ”œโ”€โ”€ leads/
โ”‚   โ”œโ”€โ”€ company-name.md
โ”‚   โ””โ”€โ”€ ...
โ”œโ”€โ”€ pipeline.md
โ”œโ”€โ”€ analytics/
โ”‚   โ”œโ”€โ”€ weekly-YYYY-MM-DD.md
โ”‚   โ””โ”€โ”€ ...
โ””โ”€โ”€ templates/
```

### External CRM Integration

**HubSpot:** Use HubSpot API for syncing
**Salesforce:** Use Salesforce API for syncing
**Notion:** Export/import via CSV or API

---

## Best Practices

1. **Follow up relentlessly** โ€” 80% of sales need 5+ touchpoints
2. **Personalize everything** โ€” Generic outreach = ignore
3. **Always have next step** โ€” Every conversation ends with clear action
4. **Track why you lose** โ€” More valuable than why you win
5. **Speed to lead** โ€” Respond within 5 minutes when possible
6. **Listen more than talk** โ€” Discovery > Pitching
7. **Document everything** โ€” Your future self will thank you
8. **Review pipeline weekly** โ€” Stale deals kill forecasts

---

## Common Mistakes

โŒ **Pitching before understanding** โ€” Do discovery first
โŒ **Forgetting to follow up** โ€” Use reminders religiously
โŒ **Vanity metrics** โ€” Calls made matters less than meetings held
โŒ **Ignoring closed-lost** โ€” They can become wins later
โŒ **No CRM hygiene** โ€” Bad data = bad decisions

---

## License

**License:** MIT โ€” use freely, modify, distribute.

---

*"Sales is not about selling anymore, but about building trust and educating." โ€” Siva Devaki*

Attribution

rondoflowrondoflow
View sourceMore from rondoflow โ†’
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants โ€” handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents โ†’