Competitive Intelligence
>-
Install
$ agentstack add skill-viktorbezdek-skillstack-competitive-intelligence ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-viktorbezdek-skillstack-competitive-intelligence) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
competitive-intelligence
Competitor analysis, market sizing, positioning maps, win/loss pattern synthesis, and battlecard creation for product and GTM decisions.
When to use
- Map the competitive landscape for AI code assistants (GitHub Copilot, Cursor, etc.)
- Create a battlecard for our sales team competing against Datadog
- Analyse our last 50 win/loss notes — what patterns do you see?
- How should we position against a competitor that's 10x larger?
- Estimate the TAM for developer productivity tools in enterprise
- What are the defensible moats in the observability market?
- Identify the positioning gaps in the MLOps tool landscape
- Compare our feature set against three competitors in a matrix
When NOT to use
- Run customer interviews to validate our positioning hypothesis — Primary research — not CI synthesis
- Build a three-year financial model for our go-to-market plan — Financial modelling — out of scope
- Design our pricing tiers and annual contract structure — Pricing strategy — separate concern
- Write a press release about our product launch — Comms/PR — not competitive intelligence
Anti-patterns
Symptom
Invoking this skill for tasks outside its scope — e.g., infrastructure concerns when the request is about application code, or vice versa.
Problem
Scope mismatch wastes context and produces advice tuned for the wrong domain. A database schema skill answering a connection-pooling question gives schema advice when the real problem is operational configuration.
Solution
Read the NOT for clauses carefully. If the request matches an exclusion, identify the correct skill (check SkillStack for the right domain) rather than stretching this skill to cover adjacent ground.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: viktorbezdek
- Source: viktorbezdek/skillstack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.