skills/c-level-advisor/competitive-intel/SKILL.md
Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.
npx skillsauth add neekware/ehayeskills competitive-intelInstall 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.
Systematic competitor tracking. Not obsession — intelligence that drives real decisions.
competitive intelligence, competitor analysis, battlecard, win/loss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy
/ci:landscape — Map your competitive space (direct, indirect, future)
/ci:battlecard [name] — Build a sales battlecard for a specific competitor
/ci:winloss — Analyze recent wins and losses by reason
/ci:update [name] — Track what a competitor did recently
/ci:map — Build competitive positioning map
Direct competitors: Same ICP, same problem, comparable solution, similar price point. Indirect competitors: Same budget, different solution (including "do nothing" and "build in-house"). Future competitors: Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.
The 2x2 Threat Matrix:
| | Same ICP | Different ICP | | --------------------- | ----------------- | ---------------- | | Same problem | Direct threat | Adjacent (watch) | | Different problem | Displacement risk | Ignore for now |
Update this quarterly. Who's moved quadrants?
Track these 8 dimensions per competitor:
| Dimension | Sources | Cadence | | -------------------- | ------------------------------------------------- | --------- | | Product moves | Changelog, G2/Capterra reviews, Twitter/LinkedIn | Monthly | | Pricing changes | Pricing page, sales call intel, customer feedback | Triggered | | Funding | Crunchbase, TechCrunch, LinkedIn | Triggered | | Hiring signals | LinkedIn job postings, Indeed | Monthly | | Partnerships | Press releases, co-marketing | Triggered | | Customer wins | Case studies, review sites, LinkedIn | Monthly | | Customer losses | Win/loss interviews, churned accounts | Ongoing | | Messaging shifts | Homepage, ads (Facebook/Google Ad Library) | Quarterly |
SWOT per Competitor:
Competitive Positioning Map (2 axis): Choose axes that matter for your buyers:
Feature Gap Analysis: | Feature | You | Competitor A | Competitor B | Gap status | |---------|-----|-------------|-------------|------------| | [Feature] | ✅ | ✅ | ❌ | Your advantage | | [Feature] | ❌ | ✅ | ✅ | Gap — roadmap? | | [Feature] | ✅ | ❌ | ❌ | Moat | | [Feature] | ❌ | ❌ | ✅ | Competitor B only |
For Sales (CRO): Battlecards — one page per competitor, designed for pre-call prep.
See templates/battlecard-template.md
For Marketing (CMO): Positioning update — message shifts, new differentiators, claims to stop or start making.
For Product (CPO): Feature gap summary — what customers ask for that we don't have, what competitors ship, what to reprioritize.
For CEO/Board: Monthly competitive summary — 1-page: who moved, what it means, recommended responses.
Monthly (scheduled):
Triggered (event-based):
Quarterly:
This is the highest-signal competitive data you have. Most companies do it too rarely.
When to interview:
Who conducts it:
Question structure:
Aggregate findings monthly:
Signs you're over-tracking competitors:
Signs you're under-tracking:
The right posture:
| Audience | Format | Cadence | Owner | | ---------- | --------------------------- | ------------------- | ------- | | AEs + SDRs | Updated battlecards in CRM | Monthly + triggered | CRO | | Product | Feature gap analysis | Quarterly | CPO | | Marketing | Positioning brief | Quarterly | CMO | | Leadership | 1-page competitive summary | Monthly | CEO/COO | | Board | Competitive landscape slide | Quarterly | CEO |
One source of truth: All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.
| Signal | What it means | | ----------------------------------------------------- | -------------------------------------------------- | | Competitor's win rate >50% in your core segment | Fundamental positioning problem, not sales problem | | Same objection from 5+ deals: "competitor has X" | Feature gap that's real, not just optics | | Competitor hired 10 engineers in your domain | Major product investment incoming | | Competitor raised >$20M and targets your ICP | 12-month runway for them to compete hard | | Prospects evaluate you to justify competitor decision | You're the "check box" — fix perception or segment |
| Intelligence Type | Feeds To | Output Format | | -------------------- | --------- | ----------------------------------------- | | Product moves | CPO | Roadmap input, feature gap analysis | | Pricing changes | CRO, CFO | Pricing response recommendations | | Funding rounds | CEO, CFO | Strategic positioning update | | Hiring signals | CHRO, CTO | Talent market intelligence | | Customer wins/losses | CRO, CMO | Battlecard updates, positioning shifts | | Marketing campaigns | CMO | Counter-positioning, channel intelligence |
references/ci-playbook.md — OSINT sources, win/loss framework, positioning map constructiontemplates/battlecard-template.md — sales battlecard templatetools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski