Agent skill

Afrexai Competitive Intel

by LeoYeAI in LeoYeAI/openclaw-master-skills

Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring.

MITAuto-check passedSales & Support

Install Afrexai Competitive Intel

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-competitive-intel -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-competitive-intel --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/afrexai-competitive-intel .claude/skills/afrexai-competitive-intel && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
afrexai-competitive-intel
GitHub stars
2.2k
Token cost
~4.7k tokens
SKILL.md length
1,163 words
Files
3
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring.

  • Works in 7 steps: Market Mapping → Product Teardown → Pricing Intelligence → …
  • Tasks that involve Competitor analysis
  • SKILL.md covers When to Use, Phase 1: Market Mapping, Phase 2: Product Teardown and Phase 3: Pricing Intelligence, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Afrexai Competitive Intel is an agent skill from LeoYeAI/openclaw-master-skills. Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring. Goes far beyond SEO to cover the full business landscape.

Its SKILL.md is about 4.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `_meta.json`).

It sits in Sales & Support, covering Competitor analysis and Sales enablement. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Tasks that involve Competitor analysis
  • Tasks that involve Sales enablement

Example prompts

  • “/afrexai-competitive-intel”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Market Mapping
  2. Product Teardown
  3. Pricing Intelligence
  4. Sales Battlecards
  5. Win/Loss Analysis
  6. Ongoing Monitoring
  7. Strategic Frameworks

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Afrexai Competitive Intel loads about 4.7k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,163 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,163 words, ~4,700 tokens.

Download SKILL.mdSave it as .claude/skills/afrexai-competitive-intel/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
afrexai-competitive-intel
description
Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring. Goes far beyond SEO to cover the full business landscape.

Competitive Intelligence Engine

A complete system for understanding, tracking, and outmaneuvering competitors. Covers market mapping, product analysis, pricing intelligence, sales battlecards, win/loss analysis, and ongoing monitoring.

When to Use

  • Entering a new market or launching a product
  • Losing deals to competitors and need to understand why
  • Quarterly strategy reviews
  • Pricing decisions (new product or adjustment)
  • Sales team needs competitive talking points
  • M&A due diligence on a target or acquirer
  • Investor pitch prep (show you understand the landscape)
  • Content strategy informed by competitor gaps

Phase 1: Market Mapping

1.1 Competitor Identification

Classify every competitor into one of four tiers:

TierDefinitionExampleMonitoring Frequency
DirectSame product, same buyerYour closest rivalsWeekly
AdjacentDifferent product, overlapping buyerPlatform expanding into your spaceBi-weekly
IndirectDifferent solution to same problemSpreadsheets replacing your SaaSMonthly
EmergingEarly-stage, same visionYC startups in your categoryMonthly
Discovery Methods

Search these sources systematically:

  1. Google: "[your category] software/tool/service" — note top 10 organic + ads
  2. G2/Capterra/TrustRadius: Your category page — note top 10 by reviews
  3. Product Hunt: Search your keywords — sort by votes
  4. Crunchbase: Search your category — filter funded companies
  5. LinkedIn: "[competitor name]" company pages — note employee count trends
  6. Reddit/HN: "alternative to [leader]" or "[category] recommendations"
  7. Customer interviews: "Who else did you evaluate?"
  8. Lost deal notes: Who did you lose to and why?
Market Map YAML
yaml
market_map:
  category: "[Your Category]"
  date: "YYYY-MM-DD"
  total_addressable_market: "$XB"
  
  competitors:
    - name: "Competitor A"
      tier: "direct"
      website: "https://..."
      founded: 2019
      funding: "$50M Series B"
      estimated_revenue: "$10-20M ARR"
      employee_count: 150
      employee_trend: "growing"  # growing | stable | shrinking
      hq: "San Francisco, CA"
      key_customers: ["Customer 1", "Customer 2"]
      primary_market: "mid-market"  # smb | mid-market | enterprise
      positioning: "All-in-one platform for X"
      strengths: ["Feature A", "Strong brand"]
      weaknesses: ["Expensive", "Slow support"]
      threat_level: "high"  # low | medium | high | critical
      notes: ""

