agent-launcher-orchest…
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use for competitor analysis, battlecards, win/loss review or positioning against alternatives. Builds a tracking system that feeds positioning, sales and roadmap.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill competitive-intel --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill competitive-intel -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill competitive-intel -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill competitive-intel -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill competitive-intel -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill competitive-intel -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill competitive-intel -a windsurf -y
name: "competitive-intel" description: "Use for competitor analysis, battlecards, win/loss review or positioning against alternatives. Builds a tracking system that feeds positioning, sales and roadmap." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: competitive-strategy updated: 2026-03-05 frameworks: ci-playbook, battlecard-template
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
Ask in natural language for the deliverable you need:
> "Map our competitive landscape" — direct, indirect, and future competitors > "Build a battlecard for [competitor]" — sales-ready battlecard > "Run a win/loss analysis" — recent wins and losses by reason > "What did [competitor] do recently?" — competitor update tracking > "Build a competitive positioning map" — 2x2 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:** 1. "Walk me through your evaluation process" 2. "Who else were you considering?" 3. "What were the top 3 criteria in your decision?" 4. "Where did [our product] fall short?" 5. "What was the deciding factor?" 6. "What would have changed your decision?"
**Aggregate findings monthly:**
---
**Signs you're over-tracking competitors:**
**Signs you're under-tracking:**
411 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when a launched managed agent needs grading against a rubric and improving ('grade my agent', 'is it good enough'). Builds…
Use when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and…
Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates…
Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads…
Use when closing out a launched managed agent ('wrap up', 'what do I own now'). Inventories primitives with…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…