competitor-tracking

Name: competitor-tracking
Author: jonathimer

82installs6forks

How to install competitor-tracking?

jonathimer/devmarketing-skills/competitor-tracking

$npx -y skills add jonathimer/devmarketing-skills --skill competitor-tracking

Installs into the current project.

Summary

Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: "competitor analysis", "track competitors", "competitive intelligence", "competitor research",

Files · 1

View on GitHub

SKILL.md

1	# Competitor Tracking
2
3	Systematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.
4
5	## Overview
6
7	Competitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding/trajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.
8
9	Effective competitor tracking helps you:
10	- Understand your competitive positioning
11	- Anticipate competitor moves
12	- Arm sales and marketing with accurate battlecards
13	- Identify market gaps and opportunities
14	- Learn from competitor successes and failures
15
16	## Competitor Identification
17
18	### Types of Competitors
19
20	Direct Competitors:
21	- Same category, same target developer
22	- Solve the same core problem
23	- Would appear in the same "best X tools" lists
24	- Example: If you're a CI/CD tool, other CI/CD tools
25
26	Indirect Competitors:
27	- Adjacent categories that overlap with your use case
28	- Might be expanding into your space
29	- Developers might use instead of your category
30	- Example: GitHub Actions competing with standalone CI tools
31
32	DIY Alternatives:
33	- Open source tools developers self-host
34	- Custom scripts and internal tooling
35	- "Just use bash scripts" or "build it yourself"
36	- Often your biggest competitor by volume
37
38	Platform Alternatives:
39	- Cloud provider native services (AWS, GCP, Azure equivalents)
40	- All-in-one platforms that include your functionality
41	- Enterprise suite solutions
42
43	### Competitive Landscape Mapping
44
45	Create a competitive landscape document with:
46
47	1. Competitor profiles - Company, product, target market, positioning
48	2. Feature matrix - Core features compared across competitors
49	3. Pricing comparison - Tiers, pricing model, enterprise pricing signals
50	4. Strengths/weaknesses - Honest assessment of each competitor
51	5. Trajectory - Funding, growth signals, strategic direction
52
53	## What to Track
54
55	### Product and Features
56
57	Track weekly/monthly:
58	- Changelog and release notes
59	- New feature announcements
60	- Pricing changes
61	- Integration announcements
62	- API changes
63	- SDK/library updates
64
65	How to track:
66	- Subscribe to competitor newsletters
67	- Follow their GitHub releases
68	- Monitor their Twitter/blog
69	- Set up monitoring alerts for "[competitor] launch" "[competitor] announces"
70
71	### Pricing and Packaging
72
73	Key signals:
74	- Pricing page changes (use archive.org to track history)
75	- New tier introductions
76	- Enterprise/custom pricing signals
77	- Free tier changes
78	- Usage-based vs seat-based shifts
79
80	Competitive pricing intelligence:
81	- What's included in free tier?
82	- Where are the upgrade triggers?
83	- How do they handle overages?
84	- What's the enterprise motion?
85
86	### Positioning and Messaging
87
88	Track changes in:
89	- Homepage headline and hero
90	- "Who it's for" positioning
91	- Primary use cases emphasized
92	- Comparison pages (how they position against others)
93	- Case studies and social proof
94
95	Analyze:
96	- What problem do they lead with?
97	- What audience are they targeting?
98	- What's their unique angle?
99	- How are they different from 6 months ago?
100
101	### Content Strategy
102
103	Monitor:
104	- Blog post frequency and topics
105	- Documentation quality and coverage
106	- Video/tutorial content
107	- Conference talks and sponsorships
108	- Developer education initiatives
109
110	Look for:
111	- SEO plays (what keywords are they targeting?)
112	- Content gaps you can exploit
113	- Successful content formats to learn from
114
115	### Community and Traction
116
117	GitHub signals:
118	- Stars/forks growth rate
119	- Issue volume and response time
120	- Contributor growth
121	- Release frequency
122
123	Community signals:
124	- Discord/Slack member counts
125	- Forum activity
126	- Stack Overflow tag activity
127	- Reddit mention frequency
128
129	## Developer Sentiment Monitoring
130
131	### Setting Up Competitor Monitoring
132
133	Use social listening tools to track developer sentiment toward competitors across platforms. Set up alerts for:
134
135	- Competitor brand mentions
136	- Negative sentiment toward competitors (opportunity signals)
137	- Comparison queries ("[competitor] vs")
138
139	### Key Sentiment Signals
140
141	Churn signals:
142	- "Migrating away from [competitor]"
143	- "Looking for [competitor] alternative"
144	- "Frustrated with [competitor]"
145	- "Canceling [competitor]"
146
147	Praise signals (learn from them):
148	- "Love [competitor]'s [feature]"
149	- "[Competitor] just works"
150	- "Best part of [competitor] is..."

People who liked this also viewed

6 picks

Type