content-moat-calculator

Name: content-moat-calculator
Author: Affitor

4installs184forks

How to install content-moat-calculator?

affitor/affiliate-skills/content-moat-calculator

$npx -y skills add Affitor/affiliate-skills --skill content-moat-calculator

Installs into the current project.

Summary

Estimate pages needed for topical authority. Go/no-go decision before investing months in content. Triggers on: "how much content do I need", "topical authority estimate", "content moat", "how many articles", "content gap analysis", "can I compete in this niche", "content investm

Files · 1

View on GitHub

SKILL.md

1	# Content Moat Calculator
2
3	Estimate the total content investment needed to establish topical authority in a niche. Analyzes competitors' content volume and quality to give you a go/no-go decision before investing months of work. Answers the question: "How many pages do I need to dominate this topic?"
4
5	## Stage
6
7	S3: Blog & SEO — This decides what blog content to build. It's the feasibility check that saves you from starting a content strategy you can't finish.
8
9	## When to Use
10
11	- User is deciding whether to invest in a niche/topic
12	- User asks "how many articles do I need to rank?"
13	- User wants to understand the content investment required
14	- User says "content moat", "topical authority", "feasibility", "content gap"
15	- After `keyword-cluster-architect` to estimate effort for the planned clusters
16	- Before committing to a major content initiative
17
18	## Input Schema
19
20	```yaml
21	niche: string # REQUIRED — the topic to analyze
22	# e.g., "AI video tools", "email marketing for SaaS"
23
24	hub_keyword: string # OPTIONAL — main keyword to analyze competitors for
25	# Default: inferred from niche
26
27	your_current_pages: number # OPTIONAL — how many pages you already have on this topic
28	# Default: 0
29
30	publishing_capacity: string # OPTIONAL — "1/week" \| "2/week" \| "3/week" \| "5/week"
31	# Default: "2/week"
32	```
33
34	Chaining from S3 keyword-cluster-architect: Use `keyword_clusters.total_clusters` and `keyword_clusters.hub.keyword`.
35
36	## Workflow
37
38	### Step 1: Analyze Top Competitors
39
40	Read `shared/references/seo-strategy.md` for moat calculation methodology.
41
42	1. `web_search` for `[hub_keyword]` or main niche keyword
43	2. Identify top 5 ranking sites (exclude giants like Wikipedia, Reddit)
44	3. For each competitor:
45	- `web_search`: `site:[competitor.com] [niche topic]` — count pages on this topic
46	- Note: content depth (word count), content freshness (publish dates), content types (blog, comparison, tutorial)
47
48	### Step 2: Calculate Moat
49
50	```
51	Average competitor pages = sum(competitor_pages) / number_of_competitors
52	Your moat target = Average × 1.5 (need MORE than average to break through)
53	Content gap = Moat target - your_current_pages
54	```
55
56	### Step 3: Feasibility Assessment
57
58	Based on moat target and publishing capacity:
59
60	```
61	Weeks to moat = Content gap / publishing_capacity_per_week
62	```
63
64	\| Moat Target \| Assessment \| Recommendation \|
65	\|---\|---\|---\|
66	\| < 20 pages \| GREEN — Achievable \| Go for it. 2-3 months at 2/week. \|
67	\| 20-50 pages \| YELLOW — Significant \| Commit or don't. 3-6 months at 2/week. \|
68	\| 50-100 pages \| ORANGE — Major investment \| Consider narrowing niche. 6-12 months. \|
69	\| 100+ pages \| RED — Very high barrier \| Find a sub-niche or different angle. \|
70
71	### Step 4: Competitive Advantage Analysis
72
73	Identify ways to build moat FASTER:
74	1. Quality over quantity: Can you beat thin content with fewer, deeper pages?
75	2. Unique data: Can you add proprietary data competitors don't have? (→ `proprietary-data-generator`)
76	3. Format advantage: Can you use formats competitors don't? (video, interactive, tools)
77	4. Update velocity: Can you refresh content faster than competitors?
78
79	### Step 5: Timeline and Roadmap
80
81	Create realistic timeline:
82	- Phase 1: Foundation content (hub + core spokes)
83	- Phase 2: Supporting content (additional spokes, long-tail)
84	- Phase 3: Authority content (original research, data, comprehensive guides)
85	- Phase 4: Maintenance (refresh, update, expand)
86
87	### Step 6: Self-Validation
88
89	- [ ] Competitor analysis uses real data (not estimates)
90	- [ ] Moat calculation is transparent and logical
91	- [ ] Feasibility assessment is honest (not overly optimistic)
92	- [ ] Competitive advantages are realistic
93	- [ ] Timeline accounts for quality, not just quantity
94
95	## Output Schema
96
97	```yaml
98	output_schema_version: "1.0.0"
99	content_moat:
100	niche: string
101	hub_keyword: string
102	competitors_analyzed: number
103	average_competitor_pages: number
104	moat_target: number
105	your_current_pages: number
106	content_gap: number
107	feasibility: string # "green" \| "yellow" \| "oran

People who liked this also viewed

6 picks

Type

content-moat-calculator

4installs184forks

View on GitHub

How to install content-moat-calculator?

affitor/affiliate-skills/content-moat-calculator

$npx -y skills add Affitor/affiliate-skills --skill content-moat-calculator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Content Moat Calculator
2
3	Estimate the total content investment needed to establish topical authority in a niche. Analyzes competitors' content volume and quality to give you a go/no-go decision before investing months of work. Answers the question: "How many pages do I need to dominate this topic?"
4
5	## Stage
6
7	S3: Blog & SEO — This decides what blog content to build. It's the feasibility check that saves you from starting a content strategy you can't finish.
8
9	## When to Use
10
11	- User is deciding whether to invest in a niche/topic
12	- User asks "how many articles do I need to rank?"
13	- User wants to understand the content investment required
14	- User says "content moat", "topical authority", "feasibility", "content gap"
15	- After `keyword-cluster-architect` to estimate effort for the planned clusters
16	- Before committing to a major content initiative
17
18	## Input Schema
19
20	```yaml
21	niche: string # REQUIRED — the topic to analyze
22	# e.g., "AI video tools", "email marketing for SaaS"
23
24	hub_keyword: string # OPTIONAL — main keyword to analyze competitors for
25	# Default: inferred from niche
26
27	your_current_pages: number # OPTIONAL — how many pages you already have on this topic
28	# Default: 0
29
30	publishing_capacity: string # OPTIONAL — "1/week" \| "2/week" \| "3/week" \| "5/week"
31	# Default: "2/week"
32	```
33
34	Chaining from S3 keyword-cluster-architect: Use `keyword_clusters.total_clusters` and `keyword_clusters.hub.keyword`.
35
36	## Workflow
37
38	### Step 1: Analyze Top Competitors
39
40	Read `shared/references/seo-strategy.md` for moat calculation methodology.
41
42	1. `web_search` for `[hub_keyword]` or main niche keyword
43	2. Identify top 5 ranking sites (exclude giants like Wikipedia, Reddit)
44	3. For each competitor:
45	- `web_search`: `site:[competitor.com] [niche topic]` — count pages on this topic
46	- Note: content depth (word count), content freshness (publish dates), content types (blog, comparison, tutorial)
47
48	### Step 2: Calculate Moat
49
50	```
51	Average competitor pages = sum(competitor_pages) / number_of_competitors
52	Your moat target = Average × 1.5 (need MORE than average to break through)
53	Content gap = Moat target - your_current_pages
54	```
55
56	### Step 3: Feasibility Assessment
57
58	Based on moat target and publishing capacity:
59
60	```
61	Weeks to moat = Content gap / publishing_capacity_per_week
62	```
63
64	\| Moat Target \| Assessment \| Recommendation \|
65	\|---\|---\|---\|
66	\| < 20 pages \| GREEN — Achievable \| Go for it. 2-3 months at 2/week. \|
67	\| 20-50 pages \| YELLOW — Significant \| Commit or don't. 3-6 months at 2/week. \|
68	\| 50-100 pages \| ORANGE — Major investment \| Consider narrowing niche. 6-12 months. \|
69	\| 100+ pages \| RED — Very high barrier \| Find a sub-niche or different angle. \|
70
71	### Step 4: Competitive Advantage Analysis
72
73	Identify ways to build moat FASTER:
74	1. Quality over quantity: Can you beat thin content with fewer, deeper pages?
75	2. Unique data: Can you add proprietary data competitors don't have? (→ `proprietary-data-generator`)
76	3. Format advantage: Can you use formats competitors don't? (video, interactive, tools)
77	4. Update velocity: Can you refresh content faster than competitors?
78
79	### Step 5: Timeline and Roadmap
80
81	Create realistic timeline:
82	- Phase 1: Foundation content (hub + core spokes)
83	- Phase 2: Supporting content (additional spokes, long-tail)
84	- Phase 3: Authority content (original research, data, comprehensive guides)
85	- Phase 4: Maintenance (refresh, update, expand)
86
87	### Step 6: Self-Validation
88
89	- [ ] Competitor analysis uses real data (not estimates)
90	- [ ] Moat calculation is transparent and logical
91	- [ ] Feasibility assessment is honest (not overly optimistic)
92	- [ ] Competitive advantages are realistic
93	- [ ] Timeline accounts for quality, not just quantity
94
95	## Output Schema
96
97	```yaml
98	output_schema_version: "1.0.0"
99	content_moat:
100	niche: string
101	hub_keyword: string
102	competitors_analyzed: number
103	average_competitor_pages: number
104	moat_target: number
105	your_current_pages: number
106	content_gap: number
107	feasibility: string # "green" \| "yellow" \| "oran

People who liked this also viewed

6 picks

Type