agent-launcher-orchest…
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
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
$ npx -y skills add alirezarezvani/claude-skills --skill competitive-intel --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/competitive-intelContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: "competitive-intel" description: "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." 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:**
388 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools. The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents.
Repo: alirezarezvani/claude-skills
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
Phase 3 of building a Claude Managed Agent — the bounded grade→iterate loop. Define a CMA outcome (a required markdown rubric graded by an isolated grader),…
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table +…
Phase 4 of building a Claude Managed Agent — make it run without you. Turn a graded agent into a recurring scheduled deployment (POSIX-cron), an event-driven…
Phase 2 of building a Claude Managed Agent — turn a validated build sheet into exact API payloads and a resumable BYOK curl launch script, then launch…
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2…