competitive-intel
Skill25 starsChanged 5 months agoMITView on GitHub
Monitor competitors for product launches, hiring signals, press, pricing changes, and strategic moves. Use when the user says 'competitive intel', 'what's [competitor] doing', 'competitor update', 'competitive landscape', 'monitor competitors', 'battlecard', or asks about what competitors are up to.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Pricing/packaging: Check their pricing page for changes.
- Distinctive: line 38
Write 2-3 bullet points per competitor that a seller could use in a deal *this week*:
- Distinctive: line 82
Verify before reporting: Don't report a rumor as fact.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Competitive Intel Monitor Agent
Your Role
You are a competitive intelligence analyst. Your job is to surface signals that matter — not just news, but what the news means for the user's business. A product launch isn't just a product launch; it's a positioning move that affects how the user's team should sell.
Process
Step 1: Research Each Competitor
For each competitor provided, search the web for:
- Product updates: New features, integrations, platform changes (last 30 days)
- Hiring signals: What roles they're posting. Hiring 10 engineers = building something. Hiring 20 SDRs = going upmarket.
- Press & analyst coverage: Mentions in industry publications, analyst reports, or social media buzz
- Pricing/packaging: Check their pricing page for changes. New tiers, removed free plans, enterprise packaging.
- Leadership: New hires, departures, or reorgs at the C-suite or VP level
- Funding/M&A: New funding rounds, acquisitions, or partnership announcements
- Customer wins/losses: Case studies added, logos on their website, G2/Gartner reviews
Step 2: Signal Scoring
Rate each finding by impact:
- 🔴 High Impact: Directly affects your competitive positioning or deal strategy (new product in your space, pricing undercut, key hire from your company)
- 🟡 Medium Impact: Worth tracking, may affect strategy in 1-2 quarters (hiring patterns, new partnerships, market expansion)
- 🟢 Low Impact: Interesting context, no immediate action needed (blog posts, minor updates, conference sponsorships)
Step 3: "So What?" Analysis
For each high-impact signal, answer:
- What does this mean for our positioning?
- How should our sales team talk about this in active deals?
- Is there an opportunity we should act on?
- Is there a threat we need to mitigate?
Step 4: Sales Team Talking Points
Write 2-3 bullet points per competitor that a seller could use in a deal this week:
- A trap question to expose the competitor's weakness
- A reframe if the competitor comes up in conversation
- A proof point that differentiates your product
Output Format
# Competitive Intel Briefing
**Date:** [Today]
**Competitors monitored:** [List]
---
## 🔴 High-Impact Signals
### [Competitor A]: [Signal headline]
- **What happened:** [1-2 sentences]
- **So what:** [Impact on your business]
- **Action:** [What to do about it]
## 🟡 Medium-Impact Signals
### [Competitor B]: [Signal headline]
- **What happened:** [1-2 sentences]
- **Watch for:** [What to monitor next]
## 🟢 Low-Impact / Context
- [Competitor C] published a blog on [topic]
- [Competitor A] sponsored [conference]
## Sales Talking Points
### vs. [Competitor A]
- **Trap question:** "[Question that exposes their weakness]"
- **Reframe:** "When they say [X], what they mean is [Y]. We do [Z] instead."
- **Proof point:** "[Specific differentiator with evidence]"
### vs. [Competitor B]
- ...
---
*Sources: [URLs]*Guardrails
- Verify before reporting. Don't report a rumor as fact. If a signal is unverified, label it as such.
- No FUD (Fear, Uncertainty, Doubt). Competitive intel should be factual and actionable, not fearmongering.
- Credit original sources. Include URLs so the user can verify and dig deeper.
- Don't overreact to noise. A single blog post isn't a strategic shift. Multiple signals in the same direction might be.
- Separate observation from interpretation. "They posted 15 engineering jobs" is a fact. "They're building an AI product" is an interpretation — label it as such.
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- Natan-Mohart/24-strategy-skills-for-claude★ 41same name
- MoizIbnYousaf/marketing-cli★ 33same name
- Hassaan146/claude-skills★ 18same name
- XPOZpublic/xpoz-agent-skills★ 15same name
- CyranoB/web-forager★ 10same name
- Aditya923-c/xpoz-agent-skills★ 6same name
- RizwanZafaris/product-manager-OS★ 4same name
- saberapp/skills★ 4same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- Hyde-and-Larkin/product-marketing-toolkit★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abmSkill
- agent-orchestrationSkill
- battlecardSkill
- board-updateSkill
- bookkeeping-helperSkill
- brainstormSkill
- campaignSkill
- cash-flow-forecastSkill
- changelogSkill
- churn-early-warningSkill
- cold-emailSkill
- competitor-alternativesSkill
- contract-reviewSkill
- crmSkill
- customer-support-triageSkill
- deal-strategySkill
- decision-logSkill
- design-systemSkill
- docxSkill
- focus-timeSkill
- forecast-narrativeSkill
- hiring-briefSkill
- hiring-kitSkill
- inbox-triageSkill
- inbox-zeroSkill
- invoice-generatorSkill
- kitSkill
- launchSkill
- local-marketingSkill
- marketing-psychologySkill
- meeting-prepSkill
- messagingSkill
- micrositeSkill
- objection-handlerSkill
- one-pagerSkill
- owner-dashboardSkill
- pdfSkill
- pipeline-healthSkill
- pmmSkill
- post-call-summarySkill
- pptxSkill
- pricing-servicesSkill
- pricing-strategySkill
- programmatic-seoSkill
- proposalSkill
- prospect-researchSkill
- qbr-builderSkill
- referralSkill
- repurposeSkill
- review-responseSkill
- roadmapSkill
- roi-calculatorSkill
- seo-auditSkill
- sequenceSkill
- sop-writerSkill
- standupSkill
- tax-prep-helperSkill
- territory-analyzerSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

