AGENT SKILLBY LOUISBLYTHE
Competitor mention handling
AT A GLANCE
Competitor mention handling is a go-to-market skill for AI agents. When the user wants to build or improve a sales bot's ability to respond appropriately when prospects bring up competitors. It is published by louisblythe in the louisblythe/sales-skills GitHub repository (134 stars), which does not specify a license. Install it with: npx skills add louisblythe/sales-skills --skill competitor-mention-handling
- SOURCE REPOSITORY
- louisblythe/sales-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- Not specifiedCHECK THE REPO
- CATEGORIES
- SKILL.MD SIZE
- 6.6 KB270 LINES
QUICK ANSWER
- WHAT IT IS01
- When the user wants to build or improve a sales bot's ability to respond appropriately when prospects bring up competitors. Its edge is a particular angle on competitive research, giving the agent tighter constraints than a plain competitor mention handling request.
- INPUTS02
- Context for competitive research: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for competitive research: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add louisblythe/sales-skills --skill competitor-mention-handlingREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 27
Competitor Mention Handling#
You are an expert in building competitor mention handling for sales bots. Your goal is to help developers create systems that respond professionally and effectively when prospects bring up alternatives.
Types of Competitor Mentions#
Information Seeking#
"How do you compare to [Competitor]?"
"What's different from [Competitor]?"
"I've heard of [Competitor]—how are you different?"
Intent: Genuine curiosity, research phase
Response: Educational, factual comparisonAlready Using Competitor#
"We currently use [Competitor]"
"We've been on [Competitor] for 2 years"
"We just signed with [Competitor]"
Intent: Testing if switch is worth it
Response: Understand satisfaction, find gapsPrice Comparison#
"[Competitor] is cheaper"
"We can get [Competitor] for half the price"
"Why should we pay more than [Competitor]?"
Intent: Leverage for discount or justify choice
Response: Value differentiation, not price matchLoyalty Signal#
"We love [Competitor]"
"[Competitor] has been great for us"
"Not sure we want to switch from [Competitor]"
Intent: Signaling low interest
Response: Respect their choice, find specific gapsNegative Mention#
"We're looking because [Competitor] doesn't..."
"Frustrated with [Competitor]'s support"
"[Competitor] keeps having outages"
Intent: Ready to switch, validating you're better
Response: Acknowledge pain, show how you're differentResponse Framework#
The PACE Method#
P - Pause (don't react defensively)
A - Acknowledge (validate their perspective)
C - Clarify (understand context)
E - Educate (share differentiation)Example Application#
Prospect: "[Competitor] seems to have better integrations"
P: (Don't immediately defend)
A: "Integration coverage is definitely important."
C: "Which integrations are most critical for your workflow?"
E: [Based on their answer, address specifically]
"We actually have deep integration with [X] that goes
beyond what [Competitor] offers—let me explain..."Handling Specific Scenarios#
"How are you different from [Competitor]?"#
Bad response:
"We're better because [feature dump]"
Good response:
"Great question! The main differences depend on what's
most important to you. Are you more focused on [Use Case A],
[Use Case B], or something else? That'll help me highlight
what matters most for your situation."
Then provide targeted differentiation."We're already using [Competitor]"#
Bad response:
"You should switch because..."
Good response:
"Got it! How's that going for you?
...
[If satisfied]: "That's great. What prompted you to take
this call/respond to our outreach?"
[If issues]: "I hear that a lot. What specifically isn't
working well?""[Competitor] is cheaper"#
Bad response:
"Let me see if I can match their price"
Good response:
"They might be—pricing depends on what's included.
Can you share what you're getting at that price point?
I want to make sure we're comparing apples to apples."
Or:
"That's fair. The customers who choose us over [Competitor]
usually do so because [specific value]. Is [that value]
important for what you're trying to do?""I've heard bad things about you"#
Bad response:
"That's not true" (defensive)
Good response:
"I appreciate you bringing that up. Do you mind sharing
what you heard? I want to address it directly, and if
there's something we need to improve, I want to know."Competitor Intelligence Integration#
Real-Time Lookup#
When competitor mentioned:
1. Identify which competitor
2. Pull relevant battlecard data
3. Load common objections
4. Prepare differentiation points
5. Note any recent news/changes
Response incorporates:
- Known weaknesses (factual, not disparaging)
- Your strengths in that area
- Customer stories of switchingHandling Unknown Competitors#
Prospect: "We're looking at [Unknown Startup]"
Response:
"I'm not as familiar with them—can you tell me what
drew your attention? That'll help me understand what's
important to you and how we compare."
Then:
- Note for competitive intelligence
- Focus on your value, not their unknown weakness
- Ask good discovery questionsTone Guidelines#
Never Disparage#
❌ "[Competitor] is terrible"
❌ "Their product is buggy"
❌ "They're going to go out of business"
❌ "I hear they have awful support"
✓ "We've heard some customers had challenges with [X]"
✓ "Where we differ is [specific capability]"
✓ "That's a different approach—here's our philosophy"
✓ "Some teams prefer [their approach], others prefer [ours]"Stay Confident, Not Arrogant#
❌ "We're obviously better"
❌ "There's no comparison"
❌ "Anyone serious chooses us"
✓ "We're a great fit for teams that need [X]"
✓ "Customers choose us when [specific scenario]"
✓ "The difference is most noticeable in [area]"Acknowledge Their Strengths#
"[Competitor] is solid for [use case]. Where we differ
is [your strength]—which tends to matter more when
you're focused on [prospect's stated goal]."
This builds trust by being fair and focuses on fit.Switching Conversations#
From Competitor to You#
If they're using competitor and open to switching:
1. Understand the pain
"What's the main thing that's not working?"
2. Validate the frustration
"That sounds frustrating, especially when..."
3. Show your solution
"Here's how we handle that differently..."
4. Address switching friction
"Switching is easier than you might think. We have a
migration team that handles everything."
5. Social proof
"Company X made the same switch last quarter—they
were up and running in [timeframe]."Handling "Just Signed" with Competitor#
Prospect: "We actually just signed with [Competitor] last month"
Response:
"Congrats on making a decision! How's the implementation going?
[Pause]
Totally understand the timing isn't right for a switch.
That said, would it be helpful to stay in touch? Things
change, and I'd rather you have my info than not.
If nothing else, I'm happy to answer questions about
the space in general—no pitch, just helpful context."Documentation#
Logging Competitor Mentions#
Track:
- Which competitor mentioned
- Context (comparing, using, heard about)
- Specific features/concerns raised
- Your response
- Outcome
Feed back to product/marketing for competitive positioning.Win/Loss Attribution#
When deals close (won or lost):
- Primary competitor involved
- Key differentiation points
- What swayed decision
- Price difference (if known)
- Feature gaps (either way)FAQ
07 QUESTIONS
01What is the Competitor mention handling agent skill?
When the user wants to build or improve a sales bot's ability to respond appropriately when prospects bring up competitors. It is listed under go-to-market in the 100xLab agent skills directory.
02How do I install Competitor mention handling in Cursor, Claude Code, or Codex?
Run npx skills add louisblythe/sales-skills --skill competitor-mention-handling in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Competitor mention handling, not every skill in the repository.
03What does the Competitor mention handling SKILL.md cover?
The SKILL.md includes sections on Types of Competitor Mentions, Information Seeking, Already Using Competitor, Price Comparison, Loyalty Signal and Negative Mention. Read the full text on this page or in plain markdown at /resources/agent-skills/louisblythe-sales-skills--competitor-mention-handling--1urgluw/raw.
04Which agents can use Competitor mention handling?
Competitor mention handling installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Competitor mention handling under?
No license was detected on the louisblythe/sales-skills repository, so the license is not specified. Check with louisblythe before you redistribute or build on the skill.
06Is Competitor mention handling free to use?
Reading and installing Competitor mention handling costs nothing, because it is published in a public GitHub repository. The repository specifies no license, so ask louisblythe before you reuse or redistribute it.
07Where is the source of Competitor mention handling?
Competitor mention handling comes from https://github.com/louisblythe/sales-skills, which has 134 GitHub stars. The SKILL.md is at https://github.com/louisblythe/sales-skills/blob/HEAD/skills/competitor-mention-handling/SKILL.md. The author is louisblythe.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Competitor mention handling was written by its original authors and is published in louisblythe/sales-skills (opens GitHub in a new tab) under no license stated in the repository. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.