hive-rank 3.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +76 -0
- package/bin/install.js +519 -0
- package/commands/audit-site.md +47 -0
- package/commands/audit.md +22 -0
- package/commands/baseline.md +39 -0
- package/commands/competitors.md +37 -0
- package/commands/content.md +39 -0
- package/commands/grow.md +40 -0
- package/commands/help.md +67 -0
- package/commands/keywords.md +48 -0
- package/commands/kickstart.md +43 -0
- package/commands/learn.md +80 -0
- package/commands/rankings.md +22 -0
- package/commands/report.md +40 -0
- package/commands/spy.md +48 -0
- package/commands/status.md +45 -0
- package/commands/trends.md +44 -0
- package/dist/hooks/capture-seo-data.js +419 -0
- package/dist/hooks/config.json +5 -0
- package/package.json +45 -0
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: baseline
|
|
3
|
+
description: Establish baseline rankings for your target keywords
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_rankings
|
|
8
|
+
- hive_domain
|
|
9
|
+
- hive_search
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
Establish baseline rankings for $ARGUMENTS.
|
|
13
|
+
|
|
14
|
+
**Input formats:**
|
|
15
|
+
- Domain only: `/hive:baseline kinsta.com` — will ask for target keywords
|
|
16
|
+
- Keywords only: `/hive:baseline best wordpress hosting, kinsta vs wp engine` — will ask for domain
|
|
17
|
+
- Both: `/hive:baseline kinsta.com best wordpress hosting, managed wp hosting`
|
|
18
|
+
|
|
19
|
+
If no arguments are provided, ask the user for their top 5-10 target keywords and their domain.
|
|
20
|
+
|
|
21
|
+
For each keyword provided:
|
|
22
|
+
1. WebSearch the exact keyword to capture the current SERP
|
|
23
|
+
2. Note where the user's domain ranks (if provided)
|
|
24
|
+
|
|
25
|
+
After all searches complete:
|
|
26
|
+
- Use `hive_rankings` on each keyword to see network-wide data
|
|
27
|
+
- Use `hive_domain` (if domain provided) to check network data for that domain
|
|
28
|
+
- Present a ranking baseline table:
|
|
29
|
+
|
|
30
|
+
| Keyword | Your Position | Top Competitor | Network Data Available |
|
|
31
|
+
|---------|--------------|----------------|------------------------|
|
|
32
|
+
| ... | ... | ... | Yes/No |
|
|
33
|
+
|
|
34
|
+
For each keyword, note:
|
|
35
|
+
- Current position (from fresh WebSearch)
|
|
36
|
+
- Top competitors visible
|
|
37
|
+
- Whether the network has historical data
|
|
38
|
+
|
|
39
|
+
Suggest running this monthly to track changes over time. Each search contributes to the network, building richer historical data.
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: competitors
|
|
3
|
+
description: Discover and analyze your SEO competitors
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_domain
|
|
8
|
+
- hive_search
|
|
9
|
+
- hive_rankings
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
Find and analyze SEO competitors for the specified domain (or ask me which domain).
|
|
13
|
+
|
|
14
|
+
**Step 1 — Identify the Domain:**
|
|
15
|
+
If no domain is specified, ask the user which domain to analyze.
|
|
16
|
+
|
|
17
|
+
**Step 2 — Research Competitors:**
|
|
18
|
+
- WebSearch the domain's brand name
|
|
19
|
+
- WebFetch the homepage to understand what they do
|
|
20
|
+
- WebSearch "[domain] vs" and "[domain] alternatives"
|
|
21
|
+
- WebSearch 3-5 key product/service keywords related to their niche
|
|
22
|
+
|
|
23
|
+
**Step 3 — Network Intelligence:**
|
|
24
|
+
- Use `hive_domain` to get network data on this domain
|
|
25
|
+
- Use `hive_search` to find related queries in the network
|
|
26
|
+
- For each competitor identified, use `hive_domain` to compare presence
|
|
27
|
+
|
|
28
|
+
**Step 4 — Analysis:**
|
|
29
|
+
Present a clear summary:
|
|
30
|
+
- Who the top competitors are (appear for same keywords)
|
|
31
|
+
- Apparent strengths of each competitor
|
|
32
|
+
- Gaps and weaknesses you could exploit
|
|
33
|
+
- Recommended next steps
|
|
34
|
+
|
|
35
|
+
Each search contributes to the network, building competitive intelligence for everyone.
|
|
36
|
+
|
|
37
|
+
$ARGUMENTS
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: content
|
|
3
|
+
description: Research a topic and generate an SEO-optimized content brief
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_rankings
|
|
8
|
+
- hive_search
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
Research and create an SEO content brief for: $ARGUMENTS
|
|
12
|
+
|
|
13
|
+
If no topic or keyword is specified, ask the user what topic to research.
|
|
14
|
+
|
|
15
|
+
**Step 1 — SERP Research:**
|
|
16
|
+
- WebSearch the primary keyword to capture the current SERP
|
|
17
|
+
- WebSearch 2-3 variations (question format, long-tail, commercial intent)
|
|
18
|
+
- WebFetch the top 3 ranking pages to analyze their content
|
|
19
|
+
|
|
20
|
+
**Step 2 — Pattern Analysis:**
|
|
21
|
+
From the WebFetch results, identify:
|
|
22
|
+
- Common title patterns (listicle, guide, comparison, etc.)
|
|
23
|
+
- H1 structures that rank well
|
|
24
|
+
- Content depth and format
|
|
25
|
+
- Key terms and topics covered
|
|
26
|
+
|
|
27
|
+
**Step 3 — Network Intelligence:**
|
|
28
|
+
- Use `hive_rankings` to see network data for this keyword
|
|
29
|
+
- Use `hive_search` to find related queries
|
|
30
|
+
|
|
31
|
+
**Step 4 — Deliver Content Brief:**
|
|
32
|
+
|
|
33
|
+
- **Target keyword** + secondary keywords (from your research)
|
|
34
|
+
- **Search intent** — informational, commercial, transactional, navigational
|
|
35
|
+
- **Recommended title** — based on patterns that rank
|
|
36
|
+
- **Content format** — listicle, guide, comparison, review, etc.
|
|
37
|
+
- **Key sections to include** — based on what top results cover
|
|
38
|
+
- **Differentiation angle** — gaps in existing content you could fill
|
|
39
|
+
- **Word count guidance** — based on top-ranking content depth
|
package/commands/grow.md
ADDED
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: grow
|
|
3
|
+
description: Weekly SEO growth check — new opportunities, ranking changes, fresh data
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_domain
|
|
8
|
+
- hive_trending
|
|
9
|
+
- hive_rankings
|
|
10
|
+
- hive_search
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
Run a weekly SEO growth check for $ARGUMENTS.
|
|
14
|
+
|
|
15
|
+
If no domain is specified, ask which domain to analyze.
|
|
16
|
+
|
|
17
|
+
**Step 1 — Refresh Core Data:**
|
|
18
|
+
- WebSearch the domain's brand name
|
|
19
|
+
- WebSearch 3-5 key product/service keywords
|
|
20
|
+
- WebSearch 2-3 new keyword variations or long-tail extensions
|
|
21
|
+
- WebSearch the domain name plus any known competitors
|
|
22
|
+
|
|
23
|
+
**Step 2 — Check Network Intelligence:**
|
|
24
|
+
- Use `hive_domain` to get current network data for this domain
|
|
25
|
+
- Use `hive_trending` to spot what's moving network-wide
|
|
26
|
+
- Use `hive_rankings` on top keywords to see aggregated positions
|
|
27
|
+
|
|
28
|
+
**Step 3 — Discover Opportunities:**
|
|
29
|
+
- WebSearch 2-3 question-format queries related to the niche
|
|
30
|
+
- WebSearch 1-2 trending or seasonal keywords
|
|
31
|
+
- WebFetch any new competitor pages discovered
|
|
32
|
+
|
|
33
|
+
**Step 4 — Present Summary:**
|
|
34
|
+
- What's the domain's current visibility?
|
|
35
|
+
- Any notable trends from the network?
|
|
36
|
+
- New competitors or threats identified?
|
|
37
|
+
- One quick-win opportunity to act on this week
|
|
38
|
+
- What to research next time
|
|
39
|
+
|
|
40
|
+
Run this weekly to keep contributing fresh data to the network. The more you search, the richer the collective intelligence becomes.
|
package/commands/help.md
ADDED
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: help
|
|
3
|
+
description: Show all Hive Rank commands and tools
|
|
4
|
+
allowed-tools: []
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
Show me a usage guide for Hive Rank. List all available slash commands and MCP tools.
|
|
8
|
+
|
|
9
|
+
**IMPORTANT:** Reproduce ALL sections below exactly — do not summarize, omit, or abbreviate any commands, tables, or content.
|
|
10
|
+
|
|
11
|
+
**Hive Rank is a crowdsourced SEO intelligence network.** Every WebSearch and WebFetch you run automatically contributes anonymized data to the hive. The more agents contribute, the richer the collective intelligence becomes.
|
|
12
|
+
|
|
13
|
+
**Slash Commands — Research (generates data for the hive):**
|
|
14
|
+
|
|
15
|
+
These commands guide SEO research. Every WebSearch and WebFetch they trigger contributes to the network.
|
|
16
|
+
|
|
17
|
+
| Command | What it does |
|
|
18
|
+
|---------|-------------|
|
|
19
|
+
| `/hive:kickstart [domain]` | **Start here.** Bootstrap SEO research — site analysis, competitors, keyword landscape |
|
|
20
|
+
| `/hive:baseline [domain] [keywords...]` | Establish baseline rankings for target keywords |
|
|
21
|
+
| `/hive:grow [domain]` | Weekly growth check — fresh data, ranking changes, new opportunities |
|
|
22
|
+
| `/hive:spy [competitor]` | Deep-dive into a competitor's SEO strategy |
|
|
23
|
+
| `/hive:content [topic]` | Research a topic and generate an SEO content brief |
|
|
24
|
+
| `/hive:learn [topic]` | Learn SEO concepts with real examples |
|
|
25
|
+
| `/hive:audit-site [domain]` | Run a technical SEO audit on a website |
|
|
26
|
+
|
|
27
|
+
**Slash Commands — Network Intelligence:**
|
|
28
|
+
|
|
29
|
+
These commands query the hive network for aggregated insights.
|
|
30
|
+
|
|
31
|
+
| Command | What it does |
|
|
32
|
+
|---------|-------------|
|
|
33
|
+
| `/hive:rankings [query]` | Check network ranking data for a query |
|
|
34
|
+
| `/hive:trends` | See what's trending across the network |
|
|
35
|
+
| `/hive:competitors [domain]` | Find competitors via network intelligence |
|
|
36
|
+
| `/hive:keywords [domain]` | Find keyword opportunities |
|
|
37
|
+
| `/hive:report [domain]` | Generate an SEO report from network data |
|
|
38
|
+
| `/hive:audit` | Check network contribution status |
|
|
39
|
+
| `/hive:status` | Hive network status and your contribution stats |
|
|
40
|
+
| `/hive:help` | This help guide |
|
|
41
|
+
|
|
42
|
+
**MCP Tools (6 network tools via hive-rank server):**
|
|
43
|
+
|
|
44
|
+
| Tool | What it does |
|
|
45
|
+
|------|-------------|
|
|
46
|
+
| `hive_stats` | Network statistics — contributors, observations, coverage |
|
|
47
|
+
| `hive_rankings(query)` | Aggregated ranking data from the network |
|
|
48
|
+
| `hive_trending` | What's gaining/losing across all contributors |
|
|
49
|
+
| `hive_domain(domain)` | Domain intelligence from network observations |
|
|
50
|
+
| `hive_contributors` | Contributor activity and leaderboard |
|
|
51
|
+
| `hive_search(term)` | Full-text search across network data |
|
|
52
|
+
|
|
53
|
+
**How it works:**
|
|
54
|
+
|
|
55
|
+
1. **You search** — Every WebSearch and WebFetch captures SEO data
|
|
56
|
+
2. **Hook contributes** — The PostToolUse hook sends anonymized data to the network
|
|
57
|
+
3. **Network grows** — Aggregated insights become available via `hive_*` tools
|
|
58
|
+
4. **Everyone benefits** — Richer data for all agents in the network
|
|
59
|
+
|
|
60
|
+
**Privacy:**
|
|
61
|
+
- Only public search data is shared (queries, URLs, positions — visible to anyone searching)
|
|
62
|
+
- Your identity is hashed (SHA-256, one-way) — no account, not trackable
|
|
63
|
+
- Timestamps are bucketed to date-only to prevent session correlation
|
|
64
|
+
|
|
65
|
+
**Dashboard:** https://www.hive-rank.com
|
|
66
|
+
|
|
67
|
+
$ARGUMENTS
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: keywords
|
|
3
|
+
description: Find keyword opportunities for a domain
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_domain
|
|
8
|
+
- hive_search
|
|
9
|
+
- hive_rankings
|
|
10
|
+
- hive_trending
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
Find keyword opportunities for the specified domain.
|
|
14
|
+
|
|
15
|
+
If no domain is specified, ask which domain to analyze.
|
|
16
|
+
|
|
17
|
+
**Step 1 — Understand the Domain:**
|
|
18
|
+
- WebFetch the homepage to understand what they do
|
|
19
|
+
- WebSearch the brand name to see current visibility
|
|
20
|
+
- Use `hive_domain` to check network data
|
|
21
|
+
|
|
22
|
+
**Step 2 — Research Keyword Landscape:**
|
|
23
|
+
- WebSearch 5-8 key product/service keywords
|
|
24
|
+
- WebSearch 3-5 informational "how to" queries
|
|
25
|
+
- WebSearch 2-3 commercial "best [category]" queries
|
|
26
|
+
- WebSearch "[domain] vs [competitor]" patterns
|
|
27
|
+
|
|
28
|
+
**Step 3 — Network Intelligence:**
|
|
29
|
+
- Use `hive_search` to find related queries in the network
|
|
30
|
+
- Use `hive_rankings` on promising keywords
|
|
31
|
+
- Use `hive_trending` to identify rising opportunities
|
|
32
|
+
|
|
33
|
+
**Step 4 — Synthesize Opportunities:**
|
|
34
|
+
|
|
35
|
+
Present findings in three categories:
|
|
36
|
+
|
|
37
|
+
1. **Quick Wins** — Keywords where the domain already appears but could rank higher
|
|
38
|
+
2. **Gaps** — Keywords competitors rank for that this domain doesn't
|
|
39
|
+
3. **Emerging** — Trending queries in the network that align with the domain's niche
|
|
40
|
+
|
|
41
|
+
For each category, present 5-10 keywords with:
|
|
42
|
+
- Current position (if any)
|
|
43
|
+
- Competitor presence
|
|
44
|
+
- Opportunity assessment
|
|
45
|
+
|
|
46
|
+
End with 2-3 specific action items.
|
|
47
|
+
|
|
48
|
+
$ARGUMENTS
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: kickstart
|
|
3
|
+
description: Bootstrap your SEO research — analyzes a site, finds competitors, maps keyword landscape
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_stats
|
|
8
|
+
- hive_domain
|
|
9
|
+
- hive_search
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
Perform a comprehensive SEO kickstart analysis for $ARGUMENTS.
|
|
13
|
+
|
|
14
|
+
If no domain is specified, ask the user which domain/site to analyze.
|
|
15
|
+
|
|
16
|
+
**Phase 1 — Site Discovery:**
|
|
17
|
+
- WebSearch the domain name to see how it appears in results
|
|
18
|
+
- WebFetch the homepage and 2-3 key pages to capture metadata
|
|
19
|
+
- WebSearch "site:[domain]" to discover indexed pages
|
|
20
|
+
|
|
21
|
+
**Phase 2 — Competitive Landscape:**
|
|
22
|
+
- WebSearch the domain's primary product/service keywords (infer from homepage content)
|
|
23
|
+
- WebSearch "[domain] vs" and "[domain] alternatives" to find competitors
|
|
24
|
+
- WebFetch the top 3 competitor homepages
|
|
25
|
+
|
|
26
|
+
**Phase 3 — Keyword Landscape:**
|
|
27
|
+
- WebSearch 5-8 high-intent keywords related to the site's niche
|
|
28
|
+
- WebSearch 3-5 informational queries the site's audience would ask
|
|
29
|
+
- WebSearch 2-3 "best [category]" and "how to [topic]" queries
|
|
30
|
+
|
|
31
|
+
**Phase 4 — Network Check:**
|
|
32
|
+
- Use `hive_stats` to confirm the network is available
|
|
33
|
+
- Use `hive_domain` to check if the network has existing data for this domain
|
|
34
|
+
- Use `hive_search` to find related queries already in the network
|
|
35
|
+
|
|
36
|
+
Present a clear summary:
|
|
37
|
+
- What the site does and who it competes with
|
|
38
|
+
- Key pages and their content focus
|
|
39
|
+
- Competitors identified
|
|
40
|
+
- Top 3 immediate opportunities spotted
|
|
41
|
+
- What to research next to deepen understanding
|
|
42
|
+
|
|
43
|
+
This kickstart contributes all your searches to the hive network, building intelligence for everyone.
|
|
@@ -0,0 +1,80 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: learn
|
|
3
|
+
description: Learn SEO concepts with real examples
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_stats
|
|
8
|
+
- hive_rankings
|
|
9
|
+
- hive_domain
|
|
10
|
+
- hive_search
|
|
11
|
+
- hive_trending
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
The user wants to learn about SEO. Topic requested: $ARGUMENTS
|
|
15
|
+
|
|
16
|
+
If the topic is empty or unspecified, present the topics below as a numbered list and ask the user to pick one.
|
|
17
|
+
|
|
18
|
+
**Learning Path** (start at the top if you're new to SEO):
|
|
19
|
+
|
|
20
|
+
Beginner:
|
|
21
|
+
1. "keyword research" — how to find what people search for and which terms to target
|
|
22
|
+
2. "search intent" — why matching what searchers want matters more than keyword volume
|
|
23
|
+
3. "on-page optimization" — what top-ranking pages have in common and how to match them
|
|
24
|
+
|
|
25
|
+
Intermediate:
|
|
26
|
+
4. "content strategy" — planning content around topics and gaps in the market
|
|
27
|
+
5. "competitor analysis" — understanding who you're competing against and where they're weak
|
|
28
|
+
|
|
29
|
+
Advanced:
|
|
30
|
+
6. "technical seo" — site structure, internal linking, and crawlability fundamentals
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
**How to teach each topic:**
|
|
35
|
+
|
|
36
|
+
**Step 1 — Explain the Principle:**
|
|
37
|
+
- 2-3 sentences explaining the concept
|
|
38
|
+
- Why it matters for rankings
|
|
39
|
+
|
|
40
|
+
**Step 2 — Demonstrate with Live Research:**
|
|
41
|
+
|
|
42
|
+
Use WebSearch and WebFetch to show real examples, then use network tools to add context.
|
|
43
|
+
|
|
44
|
+
For **keyword research**:
|
|
45
|
+
- WebSearch 3 related queries in a sample niche
|
|
46
|
+
- Use `hive_search` to find related queries in the network
|
|
47
|
+
- Teach: keyword research is about finding clusters of related queries, not just individual keywords
|
|
48
|
+
|
|
49
|
+
For **search intent**:
|
|
50
|
+
- WebSearch queries with different intents: informational, commercial, transactional
|
|
51
|
+
- Analyze the results — what content type ranks for each?
|
|
52
|
+
- Teach: matching intent is why a buying guide outranks a product page for "best X" queries
|
|
53
|
+
|
|
54
|
+
For **on-page optimization**:
|
|
55
|
+
- WebSearch a competitive keyword
|
|
56
|
+
- WebFetch the top 3 results
|
|
57
|
+
- Analyze title patterns, H1 structures, content depth
|
|
58
|
+
- Teach: on-page optimization is reverse-engineering what already works
|
|
59
|
+
|
|
60
|
+
For **content strategy**:
|
|
61
|
+
- WebSearch a niche from multiple angles
|
|
62
|
+
- Use `hive_domain` to show how different sites cover different topics
|
|
63
|
+
- Teach: content strategy is about covering topic clusters completely
|
|
64
|
+
|
|
65
|
+
For **competitor analysis**:
|
|
66
|
+
- WebSearch a main keyword to see who ranks
|
|
67
|
+
- WebFetch competitor pages
|
|
68
|
+
- Use `hive_trending` to see who's gaining/losing
|
|
69
|
+
- Teach: competitor analysis reveals opportunities by showing gaps
|
|
70
|
+
|
|
71
|
+
For **technical seo**:
|
|
72
|
+
- WebSearch "site:[domain]" to check indexation
|
|
73
|
+
- WebFetch key pages and check metadata
|
|
74
|
+
- Teach: technical SEO ensures search engines can find and understand your content
|
|
75
|
+
|
|
76
|
+
**Step 3 — Actionable Takeaway:**
|
|
77
|
+
- One specific thing the user can do right now
|
|
78
|
+
|
|
79
|
+
**Step 4 — Practice Exercise:**
|
|
80
|
+
A hands-on task that reinforces the concept AND contributes data to the network.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: rankings
|
|
3
|
+
description: Check network ranking data for a search query
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_rankings
|
|
8
|
+
- hive_trending
|
|
9
|
+
- hive_stats
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
Show me the ranking data for the specified query.
|
|
13
|
+
|
|
14
|
+
1. Use `hive_rankings` to pull network ranking data for this query
|
|
15
|
+
2. Use `hive_trending` to see if this query is trending up or down
|
|
16
|
+
3. Present a clear summary: who's ranking, what positions, and any notable patterns
|
|
17
|
+
|
|
18
|
+
If no query is specified, ask me what query to look up.
|
|
19
|
+
|
|
20
|
+
If the network has limited data for this query, suggest running a WebSearch to contribute fresh data.
|
|
21
|
+
|
|
22
|
+
$ARGUMENTS
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: report
|
|
3
|
+
description: Generate an SEO report from network data
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_domain
|
|
8
|
+
- hive_rankings
|
|
9
|
+
- hive_trending
|
|
10
|
+
- hive_search
|
|
11
|
+
- hive_stats
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
Generate a comprehensive SEO report for the specified domain (or ask me which domain to analyze).
|
|
15
|
+
|
|
16
|
+
**Step 1 — Gather Network Intelligence:**
|
|
17
|
+
- Use `hive_domain` to get all network data for this domain
|
|
18
|
+
- Use `hive_search` to find related queries in the network
|
|
19
|
+
- Use `hive_trending` to identify movement patterns
|
|
20
|
+
|
|
21
|
+
**Step 2 — Enrich with Fresh Research:**
|
|
22
|
+
- WebSearch the domain's brand name
|
|
23
|
+
- WebSearch 3-5 key queries related to their niche
|
|
24
|
+
- WebFetch the homepage and key pages
|
|
25
|
+
|
|
26
|
+
**Step 3 — Compile Report:**
|
|
27
|
+
|
|
28
|
+
Present a markdown report with these sections:
|
|
29
|
+
|
|
30
|
+
1. **Domain Overview** — What the site does, key pages, apparent focus
|
|
31
|
+
2. **Network Presence** — How the domain appears across hive network data
|
|
32
|
+
3. **Ranking Snapshot** — Current positions for key queries (from hive_rankings + fresh searches)
|
|
33
|
+
4. **Trends** — What's moving up or down (from hive_trending)
|
|
34
|
+
5. **Competitive Context** — Who else appears for similar queries
|
|
35
|
+
6. **Opportunities** — Gaps and quick wins identified
|
|
36
|
+
7. **Next Steps** — Specific recommendations
|
|
37
|
+
|
|
38
|
+
If network data is sparse for this domain, note this and rely more on fresh WebSearch/WebFetch research.
|
|
39
|
+
|
|
40
|
+
$ARGUMENTS
|
package/commands/spy.md
ADDED
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: spy
|
|
3
|
+
description: Deep-dive analysis of a specific competitor's SEO strategy
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_domain
|
|
8
|
+
- hive_rankings
|
|
9
|
+
- hive_search
|
|
10
|
+
- hive_trending
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
Perform a deep competitive analysis of $ARGUMENTS.
|
|
14
|
+
|
|
15
|
+
If no competitor domain is specified, ask the user which competitor to analyze.
|
|
16
|
+
|
|
17
|
+
**Step 0 — Establish Context:**
|
|
18
|
+
- Confirm the competitor domain to analyze
|
|
19
|
+
- Ask the user for their own domain (to enable competitive framing)
|
|
20
|
+
|
|
21
|
+
**Step 1 — Map Their Presence:**
|
|
22
|
+
- WebSearch the competitor's brand name
|
|
23
|
+
- WebFetch their homepage, about page, and blog index
|
|
24
|
+
- WebSearch "site:[competitor]" to estimate indexed pages
|
|
25
|
+
- WebSearch "[competitor] reviews" to understand market perception
|
|
26
|
+
|
|
27
|
+
**Step 2 — Reverse-Engineer Their Keywords:**
|
|
28
|
+
- WebFetch their top 5 pages (discovered from search results)
|
|
29
|
+
- For each page: infer target keywords from title, H1, content
|
|
30
|
+
- WebSearch those inferred keywords to see where they rank
|
|
31
|
+
|
|
32
|
+
**Step 3 — Network Intelligence:**
|
|
33
|
+
- Use `hive_domain` on the competitor to see network data
|
|
34
|
+
- Use `hive_search` to find queries related to the competitor
|
|
35
|
+
- Use `hive_trending` to see if the competitor is gaining or losing
|
|
36
|
+
|
|
37
|
+
**Step 4 — Find Their Weaknesses:**
|
|
38
|
+
- WebSearch long-tail variations of their top keywords
|
|
39
|
+
- Look for keywords where they rank #4-10 (vulnerable positions)
|
|
40
|
+
- Compare with your domain using `hive_domain`
|
|
41
|
+
|
|
42
|
+
**Step 5 — Present Analysis:**
|
|
43
|
+
- Their keyword strategy (what they're targeting)
|
|
44
|
+
- Where they're strong vs where they're weak
|
|
45
|
+
- 3-5 specific keywords you could take from them
|
|
46
|
+
- Content approach needed to win those keywords
|
|
47
|
+
|
|
48
|
+
Each search contributes to the network, building competitive intelligence for everyone.
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: status
|
|
3
|
+
description: Check hive network status, contribution stats, and network intelligence
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_stats
|
|
8
|
+
- hive_rankings
|
|
9
|
+
- hive_trending
|
|
10
|
+
- hive_domain
|
|
11
|
+
- hive_contributors
|
|
12
|
+
- hive_search
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
Check the status of the Hive Rank network.
|
|
16
|
+
|
|
17
|
+
**Step 1: Get network statistics**
|
|
18
|
+
|
|
19
|
+
Call `hive_stats()` to get current network data:
|
|
20
|
+
- Total contributors
|
|
21
|
+
- Total observations
|
|
22
|
+
- Query coverage
|
|
23
|
+
- Recent activity
|
|
24
|
+
|
|
25
|
+
**Step 2: Show network activity**
|
|
26
|
+
|
|
27
|
+
Call `hive_contributors()` to see who's active and `hive_trending()` to show what's moving.
|
|
28
|
+
|
|
29
|
+
Present the results clearly:
|
|
30
|
+
- Network health summary
|
|
31
|
+
- Top trending queries/domains
|
|
32
|
+
- Recent contributor activity
|
|
33
|
+
|
|
34
|
+
**Important — Early Network Context:**
|
|
35
|
+
|
|
36
|
+
The hive network may still be growing. If results are sparse, explain: "The hive network grows richer as more agents contribute. Every search you make helps build collective intelligence."
|
|
37
|
+
|
|
38
|
+
**Hive Network Info:**
|
|
39
|
+
- The hive is a shared network where agents contribute anonymized search data
|
|
40
|
+
- The hive server runs at mcp.hive-rank.com — dashboard at www.hive-rank.com
|
|
41
|
+
- Only public search data is shared (queries, URLs, positions — already visible to anyone searching)
|
|
42
|
+
- Your identity is hashed (SHA-256, one-way) — no account, not trackable
|
|
43
|
+
- Timestamps are bucketed to date-only to prevent session correlation
|
|
44
|
+
|
|
45
|
+
$ARGUMENTS
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: trends
|
|
3
|
+
description: See what's trending across the hive network
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- mcp: hive-rank
|
|
6
|
+
tools:
|
|
7
|
+
- hive_trending
|
|
8
|
+
- hive_domain
|
|
9
|
+
- hive_stats
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
Show me what's trending in the hive network.
|
|
13
|
+
|
|
14
|
+
**Interpret the user's argument to determine the mode:**
|
|
15
|
+
|
|
16
|
+
- **No argument:** Show network-wide trends — what's gaining/losing across all contributors.
|
|
17
|
+
- **Domain argument** (e.g., `kinsta.com`): Show trends scoped to that domain using `hive_domain`.
|
|
18
|
+
- **Query argument** (e.g., `"react frameworks 2026"`): Show trends for that specific query.
|
|
19
|
+
|
|
20
|
+
If it's ambiguous whether the argument is a domain or a query, treat anything with a TLD (`.com`, `.io`, `.org`, etc.) as a domain, and everything else as a query.
|
|
21
|
+
|
|
22
|
+
**Mode A — Network-wide (no argument):**
|
|
23
|
+
1. Use `hive_trending` to get aggregate movers across the network
|
|
24
|
+
2. Use `hive_stats` to provide context on network size and coverage
|
|
25
|
+
3. Present the biggest gainers and losers network-wide
|
|
26
|
+
|
|
27
|
+
**Mode B — Domain-scoped (domain argument):**
|
|
28
|
+
1. Use `hive_domain` to get network intelligence on this domain
|
|
29
|
+
2. Use `hive_trending` filtered to this domain if possible
|
|
30
|
+
3. Present trends from the domain's perspective
|
|
31
|
+
|
|
32
|
+
**Mode C — Query-scoped (query argument):**
|
|
33
|
+
1. Use `hive_trending` filtered to the specified query
|
|
34
|
+
2. Present which URLs are gaining or losing for that query
|
|
35
|
+
|
|
36
|
+
**Present a summary of:**
|
|
37
|
+
- Biggest gainers (URLs climbing in rankings)
|
|
38
|
+
- Biggest losers (URLs dropping)
|
|
39
|
+
- New entries and exits
|
|
40
|
+
- Any patterns worth noting
|
|
41
|
+
|
|
42
|
+
If network data is sparse, suggest WebSearching relevant queries to contribute fresh data.
|
|
43
|
+
|
|
44
|
+
$ARGUMENTS
|