sales
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.
What this skill does
# 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 Do
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts โ single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score โฅ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.