Phase 2: Product Teardown

2.1 Feature Matrix

For each direct competitor, build a feature comparison:

yaml
feature_matrix:
  last_updated: "YYYY-MM-DD"
  
  categories:
    - name: "Core Features"
      features:
        - name: "Feature X"
          us: "full"       # none | partial | full | superior
          competitor_a: "full"
          competitor_b: "partial"
          weight: 5        # 1-5 importance to buyer
          notes: "We have deeper customization"
          
        - name: "Feature Y"
          us: "none"
          competitor_a: "full"
          competitor_b: "full"
          weight: 3
          notes: "On our roadmap for Q3"
    
    - name: "Integrations"
      features:
        - name: "Salesforce"
          us: "full"
          competitor_a: "partial"
          weight: 4
2.2 Product Teardown Template

For each major competitor, conduct a structured teardown:

markdown
## [Competitor Name] Product Teardown
**Date:** YYYY-MM-DD
**Analyst:** [name]

### First Impressions (0-5 min)
- Homepage messaging: What problem do they lead with?
- Sign-up friction: How many steps? What info required?
- Time to value: How fast can you DO something?
- Design quality: Modern, dated, cluttered, clean?

### Onboarding (5-30 min)
- Guided tour? Checklist? Video? Nothing?
- Sample data provided? Sandbox mode?
- How quickly did you feel competent?
- What confused you?

### Core Workflow
- Complete their primary use case end-to-end
- Note: steps required, clicks per task, speed, error handling
- Screenshot key screens

### Differentiators
- What can they do that we can't? (be honest)
- What's their "magic moment"?
- What do their happiest customers praise? (check G2 reviews)

### Weaknesses
- Where did you get stuck?
- What felt missing or half-baked?
- What do their angriest customers complain about? (check G2 1-2 star reviews)

### Pricing vs Value
- What plan would a typical customer need?
- Price per user/month at that tier?
- Any hidden costs (implementation, support, integrations)?
- Free trial? Freemium? Money-back guarantee?

### Technical Assessment
- Stack: (check Wappalyzer, BuiltWith, job postings)
- API: Public? REST/GraphQL? Rate limits? Docs quality?
- Mobile: Native app? Responsive web? PWA?
- Performance: Page load speed, UI responsiveness
- Uptime: Status page? Historical incidents?
2.3 UX Scoring Rubric

Score each competitor's product (0-10 per dimension):

DimensionWhat to EvaluateWeight
Ease of SetupTime to first value, onboarding friction15%
Core UXPrimary workflow efficiency, intuitiveness25%
Feature DepthCovers edge cases, power user needs20%
ReliabilityUptime, bugs encountered, error handling15%
IntegrationsEcosystem breadth, API quality10%
SupportResponse time, quality, self-serve resources10%
MobileNative quality, feature parity5%

Total = weighted sum. Compare across competitors.


Phase 3: Pricing Intelligence

3.1 Pricing Comparison Table
yaml
pricing_intel:
  date: "YYYY-MM-DD"
  
  competitors:
    - name: "Us"
      model: "per-seat"  # per-seat | usage | flat | hybrid | freemium
      entry_price: "$29/user/mo"
      mid_price: "$79/user/mo"
      enterprise_price: "Custom"
      free_tier: true
      free_limits: "5 users, 1000 records"
      annual_discount: "20%"
      contract_required: false
      implementation_fee: "$0"
      hidden_costs: []
      
    - name: "Competitor A"
      model: "per-seat"
      entry_price: "$49/user/mo"
      mid_price: "$99/user/mo"
      enterprise_price: "Custom ($150+/user)"
      free_tier: false
      annual_discount: "15%"
      contract_required: true  # annual minimum
      implementation_fee: "$5,000"
      hidden_costs: ["API access on enterprise only", "SSO $50/user extra"]
