home / skills / omer-metin / skills-for-antigravity / sales

sales skill

/skills/sales

This skill helps you automate sales workflows with AI tools, accelerating prospecting, outreach, CRM setup, and pipeline management for higher conversions.

npx playbooks add skill omer-metin/skills-for-antigravity --skill sales

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.2 KB
---
name: sales-ai-tools
description: Master the AI tools that supercharge your sales process. From prospecting to closing, automate the grind and focus on building relationships that convert. Use when "sales automation, cold outreach, lead generation, prospecting tools, CRM setup, sales engagement, pipeline management, conversation intelligence, sales, crm, outreach, prospecting, leads, automation" mentioned. 
---

# Sales Ai Tools

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill helps sales teams master AI tools that streamline prospecting, outreach, pipeline management, and closing. It packages recommended patterns, risk checks, and validation rules so you can automate repetitive tasks while keeping data quality and compliance intact. Use it to accelerate lead generation and scale repeatable sales motions without sacrificing accuracy.

How this skill works

The skill guides creation by following prescribed patterns from references/patterns.md and flags dangerous or brittle setups using diagnostics from references/sharp_edges.md. It also runs objective validations against references/validations.md to ensure inputs, templates, and automations meet required constraints. Outputs include recommended automations, risk explanations, and concrete validation feedback.

When to use it

  • Setting up or evaluating AI-driven prospecting and cold outreach workflows
  • Designing lead scoring, routing, or CRM automation that must meet strict rules
  • Reviewing conversation intelligence pipelines for data quality and bias risks
  • Automating follow-up sequences or multi-channel sales cadences
  • Auditing existing AI sales tools for critical failure modes or policy gaps

Best practices

  • Follow patterns in references/patterns.md as the canonical blueprint for designs
  • Consult references/sharp_edges.md to understand why failures happen before deploying
  • Validate all inputs, templates, and sample outputs against references/validations.md
  • Limit automation scope incrementally; test on small cohorts before scaling
  • Log decisions and maintain human review gates for high-stakes actions

Example use cases

  • Create a prospecting pipeline that auto-enriches leads, scores them, and routes high-value prospects to reps
  • Build a cold outreach cadence with AI-personalized snippets that pass validation checks
  • Diagnose why an AI summarizer is dropping key conversation topics using sharp-edges diagnostics
  • Validate CRM field mappings and automation triggers against strict validation rules before production

FAQ

Do I have to follow the provided reference files exactly?

Yes. Use references/patterns.md for creation, references/sharp_edges.md for diagnosing failures, and references/validations.md to validate outputs. They are the authoritative guides.

Can I deploy automations without human review?

Avoid full automation for high-impact actions. Use incremental rollout and human-in-the-loop review gates as advised in the best practices.