SEO Dataforseo
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
Researches and prioritises keywords from the site context and live search intent, including problem queries, question queries, difficulty tiers, and a content map.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-keyword-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-aeo-keyword-research .claude/skills/seo-aeo-keyword-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "seo-aeo-keyword-research" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-research into .claude/skills/seo-aeo-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-keyword-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-keyword-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo-aeo-keyword-research .agents/skills/seo-aeo-keyword-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seo-aeo-keyword-research" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-research into .agents/skills/seo-aeo-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-keyword-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-keyword-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo-aeo-keyword-research .cursor/skills/seo-aeo-keyword-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seo-aeo-keyword-research" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-research into .cursor/skills/seo-aeo-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-keyword-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/seo-aeo-keyword-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-keyword-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo-aeo-keyword-research .gemini/skills/seo-aeo-keyword-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "seo-aeo-keyword-research" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-research into .gemini/skills/seo-aeo-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-keyword-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-keyword-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo-aeo-keyword-research .github/skills/seo-aeo-keyword-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "seo-aeo-keyword-research" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-research into .github/skills/seo-aeo-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-keyword-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-keyword-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo-aeo-keyword-research .opencode/skills/seo-aeo-keyword-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seo-aeo-keyword-research" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-keyword-research into .opencode/skills/seo-aeo-keyword-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-keyword-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
seo-aeo-keyword-researchResearches and prioritises keywords from the site context and live search intent, including problem queries, question queries, difficulty tiers, and a content map.
SEO Aeo Keyword Research is an agent skill from sickn33/agentic-awesome-skills. Researches and prioritises keywords from the site context and live search intent, including problem queries, question queries, difficulty tiers, and a content map.
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Keyword research and AI search optimization. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
SEO Aeo Keyword Research loads about 3.9k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 894 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 894 words, ~3,890 tokens.
.claude/skills/seo-aeo-keyword-research/SKILL.md (or your agent's skills folder).Activate this skill when the user wants to research, identify, or prioritise keywords for a topic, niche, or website. Trigger phrases include: "keyword research", "find keywords for", "what should I rank for", "keyword analysis", "best keywords for [topic]", "keyword strategy", "what are people searching for about [topic]", "SEO keywords for [niche]".
{
"topic": "string — the subject to research keywords for",
"business_type": "string — what the business or site does",
"target_audience": "string — who the content is for",
"content_goal": "rank | convert | educate | all",
"location": "string — optional, country or city for local SEO",
"intent_focus": "informational | transactional |
commercial | navigational | all",
"competitor_urls": ["string — optional, up to 3 competitor URLs
to inform keyword gaps"],
"user_keywords": ["string — optional keywords the owner already cares about"],
"site_context": "string — optional audit findings, page list, or product description",
"research_mode": "browser | api | both | unavailable — default both"
}Start by asking the owner which keywords, products, audiences, locations, and business outcomes matter. If they do not know, derive provisional candidates from the site, audit findings, competitor language, and observed search results. Do not silently replace owner-supplied priorities with guessed keywords.
Use both browser research and available search/keyword APIs when the environment supports them. Prefer APIs for repeatable data and browser inspection for actual result-page intent, related questions, snippets, and current wording. If only one is available, state which source was used. If neither is available, perform semantic research only and mark volume, difficulty, rankings, and SERP observations as unverified.
For each important query, record:
Prioritize problem-related queries that the product can genuinely solve. Search intent outranks attractive but irrelevant volume.
Important: This skill estimates difficulty and volume based on semantic analysis and competitive signals. It does not connect to live data APIs. All figures are directional estimates, not verified data. Always validate with a live tool (Ahrefs, SEMrush, Google Keyword Planner) before committing to a full content strategy.
| Score | Label | Meaning |
|---|---|---|
| 0–20 | Easy | Low competition, newer or niche keyword |
| 21–40 | Moderate | Some established content exists, beatable with quality |
| 41–60 | Competitive | Strong content exists, needs solid authority |
| 61–80 | Hard | Dominated by high-authority sites |
| 81–100 | Very Hard | Reserved for the biggest players — avoid early on |
| Label | Range |
|---|---|
| Very High | 100,000+ |
| High | 10,000–99,999 |
| Medium | 1,000–9,999 |
| Low | 100–999 |
| Very Low | Under 100 |
CPC (Cost Per Click) signals commercial value even for organic content. Use it to prioritise keywords where advertisers are spending — this means the intent is likely transactional and conversions are valuable.
| CPC Range | Signal |
|---|---|
| $0–$1 | Low commercial value, good for awareness content |
| $1–$5 | Moderate value, mix of info and commercial intent |
| $5–$15 | High commercial value, strong conversion potential |
| $15+ | Very high value — transactional, competitive space |
The skill must always produce output in this exact format:
# Keyword Research Report
**Topic:** [topic]
**Business Type:** [business_type]
**Target Audience:** [target_audience]
**Content Goal:** [content_goal]
**Location:** [location or "Global"]
**Note:** All volume and difficulty figures are estimates.
Validate with a live keyword tool before final decisions.
---
## Seed Keywords
Core terms that define the topic's search territory:
| Seed Keyword | Est. Volume | Difficulty | CPC Est. | Intent |
|----------------------|-------------|------------|----------|-----------------|
| [keyword] | [label] | [score] | [$x] | [intent type] |
| [keyword] | [label] | [score] | [$x] | [intent type] |
| [keyword] | [label] | [score] | [$x] | [intent type] |
---
## Priority Keyword Tiers
### 🟢 Tier 1 — Target First (High Value, Achievable)
Low-to-moderate difficulty. Should anchor your first
wave of content.
| Keyword | Est. Volume | Difficulty | CPC Est. | Intent | Content Type to Create |
|----------------------|-------------|------------|----------|---------------|-------------------------|
| [keyword] | [label] | [score] | [$x] | [intent] | [landing page / blog] |
| [keyword] | [label] | [score] | [$x] | [intent] | [content type] |
| [keyword] | [label] | [score] | [$x] | [intent] | [content type] |
---
### 🟡 Tier 2 — Build Toward (Medium Difficulty)
Competitive but winnable with topical authority.
Target after Tier 1 content is live.
| Keyword | Est. Volume | Difficulty | CPC Est. | Intent | Content Type to Create |
|----------------------|-------------|------------|----------|---------------|-------------------------|
| [keyword] | [label] | [score] | [$x] | [intent] | [content type] |
| [keyword] | [label] | [score] | [$x] | [intent] | [content type] |
---
### 🔴 Tier 3 — Long-Term Goals (High Difficulty)
Dominated by high-authority sites. Do not target these
until significant topical authority is established.
| Keyword | Est. Volume | Difficulty | CPC Est. | Intent | Notes |
|----------------------|-------------|------------|----------|---------------|-------------------------|
| [keyword] | [label] | [score] | [$x] | [intent] | [why it's hard] |
---
## Long-Tail Keywords
Lower volume, lower difficulty, higher conversion rate.
These are your fastest wins.
| Long-Tail Keyword | Est. Volume | Difficulty | Intent | Best For |
|--------------------------------------|-------------|------------|---------------|-----------------------|
| [keyword] | [label] | [score] | [intent] | [blog / landing page] |
| [keyword] | [label] | [score] | [intent] | [content type] |
| [keyword] | [label] | [score] | [intent] | [content type] |
| [keyword] | [label] | [score] | [intent] | [content type] |
| [keyword] | [label] | [score] | [intent] | [content type] |
---
## AEO Keywords
Question-based and conversational keywords that AI engines
surface in direct answers, featured snippets, and
People Also Ask boxes.
| AEO Keyword / Question | Est. Volume | Intent | Answer Format to Use |
|------------------------------------------------|-------------|---------------|------------------------|
| What is [topic]? | [label] | informational | Definition sentence |
| How does [topic] work? | [label] | informational | Numbered steps |
| What is the best [topic] for [audience]? | [label] | commercial | Comparison table |
| How much does [topic] cost? | [label] | transactional | Direct number + range |
| [topic] vs [alternative] — which is better? | [label] | commercial | Comparison block |
| Is [topic] worth it? | [label] | commercial | FAQ answer block |
| [Common question your audience asks] | [label] | [intent] | [format] |
| [Common question your audience asks] | [label] | [intent] | [format] |
---
## LSI and Semantic Keywords
Related terms that reinforce topical authority.
Use these naturally throughout content —
do not force them as primary targets.
- [LSI term 1]
- [LSI term 2]
- [LSI term 3]
- [LSI term 4]
- [LSI term 5]
- [LSI term 6]
---
## Keywords to Avoid
These keywords are flagged as high-risk or low-ROI
for this topic and audience:
| Keyword | Reason to Avoid |
|----------------------|--------------------------------------------------------|
| [keyword] | Wrong intent — attracts audience not looking to convert|
| [keyword] | Too broad — dominated by global brands |
| [keyword] | Cannibalises [other keyword] — similar enough to split traffic |
| [keyword] | Seasonal — only relevant [month/period] |
---
## Cannibalization Check
Keywords with enough overlap that two pages targeting
them would compete against each other:
| Keyword A | Keyword B | Risk Level | Resolution |
|----------------------|----------------------|------------|-------------------------------------|
| [keyword] | [keyword] | High/Med | [which page should own which term] |
If none detected: ✅ No cannibalization risks found.
---
## Keyword → Content Map
Recommended content to create based on this research,
in production order:
| Priority | Content Title | Target Keyword | Content Type | Goal |
|----------|----------------------------------|-------------------|------------------|-------------------|
| 1 | [title] | [keyword] | Landing Page | Convert |
| 2 | [title] | [keyword] | Pillar Blog Post | Rank + Authority |
| 3 | [title] | [keyword] | Cluster Article | Topical Depth |
| 4 | [title] | [keyword] | Cluster Article | AEO / Snippet |
| 5 | [title] | [keyword] | FAQ Page | AEO / Long-tail |
---
## Quick Wins Summary
The 3 keywords to act on immediately:
1. **[keyword]** — [one sentence on why this is the best
first target]
2. **[keyword]** — [one sentence on why]
3. **[keyword]** — [one sentence on why]Recommend between 5 and 10 foundational pages, defaulting to 10 when the topic has enough distinct intent. Include the landing page when it is a target page, then assign each page a problem, query, intent, conversion path, supporting evidence, and internal-link targets.
| # | Page / Article | Primary Query | Problem Solved | Intent | Conversion Path | Evidence |
|---|---|---|---|---|---|---|
| 1 | [title] | [query] | [problem] | [intent] | [CTA/product page] | [source/confidence] |
Do not fill the table with near-duplicates to reach ten. If fewer than five distinct intents are defensible, explain why and ask whether the owner prefers a smaller foundation or broader adjacent topics.
| Query | Market / Date | Dominant SERP Intent | Ranking Formats | User Problem | Source | Confidence |
|---|---|---|---|---|---|---|
| [query] | [market/date] | [intent] | [formats] | [problem] | [browser/API/semantic] | High/Med/Low |
topic, business_type, site_context, and any
user_keywords together to define
the full semantic territory — not just the obvious
head term but adjacent terms the audience useslocation is providedseo-aeo-content-cluster,
seo-aeo-landing-page-writer, seo-aeo-blog-writer,
seo-aeo-meta-description-generatorUse when selecting target queries, understanding search intent, or turning a business goal into a prioritised content map.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/seo-aeo-keyword-research of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
SEO Aeo Keyword Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SEO Aeo Keyword Research this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| SEO DataforseoAgriciDaniel/codex-seo | 799 | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Competitor GapRyze-AI-Adgent/open-seo-mcp-skills | 4.7k | — | ~560 | Automated safety check: Pass | MIT | |
| Geo DifficultyOpenClaudia/openclaudia-skills | 713 | — | ~694 | Automated safety check: Pass | MIT | |
| Keyword ResearchRyze-AI-Adgent/open-seo-mcp-skills | 4.7k | — | ~581 | Automated safety check: Pass | MIT | |
| DataForSEO Live SEO DataAgriciDaniel/claude-seo | 19k | — | ~4.4k | Automated safety check: Pass | MIT |
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
Ryze-AI-Adgent/open-seo-mcp-skills
Find keywords a competitor ranks for that the user's site doesn't — the content gap, prioritized by volume and winnability.
OpenClaudia/openclaudia-skills
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
Ryze-AI-Adgent/open-seo-mcp-skills
Keyword research from a seed topic — ideas, real Google volume/CPC, intent, difficulty, clustered into a plan.
AgriciDaniel/claude-seo
Pulls live SERP results, keyword metrics, backlink profiles and AI visibility data through the DataForSEO MCP server, with a cost check before each call.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "analyze the SERP" or "SERP分析"; maps SERP features, layout, ranking factors, search intent, AI Overviews, and snippet opportunities for a query.
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Categories
Researches and prioritises keywords from the site context and live search intent, including problem queries, question queries, difficulty tiers, and a content map. SEO Aeo Keyword Research is an agent skill from sickn33/agentic-awesome-skills. Researches and prioritises keywords from the site context and live search intent, including problem queries, question queries, difficulty tiers, and a content map.
SEO Aeo Keyword Research fits situations like: tasks that involve Keyword research; tasks that involve AI search optimization.
Run `npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a claude-code`. Or copy the skill folder (skills/seo-aeo-keyword-research in sickn33/agentic-awesome-skills) into .claude/skills/seo-aeo-keyword-research in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a codex`. Or copy the skill folder (skills/seo-aeo-keyword-research in sickn33/agentic-awesome-skills) into .agents/skills/seo-aeo-keyword-research in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-keyword-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-aeo-keyword-research, .gemini/skills/seo-aeo-keyword-research, .github/skills/seo-aeo-keyword-research and .opencode/skills/seo-aeo-keyword-research in your project.
SKILL.md names no scripts, command-line tools or credentials: SEO Aeo Keyword Research is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
SEO Aeo Keyword Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with SEO Aeo Keyword Research: SEO Dataforseo (AgriciDaniel/codex-seo, 799 stars), Competitor Gap (Ryze-AI-Adgent/open-seo-mcp-skills, 4.7k stars), Geo Difficulty (OpenClaudia/openclaudia-skills, 713 stars) and Keyword Research (Ryze-AI-Adgent/open-seo-mcp-skills, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.