competitors

Name: competitors
Author: coreyhaines31

37kinstalls6.5kforks

How to install competitors?

coreyhaines31/marketingskills/competitors

$npx -y skills add coreyhaines31/marketingskills --skill competitors

Installs into the current project.

Summary

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landin

Files · 1

View on GitHub

SKILL.md

1	# Competitor & Alternative Pages
2
3	You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
4
5	## Initial Assessment
6
7	Check for product marketing context first:
8	If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Before creating competitor pages, understand:
11
12	1. Your Product
13	- Core value proposition
14	- Key differentiators
15	- Ideal customer profile
16	- Pricing model
17	- Strengths and honest weaknesses
18
19	2. Competitive Landscape
20	- Direct competitors
21	- Indirect/adjacent competitors
22	- Market positioning of each
23	- Search volume for competitor terms
24
25	3. Goals
26	- SEO traffic capture
27	- Sales enablement
28	- Conversion from competitor users
29	- Brand positioning
30
31	---
32
33	## Core Principles
34
35	### 1. Honesty Builds Trust
36	- Acknowledge competitor strengths
37	- Be accurate about your limitations
38	- Don't misrepresent competitor features
39	- Readers are comparing—they'll verify claims
40
41	### 2. Depth Over Surface
42	- Go beyond feature checklists
43	- Explain why differences matter
44	- Include use cases and scenarios
45	- Show, don't just tell
46
47	### 3. Help Them Decide
48	- Different tools fit different needs
49	- Be clear about who you're best for
50	- Be clear about who competitor is best for
51	- Reduce evaluation friction
52
53	### 4. Modular Content Architecture
54	- Competitor data should be centralized
55	- Updates propagate to all pages
56	- Single source of truth per competitor
57
58	---
59
60	## Page Formats
61
62	### Format 1: [Competitor] Alternative (Singular)
63
64	Search intent: User is actively looking to switch from a specific competitor
65
66	URL pattern: `/alternatives/[competitor]` or `/[competitor]-alternative`
67
68	Target keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
69
70	Page structure:
71	1. Why people look for alternatives (validate their pain)
72	2. Summary: You as the alternative (quick positioning)
73	3. Detailed comparison (features, service, pricing)
74	4. Who should switch (and who shouldn't)
75	5. Migration path
76	6. Social proof from switchers
77	7. CTA
78
79	---
80
81	### Format 2: [Competitor] Alternatives (Plural)
82
83	Search intent: User is researching options, earlier in journey
84
85	URL pattern: `/alternatives/[competitor]-alternatives`
86
87	Target keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
88
89	Page structure:
90	1. Why people look for alternatives (common pain points)
91	2. What to look for in an alternative (criteria framework)
92	3. List of alternatives (you first, but include real options)
93	4. Comparison table (summary)
94	5. Detailed breakdown of each alternative
95	6. Recommendation by use case
96	7. CTA
97
98	Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
99
100	AI-answer expectations by stage: these pages often earn citations in AI answers, but whether AI recommends your brand from them depends on offsite consensus (reviews, forums, analysts) — for emerging brands, a self-ranked list can surface the competitors in the AI answer while you get only the citation. Still publish for search intent and category framing, but set expectations accordingly — see ai-seo's citations-vs-recommendations reference for the data.
101
102	---
103
104	### Format 3: You vs [Competitor]
105
106	Search intent: User is directly comparing you to a specific competitor
107
108	URL pattern: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]`
109
110	Target keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"
111
112	Page structure:
113	1. TL;DR summary (key differences in 2-3 sentences)
114	2. At-a-glance comparison table
115	3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
116	4. Who [You] is best for
117	5. Who [Competitor] is best for (be honest)
118	6. What customers say (testimonials from switchers)
119	7. Migration support
120	8. CTA
121
122	---
123
124	### Format 4: [Competitor A] vs [Competitor B]
125
126	Search intent: User comparing two competitors (not you directly)
127
128	URL pattern: `/compare/[c

People who liked this also viewed

6 picks

Type

competitors

37kinstalls6.5kforks

View on GitHub

How to install competitors?

coreyhaines31/marketingskills/competitors

$npx -y skills add coreyhaines31/marketingskills --skill competitors

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Competitor & Alternative Pages
2
3	You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
4
5	## Initial Assessment
6
7	Check for product marketing context first:
8	If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Before creating competitor pages, understand:
11
12	1. Your Product
13	- Core value proposition
14	- Key differentiators
15	- Ideal customer profile
16	- Pricing model
17	- Strengths and honest weaknesses
18
19	2. Competitive Landscape
20	- Direct competitors
21	- Indirect/adjacent competitors
22	- Market positioning of each
23	- Search volume for competitor terms
24
25	3. Goals
26	- SEO traffic capture
27	- Sales enablement
28	- Conversion from competitor users
29	- Brand positioning
30
31	---
32
33	## Core Principles
34
35	### 1. Honesty Builds Trust
36	- Acknowledge competitor strengths
37	- Be accurate about your limitations
38	- Don't misrepresent competitor features
39	- Readers are comparing—they'll verify claims
40
41	### 2. Depth Over Surface
42	- Go beyond feature checklists
43	- Explain why differences matter
44	- Include use cases and scenarios
45	- Show, don't just tell
46
47	### 3. Help Them Decide
48	- Different tools fit different needs
49	- Be clear about who you're best for
50	- Be clear about who competitor is best for
51	- Reduce evaluation friction
52
53	### 4. Modular Content Architecture
54	- Competitor data should be centralized
55	- Updates propagate to all pages
56	- Single source of truth per competitor
57
58	---
59
60	## Page Formats
61
62	### Format 1: [Competitor] Alternative (Singular)
63
64	Search intent: User is actively looking to switch from a specific competitor
65
66	URL pattern: `/alternatives/[competitor]` or `/[competitor]-alternative`
67
68	Target keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
69
70	Page structure:
71	1. Why people look for alternatives (validate their pain)
72	2. Summary: You as the alternative (quick positioning)
73	3. Detailed comparison (features, service, pricing)
74	4. Who should switch (and who shouldn't)
75	5. Migration path
76	6. Social proof from switchers
77	7. CTA
78
79	---
80
81	### Format 2: [Competitor] Alternatives (Plural)
82
83	Search intent: User is researching options, earlier in journey
84
85	URL pattern: `/alternatives/[competitor]-alternatives`
86
87	Target keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
88
89	Page structure:
90	1. Why people look for alternatives (common pain points)
91	2. What to look for in an alternative (criteria framework)
92	3. List of alternatives (you first, but include real options)
93	4. Comparison table (summary)
94	5. Detailed breakdown of each alternative
95	6. Recommendation by use case
96	7. CTA
97
98	Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
99
100	AI-answer expectations by stage: these pages often earn citations in AI answers, but whether AI recommends your brand from them depends on offsite consensus (reviews, forums, analysts) — for emerging brands, a self-ranked list can surface the competitors in the AI answer while you get only the citation. Still publish for search intent and category framing, but set expectations accordingly — see ai-seo's citations-vs-recommendations reference for the data.
101
102	---
103
104	### Format 3: You vs [Competitor]
105
106	Search intent: User is directly comparing you to a specific competitor
107
108	URL pattern: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]`
109
110	Target keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"
111
112	Page structure:
113	1. TL;DR summary (key differences in 2-3 sentences)
114	2. At-a-glance comparison table
115	3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
116	4. Who [You] is best for
117	5. Who [Competitor] is best for (be honest)
118	6. What customers say (testimonials from switchers)
119	7. Migration support
120	8. CTA
121
122	---
123
124	### Format 4: [Competitor A] vs [Competitor B]
125
126	Search intent: User comparing two competitors (not you directly)
127
128	URL pattern: `/compare/[c

People who liked this also viewed

6 picks

Type