competitive-intelligence

Étoiles10

Forks1

Mis à jour5 juin 2026 à 16:11

Competitive intelligence and market positioning analysis for product and GTM decisions. Use for competitor landscape mapping, positioning gap identification, win/loss pattern synthesis, battlecard creation, market-sizing estimates (TAM/SAM/SOM), and differentiation analysis. Trigger phrases: "map the competitive landscape", "create a battlecard for", "analyse our win/loss patterns", "how do we differentiate from", "size this market". NOT for primary market research (customer interviews, surveys) — this skill works from existing public and internal data. NOT for financial modelling or investor decks — competitive context informs the story but this skill does not build financial projections. NOT for pricing strategy deep-dives — pricing has its own set of constraints and frameworks beyond competitive positioning.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

viktorbezdek

viktorbezdek/skillstack

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	competitive-intelligence
description	Competitive intelligence and market positioning analysis for product and GTM decisions. Use for competitor landscape mapping, positioning gap identification, win/loss pattern synthesis, battlecard creation, market-sizing estimates (TAM/SAM/SOM), and differentiation analysis. Trigger phrases: "map the competitive landscape", "create a battlecard for", "analyse our win/loss patterns", "how do we differentiate from", "size this market". NOT for primary market research (customer interviews, surveys) — this skill works from existing public and internal data. NOT for financial modelling or investor decks — competitive context informs the story but this skill does not build financial projections. NOT for pricing strategy deep-dives — pricing has its own set of constraints and frameworks beyond competitive positioning.
allowed-tools	Read,Write,Edit,Bash

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.

Plus depuis ce dépôt

même dépôt

cloud-infrastructure

viktorbezdek/skillstack

Cloud infrastructure design and infrastructure-as-code (IaC) authoring. Use for Terraform module authoring, AWS CDK constructs, cloud architecture design (VPCs, load balancers, managed services, serverless), multi-region and disaster-recovery patterns, cost-optimisation analysis, and IaC code review. Trigger phrases: "write Terraform for", "design the AWS architecture", "set up a VPC", "convert this to CDK", "optimise our cloud costs". NOT for application-layer code — this skill models infrastructure, not the code running on it. NOT for Kubernetes application manifests (Deployments, Services, Ingress) — those belong in a k8s-specific skill. NOT for CI/CD pipeline configuration — that is a deployment concern separate from infrastructure provisioning.

2026-06-0510

database-design

viktorbezdek/skillstack

Database design and schema engineering for relational databases. Use for SQL schema design, ORM model authoring, migration strategies (Alembic, Liquibase, Flyway, Drizzle), query optimisation, indexing decisions, normalisation vs denormalisation trade-offs, and data-integrity constraints. Trigger phrases: "design this schema", "write a migration", "optimise this query", "model these entities", "add an index". NOT for NoSQL/document stores — use a dedicated NoSQL skill for those. NOT for ETL pipelines or data warehousing at scale — those involve different trade-offs. NOT for ORM configuration (framework setup) — this skill is about DATA SHAPE, not connection pooling or ORM bootstrap.

2026-06-0510

email-marketing

viktorbezdek/skillstack

Email content writing for newsletters, drip sequences, onboarding flows, and transactional emails. Use for newsletter drafting, automated drip sequence copy, welcome email series, subject line and preview text optimisation, re-engagement emails, and plain-language transactional email (receipts, confirmations, alerts). Trigger phrases: "write a newsletter", "draft an onboarding email sequence", "write a subject line", "write a drip campaign", "create a welcome email". NOT for email infrastructure setup (ESP config, sending domains, DKIM/DMARC) — that is a technical ops concern. NOT for social media content — use the social-media-content skill for LinkedIn or Twitter. NOT for cold outreach / sales prospecting emails — those have compliance and conversion constraints beyond marketing content.

2026-06-0510

research-synthesis

viktorbezdek/skillstack

Structured research and evidence synthesis for knowledge-intensive tasks. Use for multi-source research coordination, evidence triangulation across conflicting sources, competing-hypothesis analysis, literature/documentation sweeps, claim verification, and synthesis reports. Trigger phrases: "research this topic", "synthesise findings from", "compare sources on", "what does the evidence say about", "triangulate these claims". NOT for primary data collection (interviews, surveys) — this skill synthesises existing sources. NOT for code research or codebase exploration — use CodeGraph and Semble for that. NOT for creative content generation — synthesis produces structured analysis, not narrative content.

2026-06-0510

security-engineering

viktorbezdek/skillstack

Application security design and threat-informed engineering. Use for authentication and authorisation architecture (OAuth2, JWT, RBAC, ABAC), OWASP Top 10 vulnerability analysis, secrets management (Vault, AWS Secrets Manager, environment isolation), input validation patterns, secure API design, SQL injection and XSS prevention, and security-aware code review. Trigger phrases: "secure this endpoint", "design an auth system", "review this for security vulnerabilities", "how do I store secrets", "implement RBAC". NOT for network/infrastructure security (firewalls, VPNs, WAF config) — those belong in cloud-infrastructure. NOT for compliance auditing (SOC2, GDPR gap assessments) — that requires a compliance specialist. NOT for penetration testing or red-teaming — this skill is for defensive engineering, not offensive exercises.

2026-06-0510

social-media-content

viktorbezdek/skillstack

Short-form social media content for LinkedIn, Twitter/X, and similar platforms. Use for LinkedIn post drafting, Twitter/X thread writing, hook-first content structures, platform-native tone calibration, hashtag strategy, and engagement-optimised formatting. Trigger phrases: "write a LinkedIn post", "draft a Twitter thread", "turn this into a thread", "write a social post about", "make this shareable". NOT for long-form blog articles or newsletters — use the storytelling or email-marketing skill for those. NOT for ad copy or paid social — those have conversion-optimisation constraints beyond organic content. NOT for content calendars or scheduling strategy — this skill writes the content, not the plan.

2026-06-0510

name	competitive-intelligence
description	Competitive intelligence and market positioning analysis for product and GTM decisions. Use for competitor landscape mapping, positioning gap identification, win/loss pattern synthesis, battlecard creation, market-sizing estimates (TAM/SAM/SOM), and differentiation analysis. Trigger phrases: "map the competitive landscape", "create a battlecard for", "analyse our win/loss patterns", "how do we differentiate from", "size this market". NOT for primary market research (customer interviews, surveys) — this skill works from existing public and internal data. NOT for financial modelling or investor decks — competitive context informs the story but this skill does not build financial projections. NOT for pricing strategy deep-dives — pricing has its own set of constraints and frameworks beyond competitive positioning.
allowed-tools	Read,Write,Edit,Bash

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

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.