3.2 Price Positioning Analysis

Answer these questions:

  1. Where do we sit? Map all competitors on a 2x2: Price (low→high) vs Feature depth (basic→advanced)
  2. Who's cheapest? At 10 users? 50 users? 200 users? (pricing often crosses over at scale)
  3. Total Cost of Ownership: Include implementation, training, migration, hidden fees
  4. Value ratio: Features-per-dollar compared to each competitor
  5. Pricing trend: Are competitors raising prices? (check Wayback Machine on /pricing)
  6. Discount behavior: Do they discount aggressively in deals? (ask sales team, check G2 reviews mentioning price)
3.3 Pricing Strategy Recommendations

Based on analysis, recommend one of:

StrategyWhen to UseRisk
PremiumClearly superior product + brandLosing price-sensitive deals
ParitySimilar product, compete on other axesRace to bottom
PenetrationNew entrant, need market share fastPerception of low quality
ValueBetter product at lower priceMargin pressure if costs rise
NicheSpecialized for segment competitors ignoreSmall TAM

Phase 4: Sales Battlecards

4.1 Battlecard Template

Create one per direct competitor:

markdown
# 🏆 Battlecard: Us vs [Competitor]
**Last Updated:** YYYY-MM-DD | **Confidence:** High/Medium/Low

## Quick Stats
| Metric | Us | Them |
|--------|-----|------|
| Founded | | |
| Funding | | |
| Est. Revenue | | |
| Employees | | |
| G2 Rating | | |
| Gartner Position | | |

## Their Pitch (in their words)
"[Their homepage headline or elevator pitch]"

## Why Customers Choose Us Over Them
1. **[Reason 1]**: [Specific proof point — customer quote, metric, demo moment]
2. **[Reason 2]**: [Specific proof point]
3. **[Reason 3]**: [Specific proof point]

## Why Customers Choose Them Over Us (be honest)
1. **[Reason 1]**: [And how to counter it]
2. **[Reason 2]**: [And how to counter it]

## Landmines to Plant 🧨
Questions to ask the prospect that expose competitor weaknesses:
1. "Ask them how they handle [weakness area] — you'll find it requires [workaround]"
2. "Request a demo of [specific feature] — it's not as deep as it looks"
3. "Ask about [hidden cost] — it's not on the pricing page"

## Objection Handling

**"[Competitor] is cheaper"**
> Response: "At first glance, yes. But when you factor in [hidden cost 1], [hidden cost 2], and [limitation requiring workaround], the total cost is actually [higher/comparable]. Plus, [our unique value] saves you [X hours/dollars] per [period]."

**"[Competitor] has [feature we lack]"**
> Response: "[Acknowledge honestly]. Here's why our customers find that [our approach] actually works better for [their use case]: [specific reasoning]. [Customer name] evaluated both and chose us specifically because [reason]."

**"We're already using [Competitor]"**
> Response: "That makes sense — they're solid at [genuine strength]. The customers who switch to us typically hit a wall with [specific limitation]. Are you experiencing [common pain point with that competitor]?"

## Trap Plays (When to Walk Away)
- If prospect needs [specific capability we truly lack], acknowledge it honestly
- If they're deeply embedded in [competitor ecosystem], switching cost may be too high
- If deal size is below $[X], cost of competing isn't worth it

## Win Stories
- **[Customer A]**: Switched from [Competitor] because [reason]. Result: [metric improvement]
- **[Customer B]**: Evaluated both, chose us because [reason]. Quote: "[testimonial]"

## Recent Intel
- [Date]: [Competitor] announced [product change/funding/hire]
- [Date]: [Customer feedback about competitor]
4.2 Quick Objection Matrix

For the sales team's daily use:

