google-agents-cli-scaffold
Project scaffolding, deployment configuration, and CI/CD setup for Google ADK agents.
sales-compete
Runs competitive displacement campaigns — find competitor customers, identify those ready to switch, and build targeted outreach with displacement-specific messaging. Use when you know prospects are using a competitor and want to win them over, need to find companies likely to switch, losing deal...
Full skill instructions
Help the user find competitor customers, identify those ready to switch, and build targeted outreach with displacement-specific messaging. This skill is platform-agnostic but references Apollo.io's technographic and intent data as the primary source. The same frameworks apply to ZoomInfo, G2, BuiltWith, HG Insights, or any technographic/intent provider.
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
Which competitor are you targeting?
What do you sell, and what's the primary displacement angle?
What data sources do you have access to?
What's your ICP? (Overlay on top of the competitor's installed base — not every competitor customer is a good fit for you)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
Use technographic filters to find companies using the competitor's product:
Don't target the entire installed base — narrow to your ICP:
| Data source | Accuracy | Lag | Best for |
|---|---|---|---|
| Apollo technographic | 70-80% | 3-6 months | Broad installed base discovery |
| BuiltWith/HG Insights | 80-90% | 1-3 months | Web/SaaS technology detection |
| G2 visitor data | High intent signal | Real-time | Active evaluators |
| CRM win/loss data | 100% (your data) | Current | Known competitive encounters |
Layer signals on top of the installed base to identify companies ready to switch:
| Signal | Source | Readiness level | What it means |
|---|---|---|---|
| Researching alternatives | Intent data (Apollo/Bombora), G2 comparison views | Very high | Actively evaluating — act fast |
| New leader hired | Job change alerts (Apollo, LinkedIn) | High | New VP/CTO in first 90 days = re-evaluation window |
| Contract renewal timing | Industry knowledge, sales intel | High | 60-90 days before renewal is the sweet spot |
| Hiring for roles your product replaces | Job postings (Apollo, LinkedIn) | Medium-high | Building capacity = potential dissatisfaction with current tool |
| Competitor mentioned in negative context | G2 reviews, Reddit, social | Medium | Public dissatisfaction, but may not be actively looking |
| Funding event | Apollo, Crunchbase | Medium | New budget to re-evaluate stack |
| Technographic change | Apollo, BuiltWith | Medium | Removing adjacent tools may signal broader stack re-evaluation |
Multiple signals compound readiness. Score each prospect:
| Signals present | Priority | Action |
|---|---|---|
| 3+ signals (e.g., new CTO + researching alternatives + contract renewal) | Immediate | Direct outreach, top of queue |
| 2 signals (e.g., new leader + hiring) | High | Prioritized outreach within 1-2 weeks |
| 1 strong signal (researching alternatives) | Medium-high | Standard outreach cadence |
| 1 weak signal (funding, tech change) | Medium | Add to nurture, monitor for additional signals |
| ICP fit only, no signals | Low | Long-term nurture, not active outreach |
| Tier | Criteria | Volume target | Outreach approach |
|---|---|---|---|
| Tier 1 — Active | ICP fit + 2+ displacement signals | 10-15% of base | Hyper-personalized, multi-channel, reference specific signals |
| Tier 2 — Primed | ICP fit + 1 signal or very strong fit | 25-35% of base | Personalized at segment level, competitor-aware messaging |
| Tier 3 — Latent | ICP fit, no active signal | 50-60% of base | Nurture content, thought leadership, not direct displacement pitch |
For each Tier 1 prospect, identify the specific displacement angle:
| Prospect situation | Messaging angle |
|---|---|
| New leader (first 90 days) | "As you evaluate your stack..." — frame as helping them succeed in their new role |
| Researching alternatives | "I noticed companies like yours are evaluating [category]..." — don't reveal your data source |
| Hiring for roles your product addresses | "I see you're scaling [function]..." — position as enabling growth, not replacing tools |
| Negative competitor reviews | "Many [competitor] customers tell us..." — reference common pain points, not specific reviews |
| Contract renewal approaching | "Before you renew..." — create urgency around the renewal window |
For the outreach team, create a quick-reference battle card:
Design signal-specific outreach strategies:
/sales-cadence for detailed design/sales-cadence/sales-cadenceThis skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ### Related skills, e.g., /sales-leadmagic), read that platform skill's actual SKILL.md first. The 1-line description in ### Related skills is enough to identify a candidate — it's not enough to commit to it or to write a prompt that invokes it well.
How to read it:
~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.
/sales-prospect-list — Build general prospect lists (non-competitive)/sales-cadence — Design the multi-channel sequence for displacement outreach/sales-objection — Handle "we're happy with [competitor]" and loyalty objections/sales-intent — Interpret buying signals beyond competitive displacement/sales-positioning — Develop competitive messaging frameworks/sales-leadmagic — LeadMagic competitive ad intelligence, technographics, and company enrichment/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-doDon't trash-talk the competitor in outreach. Lead with your value, not their flaws. Negative selling triggers defensiveness — especially if the prospect chose the competitor and feels personally attached to the decision.
Don't assume technographic data is real-time. Tech installs in Apollo and similar tools can be 3-6 months stale. A company may have already switched away from the competitor, or the install may be a free tier/trial they never actually use. Always validate with additional signals.
Don't target the entire installed base. Most competitor users are happy — or at least not unhappy enough to switch. Blasting 10,000 competitor customers with "switch to us" messages wastes effort and damages your brand. Focus on those with displacement signals.
Don't forget switching costs. The prospect isn't just evaluating your product vs. the competitor — they're evaluating your product vs. the competitor PLUS the pain of migrating. Address migration support, onboarding help, and data transfer upfront or the prospect won't engage.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
User says: "Help me take customers away from Datadog" Skill does:
User says: "I know 50 companies use [competitor]. Which ones should I target first?" Skill does:
User says: "A competitor's customer just hired a new CTO. How do I approach?" Skill does:
Cause: Competitor's technology isn't well-tracked in your data provider, or they use a private/custom deployment Solution: Try multiple data sources (Apollo + BuiltWith + G2). Use competitor name in intent topics as an alternative signal. Check CRM win/loss data for known competitive encounters.
Cause: Messaging is too aggressive ("switch from X") or too generic (doesn't address the prospect's specific situation) Solution: Revisit messaging angles — lead with the prospect's pain, not your product. Test whether softening the competitive angle improves response rates. Consider whether the intent signal was false positive.
Cause: They may genuinely be happy, or they're brushing you off because the pitch wasn't relevant
Solution: Shift from displacement to education — share thought leadership that makes them question whether "happy" means "optimal." Use /sales-objection for handling the loyalty objection specifically.
Project scaffolding, deployment configuration, and CI/CD setup for Google ADK agents.
Set up tracing, logging, and monitoring for deployed ADK agents across Cloud Trace, BigQuery, and third-party platforms.
Enterprise Azure infrastructure architect generating Bicep or Terraform from workload descriptions.
Plan and configure production-ready Azure Kubernetes Service clusters with Day-0 and Day-1 best practices.
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
Web search, scraping, extraction, crawling, and monitoring via ScrapeGraph AI CLI.
Skill for working with Firebase Hosting (Classic). Use this when you want to deploy static web apps, Single Page Apps (SPAs), or simple microservices. Do NOT use for Firebase App Hosting.
Deploy and manage web apps with Firebase App Hosting. Use this skill when deploying Next.js/Angular apps with backends.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Build SEO-optimized pages at scale using templates, data, and proven playbook patterns.
Design and build isolated, reusable Convex backend components with clear boundaries and app-facing wrappers.
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Opus.ai: Revolutionize Your Web Experience
Build a no-code AI app in minutes.
An IDE for code migration from legacy to modern frameworks through coding agents.
Automate CGI animation in live-action scenes
Branded artistic QR-code concepts
Launch a website in seconds with AI.
Streamline Your Coding Experience with AI Code Helper
Convert any screenshot or design to clean code.