business/sales/competitive-intelligence/SKILL.md
Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".
npx skillsauth add harsh040506/claude-code-unified-skill-plugin-library competitive-intelligenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Research your competitors extensively and generate an interactive HTML battlecard you can use in deals. The output is a self-contained artifact with clickable competitor tabs and an overall comparison matrix.
┌─────────────────────────────────────────────────────────────────┐
│ COMPETITIVE INTELLIGENCE │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone via web search) │
│ ✓ Competitor product deep-dive: features, pricing, positioning │
│ ✓ Recent releases: what they've shipped in last 90 days │
│ ✓ Your company releases: what you've shipped to counter │
│ ✓ Differentiation matrix: where you win vs. where they win │
│ ✓ Sales talk tracks: how to position against each competitor │
│ ✓ Landmine questions: expose their weaknesses naturally │
├─────────────────────────────────────────────────────────────────┤
│ OUTPUT: Interactive HTML Battlecard │
│ ✓ Comparison matrix overview │
│ ✓ Clickable tabs for each competitor │
│ ✓ Dark theme, professional styling │
│ ✓ Self-contained HTML file — share or host anywhere │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: Win/loss data, competitor mentions in closed deals │
│ + Docs: Existing battlecards, competitive playbooks │
│ + Chat: Internal intel, field reports from colleagues │
│ + Transcripts: Competitor mentions in customer calls │
└─────────────────────────────────────────────────────────────────┘
When you run this skill, I'll ask for context:
Required:
Optional:
If I already have your seller context from a previous session, I'll confirm and skip the questions.
| Connector | What It Adds | |-----------|--------------| | CRM | Win/loss history against each competitor, deal-level competitor tracking | | Docs | Existing battlecards, product comparison docs, competitive playbooks | | Chat | Internal chat intel (e.g. Slack) — what your team is hearing from the field | | Transcripts | Competitor mentions in customer calls, objections raised |
No connectors? Web research works great. I'll pull everything from public sources — product pages, pricing, blogs, release notes, reviews, job postings.
The skill generates a self-contained HTML file with:
Overview comparing you vs. all competitors at a glance:
Each competitor gets a clickable card that expands to show:
<!DOCTYPE html>
<html>
<head>
<title>Battlecard: [Your Company] vs Competitors</title>
<style>
/* Dark theme, professional styling */
/* Tabbed navigation */
/* Expandable cards */
/* Responsive design */
</style>
</head>
<body>
<!-- Header with your company + date -->
<header>
<h1>[Your Company] Competitive Battlecard</h1>
<p>Generated: [Date] | Competitors: [List]</p>
</header>
<!-- Tab Navigation -->
<nav class="tabs">
<button class="tab active" data-tab="matrix">Comparison Matrix</button>
<button class="tab" data-tab="competitor-1">[Competitor 1]</button>
<button class="tab" data-tab="competitor-2">[Competitor 2]</button>
<button class="tab" data-tab="competitor-3">[Competitor 3]</button>
</nav>
<!-- Comparison Matrix Tab -->
<section id="matrix" class="tab-content active">
<h2>Head-to-Head Comparison</h2>
<table class="comparison-matrix">
<!-- Feature rows with you vs each competitor -->
</table>
<h2>Quick Win/Loss Guide</h2>
<div class="win-loss-grid">
<!-- Per-competitor: when you win, when you lose -->
</div>
</section>
<!-- Individual Competitor Tabs -->
<section id="competitor-1" class="tab-content">
<div class="battlecard">
<div class="profile"><!-- Company info --></div>
<div class="differentiation"><!-- Where they win / you win --></div>
<div class="talk-tracks"><!-- Scenario-based positioning --></div>
<div class="objections"><!-- Common objections + responses --></div>
<div class="landmines"><!-- Questions to ask --></div>
</div>
</section>
<script>
// Tab switching logic
// Expand/collapse sections
</script>
</body>
</html>
:root {
/* Dark theme base */
--bg-primary: #0a0d14;
--bg-elevated: #0f131c;
--bg-surface: #161b28;
--bg-hover: #1e2536;
/* Text */
--text-primary: #ffffff;
--text-secondary: rgba(255, 255, 255, 0.7);
--text-muted: rgba(255, 255, 255, 0.5);
/* Accent (your brand or neutral) */
--accent: #3b82f6;
--accent-hover: #2563eb;
/* Status indicators */
--you-win: #10b981;
--they-win: #ef4444;
--tie: #f59e0b;
}
If first time:
1. Ask: "What company do you work for?"
2. Ask: "What do you sell? (product/service in one line)"
3. Ask: "Who are your main competitors? (up to 5)"
4. Store context for future sessions
If returning user:
1. Confirm: "Still at [Company] selling [Product]?"
2. Ask: "Same competitors, or any new ones to add?"
Web searches:
1. "[Your company] product" — current offerings
2. "[Your company] pricing" — pricing model
3. "[Your company] news" — recent announcements (90 days)
4. "[Your company] product updates OR changelog OR releases" — what you've shipped
5. "[Your company] vs [competitor]" — existing comparisons
For each competitor, run:
1. "[Competitor] product features" — what they offer
2. "[Competitor] pricing" — how they charge
3. "[Competitor] news" — recent announcements
4. "[Competitor] product updates OR changelog OR releases" — what they've shipped
5. "[Competitor] reviews G2 OR Capterra OR TrustRadius" — customer sentiment
6. "[Competitor] vs [alternatives]" — how they position
7. "[Competitor] customers" — who uses them
8. "[Competitor] careers" — hiring signals (growth areas)
If CRM connected:
1. Query closed-won deals with competitor field = [Competitor]
2. Query closed-lost deals with competitor field = [Competitor]
3. Extract win/loss patterns
If docs connected:
1. Search for "battlecard [competitor]"
2. Search for "competitive [competitor]"
3. Pull existing positioning docs
If chat connected:
1. Search for "[Competitor]" mentions (last 90 days)
2. Extract field intel and colleague insights
If transcripts connected:
1. Search calls for "[Competitor]" mentions
2. Extract objections and customer quotes
1. Structure data for each competitor
2. Build comparison matrix
3. Generate individual battlecards
4. Create talk tracks for each scenario
5. Compile landmine questions
6. Render as self-contained HTML
7. Save as [YourCompany]-battlecard-[date].html
competitor:
name: "[Name]"
website: "[URL]"
profile:
founded: "[Year]"
funding: "[Stage + amount]"
employees: "[Count]"
target_market: "[Who they sell to]"
pricing_model: "[Per seat / usage / etc.]"
market_position: "[Leader / Challenger / Niche]"
what_they_sell: "[Product summary]"
their_positioning: "[How they describe themselves]"
recent_releases:
- date: "[Date]"
release: "[Feature/Product]"
impact: "[Why it matters]"
where_they_win:
- area: "[Area]"
advantage: "[Their strength]"
how_to_handle: "[Your counter]"
where_you_win:
- area: "[Area]"
advantage: "[Your strength]"
proof_point: "[Evidence]"
pricing:
model: "[How they charge]"
entry_price: "[Starting price]"
enterprise: "[Enterprise pricing]"
hidden_costs: "[Implementation, etc.]"
talk_track: "[How to discuss pricing]"
talk_tracks:
early_mention: "[Strategy if they come up early]"
displacement: "[Strategy if customer uses them]"
late_addition: "[Strategy if added late to eval]"
objections:
- objection: "[What customer says]"
response: "[How to handle]"
landmines:
- "[Question that exposes their weakness]"
win_loss: # If CRM connected
win_rate: "[X]%"
common_win_factors: "[What predicts wins]"
common_loss_factors: "[What predicts losses]"
## ✓ Battlecard Created
[View your battlecard](file:///path/to/[YourCompany]-battlecard-[date].html)
---
**Summary**
- **Your Company**: [Name]
- **Competitors Analyzed**: [List]
- **Data Sources**: Web research [+ CRM] [+ Docs] [+ Transcripts]
---
**How to Use**
- **Before a call**: Open the relevant competitor tab, review talk tracks
- **During a call**: Reference landmine questions
- **After win/loss**: Update with new intel
---
**Sharing Options**
- **Local file**: Open in any browser
- **Host it**: Upload to Netlify, Vercel, or internal wiki
- **Share directly**: Send the HTML file to teammates
---
**Keep it Fresh**
Run this skill again to refresh with latest intel. Recommended: monthly or before major deals.
Competitive intel gets stale. Recommended refresh:
| Trigger | Action | |---------|--------| | Monthly | Quick refresh — new releases, news, pricing changes | | Before major deal | Deep refresh for specific competitor in that deal | | After win/loss | Update patterns with new data | | Competitor announcement | Immediate update on that competitor |
testing
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
tools
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
testing
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
development
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.