ObjectionShort ResponseProof Point
"Too expensive"[Value reframe][ROI stat or customer quote]
"Never heard of you"[Social proof][Customer logos, G2 rank]
"Missing [feature]"[Alternative or roadmap][Workaround or timeline]
"Happy with current tool"[Trigger question][Common pain with incumbent]
"Need enterprise features"[What we have][Enterprise customer reference]

Phase 5: Win/Loss Analysis

5.1 Win/Loss Interview Framework

After every significant deal (won or lost), capture:

yaml
win_loss:
  deal: "[Company Name]"
  date: "YYYY-MM-DD"
  outcome: "won"  # won | lost | no-decision
  deal_size: "$X ARR"
  sales_cycle_days: 45
  competitors_evaluated: ["Competitor A", "Competitor B"]
  
  decision_factors:
    - factor: "Ease of use"
      importance: 5  # 1-5
      our_score: 4   # 1-5
      winner_score: 3
      notes: "Demo experience was decisive"
      
    - factor: "Price"
      importance: 4
      our_score: 3
      winner_score: 4
      notes: "We were 20% more expensive but justified by ROI"
      
    - factor: "Integration with Salesforce"
      importance: 5
      our_score: 5
      winner_score: 2
      notes: "They required middleware; we're native"
  
  champion: "VP of Sales"
  decision_maker: "CRO"
  buying_trigger: "Previous tool couldn't scale past 50 users"
  
  key_quote: "Your Salesforce integration sealed the deal"
  
  lessons:
    - "Lead with integration story for Salesforce-heavy orgs"
    - "ROI calculator was critical for justifying premium price"
5.2 Win/Loss Trend Dashboard

Track quarterly:

markdown
## Q[X] Win/Loss Summary

### Win Rate by Competitor
| Competitor | Wins | Losses | Win Rate | Trend |
|-----------|------|--------|----------|-------|
| Competitor A | 12 | 8 | 60% | ↑ (was 50%) |
| Competitor B | 5 | 15 | 25% | ↓ (was 35%) |
| No competition | 20 | 3 | 87% | → |

### Top Win Reasons (ranked by frequency)
1. Ease of use (mentioned in 65% of wins)
2. Integration depth (55%)
3. Customer support (40%)

### Top Loss Reasons (ranked by frequency)
1. Price (mentioned in 70% of losses)
2. Missing [specific feature] (45%)
3. Incumbent relationship (30%)

### Action Items from This Quarter's Losses
1. [Feature gap] → Product team building for Q[X+1]
2. [Price objection] → New ROI calculator + case study
3. [Competitor strength] → Invest in [counter-strategy]

Phase 6: Ongoing Monitoring

6.1 Competitor Signal Tracking

Set up monitoring for each direct competitor:

SignalSourceFrequencyWhat to Look For
Product changesTheir changelog/blogWeeklyNew features, deprecations
Pricing changes/pricing page + WaybackMonthlyPrice increases, new tiers, model changes
HiringLinkedIn JobsBi-weeklyEngineering surge = new product. Sales surge = growth push
FundingCrunchbase, TechCrunchAs it happensNew round = aggressive expansion coming
LeadershipLinkedIn, pressAs it happensNew CEO/CRO = strategy shift likely
ReviewsG2, CapterraMonthlySentiment shifts, recurring complaints
ContentTheir blog, socialWeeklyMessaging changes, new positioning
CustomersPress releases, case studiesMonthlyLogos gained, industries targeted
CommunityReddit, HN, TwitterWeeklyComplaints, praise, feature requests
6.2 Weekly Intel Brief Template
markdown
## Competitive Intel Brief — Week of [Date]

### 🔴 Critical (action needed)
- [Competitor X] launched [feature] that directly competes with our [feature]
  - Impact: [assessment]
  - Recommended response: [action]

### 🟡 Notable (monitor)
- [Competitor Y] raised Series C ($40M) — expect aggressive hiring/marketing
- [Competitor Z] changed pricing model from per-seat to usage-based

