opencode-skills-collection 1.0.136 → 1.0.138
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/bundled-skills/.antigravity-install-manifest.json +29 -1
- package/bundled-skills/awareness-stage-mapper/SKILL.md +118 -0
- package/bundled-skills/brand-perception-psychologist/SKILL.md +115 -0
- package/bundled-skills/copywriting-psychologist/SKILL.md +124 -0
- package/bundled-skills/customer-psychographic-profiler/SKILL.md +127 -0
- package/bundled-skills/docs/integrations/jetski-cortex.md +3 -3
- package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md +1 -1
- package/bundled-skills/docs/maintainers/repo-growth-seo.md +3 -3
- package/bundled-skills/docs/maintainers/skills-update-guide.md +1 -1
- package/bundled-skills/docs/users/bundles.md +1 -1
- package/bundled-skills/docs/users/claude-code-skills.md +1 -1
- package/bundled-skills/docs/users/gemini-cli-skills.md +1 -1
- package/bundled-skills/docs/users/getting-started.md +1 -1
- package/bundled-skills/docs/users/kiro-integration.md +1 -1
- package/bundled-skills/docs/users/usage.md +4 -4
- package/bundled-skills/docs/users/visual-guide.md +4 -4
- package/bundled-skills/emotional-arc-designer/SKILL.md +128 -0
- package/bundled-skills/headline-psychologist/SKILL.md +117 -0
- package/bundled-skills/identity-mirror/SKILL.md +115 -0
- package/bundled-skills/jobs-to-be-done-analyst/SKILL.md +115 -0
- package/bundled-skills/loss-aversion-designer/SKILL.md +116 -0
- package/bundled-skills/objection-preemptor/SKILL.md +118 -0
- package/bundled-skills/onboarding-psychologist/SKILL.md +115 -0
- package/bundled-skills/pitch-psychologist/SKILL.md +118 -0
- package/bundled-skills/price-psychology-strategist/SKILL.md +114 -0
- package/bundled-skills/scarcity-urgency-psychologist/SKILL.md +115 -0
- package/bundled-skills/seo-aeo-blog-writer/SKILL.md +88 -0
- package/bundled-skills/seo-aeo-content-cluster/SKILL.md +89 -0
- package/bundled-skills/seo-aeo-content-quality-auditor/SKILL.md +93 -0
- package/bundled-skills/seo-aeo-internal-linking/SKILL.md +85 -0
- package/bundled-skills/seo-aeo-keyword-research/SKILL.md +113 -0
- package/bundled-skills/seo-aeo-landing-page-writer/SKILL.md +98 -0
- package/bundled-skills/seo-aeo-meta-description-generator/SKILL.md +87 -0
- package/bundled-skills/seo-aeo-schema-generator/SKILL.md +103 -0
- package/bundled-skills/sequence-psychologist/SKILL.md +115 -0
- package/bundled-skills/social-proof-architect/SKILL.md +117 -0
- package/bundled-skills/subject-line-psychologist/SKILL.md +114 -0
- package/bundled-skills/trust-calibrator/SKILL.md +116 -0
- package/bundled-skills/ux-persuasion-engineer/SKILL.md +115 -0
- package/bundled-skills/visual-emotion-engineer/SKILL.md +115 -0
- package/package.json +1 -1
|
@@ -0,0 +1,115 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: scarcity-urgency-psychologist
|
|
3
|
+
description: "One sentence - what this skill does and when to invoke it"
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-04"
|
|
7
|
+
---
|
|
8
|
+
You are a **Behavioral Psychologist specializing in motivation, reactance, and temporal decision-making**. Your task is to engineer genuine scarcity and urgency mechanics that create real psychological motivation to act now.
|
|
9
|
+
|
|
10
|
+
## When to Use
|
|
11
|
+
|
|
12
|
+
- Use when you need urgency or scarcity messaging that feels credible instead of manipulative.
|
|
13
|
+
- Use when timing, stock, access, or deadlines should push action without damaging trust.
|
|
14
|
+
|
|
15
|
+
## CONTEXT GATHERING
|
|
16
|
+
|
|
17
|
+
Before designing scarcity, establish:
|
|
18
|
+
|
|
19
|
+
1. **The Target Human** - psychographic profile, cynicism level, and trust stage.
|
|
20
|
+
2. **The Objective** - what action must happen now.
|
|
21
|
+
3. **The Output** - scarcity and urgency strategy.
|
|
22
|
+
4. **Constraints** - actual inventory, deadline truth, and ethics.
|
|
23
|
+
|
|
24
|
+
If the scarcity is not real, stop and ask for a different strategy.
|
|
25
|
+
|
|
26
|
+
## PSYCHOLOGICAL FRAMEWORK: GENUINE SCARCITY CALIBRATION
|
|
27
|
+
|
|
28
|
+
### Mechanism
|
|
29
|
+
Scarcity works when the audience believes the opportunity is genuinely limited and personally relevant. If the audience senses manipulation, psychological reactance rises and the tactic can backfire. Use only real scarcity, honest deadlines, and proportionate urgency (Worchel scarcity heuristic; Brehm reactance theory; Omar et al., 2021; Gong et al., 2021; Wang et al., 2025; Suvarna & Malagi, 2025).
|
|
30
|
+
|
|
31
|
+
### Execution Steps
|
|
32
|
+
|
|
33
|
+
**Step 1 - Verify the scarcity is real**
|
|
34
|
+
Check whether the limit is inventory, capacity, time, access, or attention.
|
|
35
|
+
*Research basis: fake scarcity destroys trust when detected (Omar et al., 2021; Wang et al., 2025).*
|
|
36
|
+
|
|
37
|
+
**Step 2 - Decide whether urgency is needed**
|
|
38
|
+
Not every scarce offer needs a deadline.
|
|
39
|
+
*Research basis: urgency is effective only when delay has a real cost (temporal discounting research; Brehm).*
|
|
40
|
+
|
|
41
|
+
**Step 3 - Match the frame to cynicism**
|
|
42
|
+
Use softer language when the audience is skeptical and stronger language when the limit is obvious.
|
|
43
|
+
*Research basis: reactance increases as the audience perceives pressure or manipulation (Grandpre et al., 2003; Quick et al., 2018).*
|
|
44
|
+
|
|
45
|
+
**Step 4 - State the consequence clearly**
|
|
46
|
+
Explain what happens if the user waits.
|
|
47
|
+
*Research basis: visible opportunity cost increases action more than vague urgency (Houdek, 2016; Suvarna & Malagi, 2025).*
|
|
48
|
+
|
|
49
|
+
**Step 5 - Keep the tone calm**
|
|
50
|
+
Avoid panic language.
|
|
51
|
+
*Research basis: high-pressure scarcity can trigger avoidance and doubt (Brehm; Lavoie & Quick, 2013).*
|
|
52
|
+
|
|
53
|
+
## DECISION MATRIX
|
|
54
|
+
|
|
55
|
+
### Variable: scarcity type
|
|
56
|
+
- If inventory-limited -> state the actual remaining quantity.
|
|
57
|
+
- If capacity-limited -> explain slots, seats, or bandwidth honestly.
|
|
58
|
+
- If time-limited -> explain the real deadline and why it exists.
|
|
59
|
+
- If access-limited -> explain the genuine window or eligibility.
|
|
60
|
+
|
|
61
|
+
### Variable: audience cynicism
|
|
62
|
+
- If high -> use transparent, minimal urgency.
|
|
63
|
+
- If medium -> combine clarity with consequence.
|
|
64
|
+
- If low -> you can be slightly more vivid, but still honest.
|
|
65
|
+
|
|
66
|
+
### Variable: category norm
|
|
67
|
+
- If urgency is expected -> a deadline can be effective.
|
|
68
|
+
- If urgency is unusual -> be especially careful.
|
|
69
|
+
- If urgency is common and abused -> use scarcity sparingly.
|
|
70
|
+
|
|
71
|
+
## FAILURE MODES - DO NOT DO THESE
|
|
72
|
+
|
|
73
|
+
**Failure Mode 1**
|
|
74
|
+
- Agents typically: invent scarcity.
|
|
75
|
+
- Why it fails psychologically: once the trick is detected, credibility drops sharply.
|
|
76
|
+
- Instead: use real limits only.
|
|
77
|
+
|
|
78
|
+
**Failure Mode 2**
|
|
79
|
+
- Agents typically: overuse countdowns and alarms.
|
|
80
|
+
- Why it fails psychologically: urgency fatigue makes people tune out.
|
|
81
|
+
- Instead: use the minimum urgent cue needed.
|
|
82
|
+
|
|
83
|
+
**Failure Mode 3**
|
|
84
|
+
- Agents typically: pair scarcity with aggressive pressure.
|
|
85
|
+
- Why it fails psychologically: reactance turns motivation into resistance.
|
|
86
|
+
- Instead: keep the tone calm and choice-preserving.
|
|
87
|
+
|
|
88
|
+
## ETHICAL GUARDRAILS
|
|
89
|
+
|
|
90
|
+
This skill must:
|
|
91
|
+
- Use real scarcity.
|
|
92
|
+
- Avoid fake deadlines and fake stock counts.
|
|
93
|
+
- Preserve choice and clarity.
|
|
94
|
+
|
|
95
|
+
The line between persuasion and manipulation is making a real opportunity timely versus manufacturing panic to force a purchase. Never cross it.
|
|
96
|
+
|
|
97
|
+
## SKILL CHAINING
|
|
98
|
+
|
|
99
|
+
Before invoking this skill, the agent should have completed:
|
|
100
|
+
- [ ] `@loss-aversion-designer`
|
|
101
|
+
- [ ] `@trust-calibrator`
|
|
102
|
+
|
|
103
|
+
This skill's output feeds into:
|
|
104
|
+
- [ ] `@copywriting-psychologist`
|
|
105
|
+
- [ ] `@sequence-psychologist`
|
|
106
|
+
- [ ] `@price-psychology-strategist`
|
|
107
|
+
|
|
108
|
+
## OUTPUT QUALITY CHECK
|
|
109
|
+
|
|
110
|
+
Before finalizing output, the agent asks:
|
|
111
|
+
- [ ] Is the scarcity real?
|
|
112
|
+
- [ ] Is urgency actually needed?
|
|
113
|
+
- [ ] Did I match the tone to the audience's cynicism?
|
|
114
|
+
- [ ] Did I avoid panic language?
|
|
115
|
+
- [ ] Does this preserve trust and autonomy?
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: seo-aeo-blog-writer
|
|
3
|
+
description: "Writes long-form blog posts with TL;DR block, definition sentence, comparison table, and 5-question FAQ for SEO ranking and AEO citation. Activate when the user wants to write a blog post, article, or long-form content piece."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-01"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# SEO-AEO Blog Writer
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
Writes structured long-form blog posts (800–3000 words) that satisfy both SEO ranking signals and AEO citation requirements. Every post includes a TL;DR direct-answer block, a definition sentence, structured H2/H3 hierarchy, a comparison table where relevant, and exactly 5 FAQ entries written for AI extraction.
|
|
14
|
+
|
|
15
|
+
Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- Use when writing a cluster article from a content cluster map
|
|
20
|
+
- Use when creating a long-form guide to build topical authority
|
|
21
|
+
- Use when you need content that can be cited by AI engines like Perplexity or ChatGPT
|
|
22
|
+
- Use when you need a blog post that follows a consistent, auditable structure
|
|
23
|
+
|
|
24
|
+
## How It Works
|
|
25
|
+
|
|
26
|
+
### Step 1: Write the TL;DR Block First
|
|
27
|
+
Write a 2–3 sentence direct answer to the article's core question. Place it immediately after the H1 in a blockquote. This is the first block AI engines attempt to extract.
|
|
28
|
+
|
|
29
|
+
### Step 2: Build the Heading Skeleton
|
|
30
|
+
Set H1, H2s (4–6), and H3s before writing any body content. The first H2 must be a "What Is" section with a clean definition sentence as its opening line.
|
|
31
|
+
|
|
32
|
+
### Step 3: Write Body Sections
|
|
33
|
+
Follow the section order: What Is → Why It Matters → How It Works (with H3 sub-concepts) → Practical Steps → Common Mistakes → FAQ → Conclusion.
|
|
34
|
+
|
|
35
|
+
### Step 4: Write 5 FAQ Entries
|
|
36
|
+
Use long-tail and secondary keywords as questions. Each answer must be under 50 words and self-contained — readable without any surrounding context.
|
|
37
|
+
|
|
38
|
+
### Step 5: Run AEO and SEO Checklists
|
|
39
|
+
Verify TL;DR presence, definition sentence, FAQ count, keyword placement, and heading structure before outputting.
|
|
40
|
+
|
|
41
|
+
## Examples
|
|
42
|
+
|
|
43
|
+
### Example: TL;DR Block
|
|
44
|
+
How to Manage a Remote Engineering Team
|
|
45
|
+
|
|
46
|
+
TL;DR: Managing a remote engineering team requires async
|
|
47
|
+
communication tools, clear documentation standards, and
|
|
48
|
+
timezone-aware sprint planning. Teams that nail these three
|
|
49
|
+
areas ship consistently regardless of where members are located.
|
|
50
|
+
|
|
51
|
+
|
|
52
|
+
### Example: FAQ Section
|
|
53
|
+
Q: What is the biggest challenge of remote engineering teams?
|
|
54
|
+
A: Async communication. Without shared hours, decisions slow down
|
|
55
|
+
and context gets lost. Teams that document decisions in writing
|
|
56
|
+
and use structured standup tools close this gap fastest.
|
|
57
|
+
Q: How do you run a daily standup with a remote team?
|
|
58
|
+
A: Use async video or text standups posted at the start of each
|
|
59
|
+
member's day. Tools like Loom or Slack threads work well.
|
|
60
|
+
Avoid live calls across more than 2 timezones.
|
|
61
|
+
|
|
62
|
+
## Best Practices
|
|
63
|
+
|
|
64
|
+
- ✅ **Do:** Write the TL;DR block before writing anything else — it anchors the article
|
|
65
|
+
- ✅ **Do:** Make the "What Is" definition sentence extractable on its own — one clean sentence
|
|
66
|
+
- ✅ **Do:** Use secondary keywords as FAQ questions to capture long-tail traffic
|
|
67
|
+
- ❌ **Don't:** Write FAQ answers longer than 50 words — AI engines skip long answers
|
|
68
|
+
- ❌ **Don't:** Use duplicate H2 headings anywhere in the article
|
|
69
|
+
- ❌ **Don't:** Skip the comparison table if the topic involves comparing options
|
|
70
|
+
|
|
71
|
+
## Common Pitfalls
|
|
72
|
+
|
|
73
|
+
- **Problem:** TL;DR block is too vague to be extracted as a direct answer
|
|
74
|
+
**Solution:** The TL;DR must answer the article's core question in 2–3 sentences. If it doesn't answer a specific question, rewrite it.
|
|
75
|
+
|
|
76
|
+
- **Problem:** FAQ answers reference "as mentioned above" or other context
|
|
77
|
+
**Solution:** Every FAQ answer must stand completely alone — no references to other parts of the article.
|
|
78
|
+
|
|
79
|
+
## Related Skills
|
|
80
|
+
|
|
81
|
+
- `@seo-aeo-content-cluster` — provides the topic and keyword for this article
|
|
82
|
+
- `@seo-aeo-content-quality-auditor` — audits the completed post for SEO and AEO signals
|
|
83
|
+
- `@seo-aeo-internal-linking` — maps links between this post and related pages
|
|
84
|
+
|
|
85
|
+
## Additional Resources
|
|
86
|
+
|
|
87
|
+
- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
|
|
88
|
+
- [Full Blog Writer SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/blog-writer/SKILL.md)
|
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: seo-aeo-content-cluster
|
|
3
|
+
description: "Builds a topical authority map with a pillar page, prioritised cluster articles, content types, internal link map, and content gap analysis. Activate when the user wants to build a content cluster, topic map, or content strategy."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-01"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# SEO-AEO Content Cluster
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
Maps out a complete topical authority structure around a pillar keyword. Produces a pillar page definition, 8–15 cluster articles sorted into Priority 1/2/3 tiers, a content type for each, an internal link map, and a content gap analysis identifying AEO opportunities competitors are missing.
|
|
14
|
+
|
|
15
|
+
Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- Use when building topical authority around a new subject
|
|
20
|
+
- Use when you need to know what to write next to support a pillar page
|
|
21
|
+
- Use when planning a content calendar for a niche
|
|
22
|
+
- Use when you want to identify AEO content gaps competitors are missing
|
|
23
|
+
|
|
24
|
+
## How It Works
|
|
25
|
+
|
|
26
|
+
### Step 1: Define the Pillar Page
|
|
27
|
+
Set the primary keyword, target audience, and word count target (2500–4000 words) for the pillar page that anchors the cluster.
|
|
28
|
+
|
|
29
|
+
### Step 2: Generate Cluster Articles
|
|
30
|
+
Produce 8–15 subtopics sorted into three priority tiers:
|
|
31
|
+
- **Priority 1** — High volume, clear intent. Write these first.
|
|
32
|
+
- **Priority 2** — Medium volume, long-tail focus. Write second.
|
|
33
|
+
- **Priority 3** — Low volume, high conversion intent. Write last.
|
|
34
|
+
|
|
35
|
+
Assign each article a unique keyword, content type, search intent, and link map.
|
|
36
|
+
|
|
37
|
+
### Step 3: Build Internal Link Map
|
|
38
|
+
Every cluster article must link back to the pillar page. No orphan articles. Show the full tree of relationships.
|
|
39
|
+
|
|
40
|
+
### Step 4: Run Content Gap Analysis
|
|
41
|
+
Identify angles that competitors likely miss — especially question-based AEO opportunities that AI engines commonly surface.
|
|
42
|
+
|
|
43
|
+
## Examples
|
|
44
|
+
|
|
45
|
+
### Example: Automated Budgeting Cluster
|
|
46
|
+
Pillar: The Complete Guide to Automated Budgeting
|
|
47
|
+
Priority 1:
|
|
48
|
+
|
|
49
|
+
How to Build a Budget That Actually Works | how-to guide
|
|
50
|
+
Best Budgeting Apps Compared | comparison
|
|
51
|
+
What Is Zero-Based Budgeting? | explainer ← AEO priority
|
|
52
|
+
|
|
53
|
+
Priority 2:
|
|
54
|
+
4. How to Automate Your Savings in 3 Steps | how-to guide
|
|
55
|
+
5. Budgeting for Millennials: What Nobody Tells You | opinion
|
|
56
|
+
Link Map:
|
|
57
|
+
Pillar ← Article 1, 2, 3, 4, 5
|
|
58
|
+
Article 1 ↔ Article 4
|
|
59
|
+
Article 2 → Article 3
|
|
60
|
+
AEO Priority:
|
|
61
|
+
★ Article 3 — "What Is" format has highest AI extraction probability
|
|
62
|
+
★ Article 2 — comparison table will be lifted for product queries
|
|
63
|
+
|
|
64
|
+
## Best Practices
|
|
65
|
+
|
|
66
|
+
- ✅ **Do:** Assign every cluster article a unique target keyword — no overlap
|
|
67
|
+
- ✅ **Do:** Include at least one FAQ page and one comparison article in every cluster
|
|
68
|
+
- ✅ **Do:** Flag the 2 highest AEO-opportunity articles for priority writing
|
|
69
|
+
- ❌ **Don't:** Let any article become an orphan — every article links to at least one other
|
|
70
|
+
- ❌ **Don't:** Target the same keyword on both the pillar and a cluster article
|
|
71
|
+
|
|
72
|
+
## Common Pitfalls
|
|
73
|
+
|
|
74
|
+
- **Problem:** Cluster articles all target similar keywords and cannibalise each other
|
|
75
|
+
**Solution:** Run a uniqueness check — every article needs a distinct keyword with no semantic overlap.
|
|
76
|
+
|
|
77
|
+
- **Problem:** No AEO content in the cluster
|
|
78
|
+
**Solution:** At least 2 articles must be structured as direct-answer pages (FAQ or "What Is" explainer).
|
|
79
|
+
|
|
80
|
+
## Related Skills
|
|
81
|
+
|
|
82
|
+
- `@seo-aeo-keyword-research` — provides the keyword foundation for the cluster
|
|
83
|
+
- `@seo-aeo-blog-writer` — writes the Priority 1 cluster articles
|
|
84
|
+
- `@seo-aeo-internal-linking` — builds the detailed link map from cluster output
|
|
85
|
+
|
|
86
|
+
## Additional Resources
|
|
87
|
+
|
|
88
|
+
- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
|
|
89
|
+
- [Full Content Cluster SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/content-cluster/SKILL.md)
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: seo-aeo-content-quality-auditor
|
|
3
|
+
description: "Audits content for SEO and AEO performance with scored reports, severity-ranked fix lists, and projected scores after fixes. Activate when the user wants to audit, review, or score content for SEO or AEO compliance."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-01"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# SEO-AEO Content Quality Auditor
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
Runs a dual SEO + AEO audit on any landing page or blog post. Produces an overall score, SEO score, AEO score, and readability score — each out of 100 — with severity-ranked issue lists (Critical / Warning / Polish), exact fix instructions for every issue, and projected scores after all fixes are applied.
|
|
14
|
+
|
|
15
|
+
Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- Use when auditing a landing page or blog post before publishing
|
|
20
|
+
- Use after the blog-writer or landing-page-writer skill outputs content
|
|
21
|
+
- Use when diagnosing why existing content is underperforming in search
|
|
22
|
+
- Use when you need a scored, actionable SEO and AEO report
|
|
23
|
+
|
|
24
|
+
## How It Works
|
|
25
|
+
|
|
26
|
+
### Step 1: Run SEO Checks
|
|
27
|
+
Verify keyword density, H1/H2/H3 structure, meta elements, word count, sentence length, and paragraph density. Flag every issue with its severity.
|
|
28
|
+
|
|
29
|
+
### Step 2: Run AEO Checks
|
|
30
|
+
Check for TL;DR block, definition sentence, FAQ section (minimum 4 entries), bullet and numbered lists, comparison table, and extractable direct answers. Score each signal as found or missing.
|
|
31
|
+
|
|
32
|
+
### Step 3: Run Readability Checks
|
|
33
|
+
Check passive voice ratio, transition word presence, wall-of-text paragraphs, subheading frequency, and reading level.
|
|
34
|
+
|
|
35
|
+
### Step 4: Score and Prioritise
|
|
36
|
+
Calculate three scores out of 100. Sort all issues into Critical (fix before publishing), Important (fix soon), and Polish (optional improvements). Generate projected scores after all fixes are applied.
|
|
37
|
+
|
|
38
|
+
## Scoring System
|
|
39
|
+
|
|
40
|
+
| Score | Status | Label |
|
|
41
|
+
|-------|--------|-------|
|
|
42
|
+
| 85–100 | ✅ Pass | Strong |
|
|
43
|
+
| 70–84 | ⚠️ Warn | Acceptable |
|
|
44
|
+
| 50–69 | 🔶 Weak | Needs work |
|
|
45
|
+
| 0–49 | ❌ Fail | Do not publish |
|
|
46
|
+
|
|
47
|
+
## Examples
|
|
48
|
+
|
|
49
|
+
### Example: Audit Summary
|
|
50
|
+
Overall Score: 84/100 ⚠️ Acceptable
|
|
51
|
+
SEO Score: 88/100 ✅ Pass
|
|
52
|
+
AEO Score: 74/100 ⚠️ Acceptable
|
|
53
|
+
Readability: 91/100 ✅ Pass
|
|
54
|
+
Verdict: Strong SEO foundation. AEO needs a TL;DR block
|
|
55
|
+
and one more FAQ entry before publishing.
|
|
56
|
+
🔴 Critical (fix before publishing):
|
|
57
|
+
|
|
58
|
+
AEO: No TL;DR block found
|
|
59
|
+
Fix: Add a 2–3 sentence direct-answer block in a
|
|
60
|
+
blockquote immediately after the H1.
|
|
61
|
+
|
|
62
|
+
🟡 Important (fix soon):
|
|
63
|
+
2. AEO: FAQ has 3 entries — minimum is 4
|
|
64
|
+
Fix: Add one more FAQ entry using a secondary keyword
|
|
65
|
+
as the question.
|
|
66
|
+
Projected score after fixes: 93/100 ✅
|
|
67
|
+
|
|
68
|
+
## Best Practices
|
|
69
|
+
|
|
70
|
+
- ✅ **Do:** Fix all Critical issues before publishing — they block AEO extraction
|
|
71
|
+
- ✅ **Do:** Use the projected score to prioritise which fixes to make first
|
|
72
|
+
- ✅ **Do:** Run the audit on both the landing page and blog post in the same session
|
|
73
|
+
- ❌ **Don't:** Publish content scoring below 50/100 overall
|
|
74
|
+
- ❌ **Don't:** Ignore AEO warnings — they directly affect AI engine citation probability
|
|
75
|
+
|
|
76
|
+
## Common Pitfalls
|
|
77
|
+
|
|
78
|
+
- **Problem:** SEO score is high but AEO score is low
|
|
79
|
+
**Solution:** Traditional SEO tools miss AEO signals entirely. Run the AEO checklist separately and treat it as equally important.
|
|
80
|
+
|
|
81
|
+
- **Problem:** Fix list is long and overwhelming
|
|
82
|
+
**Solution:** Work through Critical issues only first, re-run the audit, then tackle Important issues.
|
|
83
|
+
|
|
84
|
+
## Related Skills
|
|
85
|
+
|
|
86
|
+
- `@seo-aeo-blog-writer` — produces the content this skill audits
|
|
87
|
+
- `@seo-aeo-landing-page-writer` — produces landing pages this skill audits
|
|
88
|
+
- `@seo-aeo-schema-generator` — uses audit output to determine schema priorities
|
|
89
|
+
|
|
90
|
+
## Additional Resources
|
|
91
|
+
|
|
92
|
+
- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
|
|
93
|
+
- [Full Content Quality Auditor SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/content-quality-auditor/SKILL.md)
|
|
@@ -0,0 +1,85 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: seo-aeo-internal-linking
|
|
3
|
+
description: "Maps internal link opportunities between pages with anchor text, placement instructions, orphan page detection, and cannibalization checks. Activate when the user wants to build an internal linking strategy or find link opportunities."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-01"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# SEO-AEO Internal Linking
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
Analyses a set of pages and produces a prioritised list of internal link opportunities with exact anchor text, a context sentence showing where each link should appear, orphan page detection, anchor text cannibalization warnings, and a link equity map showing how authority flows across the content.
|
|
14
|
+
|
|
15
|
+
Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- Use when building internal links between a new pillar page and its cluster articles
|
|
20
|
+
- Use when auditing an existing site for orphan pages
|
|
21
|
+
- Use after content-cluster generates a topic map
|
|
22
|
+
- Use when you need anchor text suggestions with placement context
|
|
23
|
+
|
|
24
|
+
## How It Works
|
|
25
|
+
|
|
26
|
+
### Step 1: Detect Orphan Pages
|
|
27
|
+
Flag any page with zero incoming internal links. These are invisible to search engines and must be linked immediately.
|
|
28
|
+
|
|
29
|
+
### Step 2: Build Semantic Overlap Matrix
|
|
30
|
+
Match pages by primary keyword similarity and content summary to identify natural linking opportunities.
|
|
31
|
+
|
|
32
|
+
### Step 3: Assign Link Types
|
|
33
|
+
Every suggestion gets one of four labels:
|
|
34
|
+
- **Cluster → Pillar** — highest priority, consolidates authority upward
|
|
35
|
+
- **Pillar → Cluster** — distributes authority downward
|
|
36
|
+
- **Cluster → Cluster** — builds semantic depth
|
|
37
|
+
- **Contextual Boost** — concentrates equity on a focus page
|
|
38
|
+
|
|
39
|
+
### Step 4: Write Context Sentences
|
|
40
|
+
For every link opportunity, write the sentence the anchor text should appear in — naturally placed, not forced.
|
|
41
|
+
|
|
42
|
+
### Step 5: Check Anchor Text
|
|
43
|
+
Flag any exact-match anchor used more than once for the same target page as a cannibalization risk. Never use generic anchors like "click here".
|
|
44
|
+
|
|
45
|
+
## Examples
|
|
46
|
+
|
|
47
|
+
### Example: Link Opportunity Output
|
|
48
|
+
🔴 High Priority — Link 1
|
|
49
|
+
Type: Cluster → Pillar
|
|
50
|
+
Source: "How to Build a Budget That Actually Works"
|
|
51
|
+
Target: "The Complete Guide to Automated Budgeting"
|
|
52
|
+
Anchor: "automated budgeting guide"
|
|
53
|
+
Context: "For a full breakdown of every method available,
|
|
54
|
+
see our [automated budgeting guide]."
|
|
55
|
+
Impact: Consolidates topical authority on pillar page.
|
|
56
|
+
Orphan Alert:
|
|
57
|
+
"PennyWise Pricing Page" has no incoming links.
|
|
58
|
+
Fix: Add link from comparison table in Article 2.
|
|
59
|
+
|
|
60
|
+
## Best Practices
|
|
61
|
+
|
|
62
|
+
- ✅ **Do:** Every cluster article must have at least one Cluster → Pillar link
|
|
63
|
+
- ✅ **Do:** Write a context sentence for every suggestion — anchor text needs natural placement
|
|
64
|
+
- ✅ **Do:** Fix orphan pages before adding any new links
|
|
65
|
+
- ❌ **Don't:** Use the same exact-match anchor for the same target page more than once
|
|
66
|
+
- ❌ **Don't:** Use "click here", "read more", or "learn more" as anchor text — ever
|
|
67
|
+
- ❌ **Don't:** Add more than 100 outgoing internal links on any single page
|
|
68
|
+
|
|
69
|
+
## Common Pitfalls
|
|
70
|
+
|
|
71
|
+
- **Problem:** All cluster articles link to the pillar but not to each other
|
|
72
|
+
**Solution:** Add Cluster → Cluster links between semantically related articles to build depth.
|
|
73
|
+
|
|
74
|
+
- **Problem:** Same anchor text used across multiple pages for the same target
|
|
75
|
+
**Solution:** Use partial match and branded anchors for subsequent links after the first exact-match use.
|
|
76
|
+
|
|
77
|
+
## Related Skills
|
|
78
|
+
|
|
79
|
+
- `@seo-aeo-content-cluster` — generates the cluster map this skill links together
|
|
80
|
+
- `@seo-aeo-schema-generator` — uses link map output for BreadcrumbList schema
|
|
81
|
+
|
|
82
|
+
## Additional Resources
|
|
83
|
+
|
|
84
|
+
- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
|
|
85
|
+
- [Full Internal Linking SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/internal-linking/SKILL.md)
|
|
@@ -0,0 +1,113 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: seo-aeo-keyword-research
|
|
3
|
+
description: "Researches and prioritises SEO keywords with AEO question queries, difficulty tiers, cannibalization checks, and a content map. Activate when the user wants to find keywords, research search terms, or build a keyword strategy."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-01"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# SEO-AEO Keyword Research
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
Identifies high-value SEO keywords and AEO question-based queries for a topic. Produces keyword tiers (easy wins to long-term goals), search intent classification, cannibalization checks, and a content production map — all from a single topic input.
|
|
14
|
+
|
|
15
|
+
Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine) — an open-source AI-powered content growth system.
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- Use when you need to build a keyword strategy for a new topic or niche
|
|
20
|
+
- Use when you want to find AEO question queries for AI engine citation
|
|
21
|
+
- Use when you need to prioritise which keywords to target first
|
|
22
|
+
- Use when you want to check for keyword cannibalization before writing content
|
|
23
|
+
|
|
24
|
+
## How It Works
|
|
25
|
+
|
|
26
|
+
### Step 1: Extract Seed Keywords
|
|
27
|
+
Identify 3–5 core terms that anchor the topic's search territory. Go beyond the obvious head term to include adjacent terms the audience actually uses.
|
|
28
|
+
|
|
29
|
+
### Step 2: Expand Into Tiers
|
|
30
|
+
Sort all keywords into three tiers:
|
|
31
|
+
- **Tier 1** — Low-to-moderate difficulty. Target first.
|
|
32
|
+
- **Tier 2** — Medium difficulty. Build toward after Tier 1 content is live.
|
|
33
|
+
- **Tier 3** — High difficulty. Long-term goals only.
|
|
34
|
+
|
|
35
|
+
### Step 3: Generate AEO Keywords
|
|
36
|
+
Produce question-based keywords that AI engines surface in direct answers and People Also Ask boxes. For each AEO keyword, specify the answer format to use (definition sentence, numbered steps, comparison table, direct number).
|
|
37
|
+
|
|
38
|
+
### Step 4: Run Cannibalization Check
|
|
39
|
+
Flag any two keywords similar enough to split traffic if targeted on separate pages. Recommend which page should own which term.
|
|
40
|
+
|
|
41
|
+
### Step 5: Build Content Map
|
|
42
|
+
Recommend content type and production order for all Tier 1 and Tier 2 keywords.
|
|
43
|
+
|
|
44
|
+
## Examples
|
|
45
|
+
|
|
46
|
+
### Example 1: SaaS Product
|
|
47
|
+
Input: topic = "remote project management software"
|
|
48
|
+
audience = "engineering managers and startup founders"
|
|
49
|
+
goal = "convert"
|
|
50
|
+
Output:
|
|
51
|
+
Tier 1 Keywords:
|
|
52
|
+
|
|
53
|
+
"remote project management software" | Medium volume | Difficulty: 38
|
|
54
|
+
"project management tool remote teams" | Low volume | Difficulty: 29
|
|
55
|
+
|
|
56
|
+
AEO Keywords:
|
|
57
|
+
|
|
58
|
+
"What is the best project management software for remote teams?"
|
|
59
|
+
→ Answer format: Comparison table
|
|
60
|
+
"How does remote project management work?"
|
|
61
|
+
→ Answer format: Numbered steps
|
|
62
|
+
|
|
63
|
+
Content Map:
|
|
64
|
+
|
|
65
|
+
Landing page → "remote project management software"
|
|
66
|
+
Pillar blog → "complete guide to remote project management"
|
|
67
|
+
Cluster article → "how to manage remote engineering teams"
|
|
68
|
+
|
|
69
|
+
|
|
70
|
+
### Example 2: Fintech App
|
|
71
|
+
Input: topic = "automated budgeting app"
|
|
72
|
+
audience = "millennials managing personal finances"
|
|
73
|
+
goal = "all"
|
|
74
|
+
Output:
|
|
75
|
+
Tier 1 Keywords:
|
|
76
|
+
|
|
77
|
+
"automated budgeting app" | Medium volume | Difficulty: 33
|
|
78
|
+
"automatic savings app" | Low volume | Difficulty: 24
|
|
79
|
+
|
|
80
|
+
AEO Keywords:
|
|
81
|
+
|
|
82
|
+
"What is the best budgeting app for millennials?"
|
|
83
|
+
→ Answer format: Comparison table
|
|
84
|
+
"How does automated budgeting work?"
|
|
85
|
+
→ Answer format: Numbered steps
|
|
86
|
+
|
|
87
|
+
|
|
88
|
+
## Best Practices
|
|
89
|
+
|
|
90
|
+
- ✅ **Do:** Target Tier 1 keywords first — build authority before going after competitive terms
|
|
91
|
+
- ✅ **Do:** Use AEO keywords in FAQ sections and definition blocks for AI engine citation
|
|
92
|
+
- ✅ **Do:** Validate estimated volume and difficulty with a live tool (Ahrefs, SEMrush) before committing
|
|
93
|
+
- ❌ **Don't:** Target two keywords on the same page if cannibalization is flagged
|
|
94
|
+
- ❌ **Don't:** Use volume as the only prioritisation signal — difficulty and intent matter more
|
|
95
|
+
|
|
96
|
+
## Common Pitfalls
|
|
97
|
+
|
|
98
|
+
- **Problem:** High-volume keyword chosen but impossible to rank for early on
|
|
99
|
+
**Solution:** Always cross-check volume with difficulty. Tier 1 should have difficulty under 45.
|
|
100
|
+
|
|
101
|
+
- **Problem:** AEO keywords ignored in favour of traditional search terms
|
|
102
|
+
**Solution:** AEO keywords drive AI engine citation — include at least 5 in every research run.
|
|
103
|
+
|
|
104
|
+
## Related Skills
|
|
105
|
+
|
|
106
|
+
- `@seo-aeo-content-cluster` — uses keyword research output to build topic cluster
|
|
107
|
+
- `@seo-aeo-landing-page-writer` — consumes primary keyword to generate landing page
|
|
108
|
+
- `@seo-aeo-blog-writer` — uses secondary keywords for cluster article targeting
|
|
109
|
+
|
|
110
|
+
## Additional Resources
|
|
111
|
+
|
|
112
|
+
- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
|
|
113
|
+
- [Full Keyword Research SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/keyword-research/SKILL.md)
|
|
@@ -0,0 +1,98 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: seo-aeo-landing-page-writer
|
|
3
|
+
description: "Writes complete, structured landing pages optimized for SEO ranking, AEO citation, and visitor conversion. Activate when the user wants to write or generate a landing page for a product, service, or offer."
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-01"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# SEO-AEO Landing Page Writer
|
|
10
|
+
|
|
11
|
+
## Overview
|
|
12
|
+
|
|
13
|
+
Generates a full, publish-ready landing page following a defined section order with SEO heading structure, AEO extraction blocks, FAQ section, comparison table, social proof, and conversion-focused CTAs. Every section serves a specific purpose in a narrative arc that moves the visitor from awareness to action.
|
|
14
|
+
|
|
15
|
+
Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
|
|
16
|
+
|
|
17
|
+
## When to Use This Skill
|
|
18
|
+
|
|
19
|
+
- Use when building a landing page for a new product or service
|
|
20
|
+
- Use when an existing landing page needs a full SEO and AEO rewrite
|
|
21
|
+
- Use when you need a page that can be cited by AI engines like Perplexity or ChatGPT
|
|
22
|
+
- Use when you want conversion copy that leads with pain before pitching the product
|
|
23
|
+
|
|
24
|
+
## How It Works
|
|
25
|
+
|
|
26
|
+
### Step 1: Map Inputs
|
|
27
|
+
Extract product name, audience, primary keyword, pain points, features, benefits, USPs, social proof, and CTAs. Map every feature to a user outcome before writing any copy.
|
|
28
|
+
|
|
29
|
+
### Step 2: Write AEO Extraction Sentence
|
|
30
|
+
Write one 25–40 word sentence that answers "What is [product]?" — standalone, no jargon, placed in a blockquote immediately after the H1. This is the sentence AI engines extract.
|
|
31
|
+
|
|
32
|
+
### Step 3: Follow the Narrative Arc
|
|
33
|
+
Write sections in this exact order:
|
|
34
|
+
1. Hero — H1 + AEO sentence + CTA
|
|
35
|
+
2. Problem — audience pain, no product mention yet
|
|
36
|
+
3. Solution — introduce product as the answer
|
|
37
|
+
4. Features as Benefits — table format
|
|
38
|
+
5. Social Proof — testimonials, logos, stats
|
|
39
|
+
6. Mid-page CTA
|
|
40
|
+
7. How It Works — numbered steps
|
|
41
|
+
8. Comparison — table with honest competitor comparison
|
|
42
|
+
9. FAQ — minimum 6 entries, each under 50 words
|
|
43
|
+
10. Trust Signals
|
|
44
|
+
11. Final CTA
|
|
45
|
+
|
|
46
|
+
### Step 4: Run SEO and AEO Checklists
|
|
47
|
+
Verify keyword placement, heading hierarchy, FAQ count, AEO block presence, and meta description placeholder before outputting.
|
|
48
|
+
|
|
49
|
+
## Examples
|
|
50
|
+
|
|
51
|
+
### Example 1: Hero Section Output
|
|
52
|
+
Ship Faster With Your Remote Team
|
|
53
|
+
|
|
54
|
+
Syncro is a remote-first project management platform that helps
|
|
55
|
+
distributed engineering teams track work, communicate
|
|
56
|
+
asynchronously, and ship without the chaos of email and
|
|
57
|
+
scattered spreadsheets.
|
|
58
|
+
|
|
59
|
+
[Start Free Trial] [See How It Works]
|
|
60
|
+
"4,000+ remote teams" · "40% fewer status meetings" · "4.8/5 on G2"
|
|
61
|
+
|
|
62
|
+
### Example 2: FAQ Section Output
|
|
63
|
+
Q: What is Syncro?
|
|
64
|
+
A: Syncro is a remote-first project management platform for
|
|
65
|
+
distributed engineering teams. It centralises task tracking,
|
|
66
|
+
async communication, and sprint planning in one tool.
|
|
67
|
+
Q: How much does Syncro cost?
|
|
68
|
+
A: Syncro offers a flat-rate plan at $49/month for unlimited
|
|
69
|
+
users. A 14-day free trial is available — no credit card required.
|
|
70
|
+
|
|
71
|
+
## Best Practices
|
|
72
|
+
|
|
73
|
+
- ✅ **Do:** Write the problem section before mentioning the product — empathy first
|
|
74
|
+
- ✅ **Do:** Place the AEO extraction sentence in a blockquote immediately after H1
|
|
75
|
+
- ✅ **Do:** Write FAQ answers as standalone — each must make sense without context
|
|
76
|
+
- ✅ **Do:** Include at least one honest point in the comparison table where the alternative wins
|
|
77
|
+
- ❌ **Don't:** Use "revolutionary", "game-changing", or "best-in-class" anywhere
|
|
78
|
+
- ❌ **Don't:** Use "Submit" or "Click Here" as CTA button text
|
|
79
|
+
- ❌ **Don't:** Write paragraphs longer than 4 lines
|
|
80
|
+
|
|
81
|
+
## Common Pitfalls
|
|
82
|
+
|
|
83
|
+
- **Problem:** Product mentioned in the pain section
|
|
84
|
+
**Solution:** The pain section exists to build empathy. Save the product introduction for the solution section.
|
|
85
|
+
|
|
86
|
+
- **Problem:** FAQ answers are too long to be extracted by AI engines
|
|
87
|
+
**Solution:** Every FAQ answer must be under 50 words and self-contained.
|
|
88
|
+
|
|
89
|
+
## Related Skills
|
|
90
|
+
|
|
91
|
+
- `@seo-aeo-keyword-research` — provides the primary keyword and AEO queries
|
|
92
|
+
- `@seo-aeo-meta-description-generator` — writes title and meta description from page output
|
|
93
|
+
- `@seo-aeo-content-quality-auditor` — audits the completed landing page
|
|
94
|
+
|
|
95
|
+
## Additional Resources
|
|
96
|
+
|
|
97
|
+
- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
|
|
98
|
+
- [Full Landing Page Writer SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/landing-page-writer/SKILL.md)
|