### 🟢 Informational
- [Competitor X] published blog post about [topic]
- [Competitor Y] hiring 3 new enterprise AEs in EMEA

### Win/Loss This Week
- Won [Deal] vs [Competitor] — reason: [X]
- Lost [Deal] to [Competitor] — reason: [X]
Show full SKILL.md (464 more words)Show less
6.3 Quarterly Competitive Review Agenda
  1. Market map update (15 min): Any new entrants? Any exits? Tier changes?
  2. Feature gap review (20 min): What did competitors ship? What should we respond to?
  3. Win/loss trends (15 min): Are we gaining or losing ground? Against whom?
  4. Pricing check (10 min): Any pricing changes? Is our positioning still right?
  5. Battlecard refresh (15 min): Update all active battlecards
  6. Strategic decisions (15 min): Based on all intel, what should we invest in / deprioritize?

Phase 7: Strategic Frameworks

7.1 Competitive Moat Assessment

Rate your moat and each competitor's (1-5):

Moat TypeDescriptionUsComp AComp B
Network EffectsProduct gets better with more users
Switching CostsPain of leaving increases over time
Data AdvantageProprietary data that improves product
BrandTrust, recognition, preference
Scale EconomiesCost advantages from size
RegulatoryLicenses, certifications, compliance
TechnologyPatents, proprietary tech, speed
EcosystemIntegrations, partnerships, marketplace

Total moat score = sum. Higher = harder to displace.

7.2 Competitor Response Prediction

For each major competitor move, predict their likely response to YOUR moves:

markdown
**If we [action]...**
- Competitor A will likely: [response] because [reasoning]
- Competitor B will likely: [response] because [reasoning]
- Timeline: [how fast they'll respond]
- Our counter-move: [what we do next]
7.3 Blue Ocean Opportunities

After mapping all competitors, look for:

  1. Underserved segments: Customer types everyone ignores (too small? too niche? too complex?)
  2. Unmet needs: Features/capabilities no one offers that customers actually want
  3. Experience gaps: The workflow everyone does poorly
  4. Business model innovation: Could you win by charging differently? (usage vs seat vs outcome-based)
  5. Channel gaps: Where are customers NOT being reached? (vertical communities, specific geographies, languages)

Edge Cases & Advanced Techniques

Stealth Competitors
  • Monitor patent filings in your space (Google Patents)
  • Watch YC/Techstars demo days for category entrants
  • Track job postings at big tech for [your category] keywords — could signal internal build
International Competitors
  • Search in target language for your category
  • Check local review sites (Capterra has country-specific)
  • Different markets have different leaders — map per region
Platform Risk
  • If you build on a platform (Salesforce, Shopify, etc.), monitor the platform itself
  • Platforms often build features that commoditize plugins
  • Track platform's acquisition history in your space
Competitor Intelligence Ethics
  • ✅ Public information (websites, press, job postings, reviews, patents)
  • ✅ Customer feedback about competitors (win/loss interviews)
  • ✅ Product trials and demos (sign up normally)
  • ❌ Fake identities to access gated content
  • ❌ Poaching employees for intel
  • ❌ Accessing confidential documents
  • ❌ Reverse engineering protected code

Natural Language Commands

CommandWhat It Does
"Map my competitive landscape"Full Phase 1 market mapping
"Tear down [competitor]"Product teardown (Phase 2)
"Compare pricing with [competitors]"Pricing intelligence (Phase 3)
"Build battlecard for [competitor]"Sales battlecard (Phase 4)
"Analyze our win/loss data"Win/loss patterns (Phase 5)
"Weekly competitive brief"Monitoring summary (Phase 6)
"Assess our competitive moat"Strategic analysis (Phase 7)
"Find blue ocean opportunities"Gap analysis (Phase 7.3)
"How should we respond to [competitor move]?"Response prediction (Phase 7.2)
"Full competitive review"All phases, comprehensive output

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/afrexai-competitive-intel of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Afrexai Competitive Intel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Afrexai Competitive Intel compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Afrexai Competitive Intel this skillLeoYeAI/openclaw-master-skills2.2k—~4.7kAutomated safety check: PassMIT
Sales Enablement Kitaaron-he-zhu/aaron-marketing-skills2.9k—~3.3kAutomated safety check: PassApache-2.0
Battlecardsgrowthack88/growth-marketing-os116—~2.4kAutomated safety check: PassMIT
Competitive Battlecardphuryn/pm-skills27k—~721Automated safety check: PassMIT
Battlecard Generatorgooseworks-ai/goose-skills1.2k1 repos~2.3kAutomated safety check: PassMIT
Gtm Competitive Battlecard Writercriptogus/agent-evolve-network288—~551Automated safety check: PassCC-BY-SA-4.0

Similar skills

  • Sales Enablement Kit

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch…

    2.9k GitHub stars~3.3k tokensUpdated today
    Sales & SupportAuto-check passed
  • Battlecards

    growthack88/growth-marketing-os

    Creates competitive battlecards for sales deal conversations.

    116 GitHub stars~2.4k tokensUpdated 8 days ago
    Sales & SupportAuto-check passed
  • Competitive Battlecard

    phuryn/pm-skills

    Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns.

    27k GitHub stars~721 tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Battlecard Generator

    gooseworks-ai/goose-skills

    Research a specific competitor across their website, reviews, ads, social presence, and pricing — then produce a structured sales battlecard with positioning traps, objection handlers, landmine…

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Sales & SupportAuto-check passed
  • Gtm Competitive Battlecard Writer

    criptogus/agent-evolve-network

    Writes seller-ready battlecards: positioning, traps, landmines, objection handling, and proof points.

    288 GitHub stars~551 tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Competitive Intelligence

    w95/awesome-claude-corporate-skills

    Research your competitors and build an interactive battlecard.

    244 GitHub stars~3.1k tokensUpdated 7 mo ago
    Sales & SupportAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Afrexai Competitive Intel

What does Afrexai Competitive Intel do?

Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring. Afrexai Competitive Intel is an agent skill from LeoYeAI/openclaw-master-skills. Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring.

When should I use Afrexai Competitive Intel?

Afrexai Competitive Intel fits situations like: tasks that involve Competitor analysis; tasks that involve Sales enablement.

How do I install Afrexai Competitive Intel in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-competitive-intel -a claude-code`. Or copy the skill folder (skills/afrexai-competitive-intel in LeoYeAI/openclaw-master-skills) into .claude/skills/afrexai-competitive-intel in your project. Claude Code loads it when a task matches its description.

How do I install Afrexai Competitive Intel in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-competitive-intel -a codex`. Or copy the skill folder (skills/afrexai-competitive-intel in LeoYeAI/openclaw-master-skills) into .agents/skills/afrexai-competitive-intel in your project. Codex loads it when a task matches its description.

Can I use Afrexai Competitive Intel in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-competitive-intel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/afrexai-competitive-intel, .gemini/skills/afrexai-competitive-intel, .github/skills/afrexai-competitive-intel and .opencode/skills/afrexai-competitive-intel in your project.

What does Afrexai Competitive Intel need to run?

SKILL.md names no scripts, command-line tools or credentials: Afrexai Competitive Intel is instructions for the agent only.

Does Afrexai Competitive Intel access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Afrexai Competitive Intel safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Afrexai Competitive Intel use?

Afrexai Competitive Intel is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Afrexai Competitive Intel use?

About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Afrexai Competitive Intel?

Skills that share tags, products or a category with Afrexai Competitive Intel: Sales Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Battlecards (growthack88/growth-marketing-os, 116 stars), Competitive Battlecard (phuryn/pm-skills, 27k stars) and Battlecard Generator (gooseworks-ai/goose-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Afrexai Competitive Intel?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.