SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
Complete SEO content creation system for AI agents. An agent skill from LeoYeAI/openclaw-master-skills.
$ npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-seo-content-engine --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/afrexai-seo-content-engine .claude/skills/afrexai-seo-content-engine && 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 "afrexai-seo-content-engine" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engine into .claude/skills/afrexai-seo-content-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-seo-content-engine", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engineType 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 LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-seo-content-engine --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/afrexai-seo-content-engine .agents/skills/afrexai-seo-content-engine && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "afrexai-seo-content-engine" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engine into .agents/skills/afrexai-seo-content-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-seo-content-engine", 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 LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-seo-content-engine --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/afrexai-seo-content-engine .cursor/skills/afrexai-seo-content-engine && 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 "afrexai-seo-content-engine" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engine into .cursor/skills/afrexai-seo-content-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-seo-content-engine", 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/LeoYeAI/openclaw-master-skills.git --path skills/afrexai-seo-content-engine--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 LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-seo-content-engine --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/afrexai-seo-content-engine .gemini/skills/afrexai-seo-content-engine && 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 "afrexai-seo-content-engine" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engine into .gemini/skills/afrexai-seo-content-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-seo-content-engine", 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 LeoYeAI/openclaw-master-skills afrexai-seo-content-engineInstalls 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 LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/afrexai-seo-content-engine .github/skills/afrexai-seo-content-engine && 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 "afrexai-seo-content-engine" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engine into .github/skills/afrexai-seo-content-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-seo-content-engine", 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 LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-seo-content-engine --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/afrexai-seo-content-engine .opencode/skills/afrexai-seo-content-engine && 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 "afrexai-seo-content-engine" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-seo-content-engine into .opencode/skills/afrexai-seo-content-engine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-seo-content-engine", 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.
afrexai-seo-content-engineComplete SEO content creation system for AI agents. An agent skill from LeoYeAI/openclaw-master-skills.
Afrexai SEO Content Engine is an agent skill from LeoYeAI/openclaw-master-skills. Complete SEO content creation system for AI agents. Research keywords, analyze competitors, write optimized articles, and track rankings — all through natural conversation. No APIs required.
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `_meta.json`).
It sits in Marketing & SEO, covering On-page SEO. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. 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 markdown and json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
schema.orgAlso links to:
afrexai-cto.github.ioFrom 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.
Afrexai SEO Content Engine loads about 4.3k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 1,292 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 LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,292 words, ~4,333 tokens.
.claude/skills/afrexai-seo-content-engine/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Turn your AI agent into a full SEO content team. Research → Plan → Write → Optimize → Publish — all in natural language.
No APIs. No subscriptions. Just smart agent workflows using web search and structured frameworks.
When given a topic, expand it systematically:
For each keyword, classify intent:
| Intent | Signal Words | Content Type |
|---|---|---|
| Informational | how to, what is, guide, tutorial, why | How-to guide, explainer, tutorial |
| Commercial | best, top, review, comparison, vs | Listicle, comparison, review |
| Transactional | buy, pricing, discount, free trial, download | Product page, landing page |
| Navigational | [brand name], login, support, docs | Brand page (skip — low value) |
For each target keyword:
Step 1: Search the exact keyword
Step 2: Analyze top 5 results:
- What type of content ranks? (listicle, guide, review)
- What's the average word count? (check article length)
- What subtopics do ALL top results cover? (table stakes)
- What subtopics do NONE cover? (your opportunity)
- Who wrote them? (big brand = harder, niche blog = beatable)
Step 3: Score opportunity:
- Mostly forums/Reddit in top 5 = HIGH opportunity (no dedicated content)
- All big brands (Forbes, HubSpot) = LOW opportunity (hard to outrank)
- Mix of niche sites = MEDIUM opportunity (winnable with better content)Score each keyword (1-5 per dimension):
| Dimension | 1 (Low) | 5 (High) |
|---|---|---|
| Relevance | Tangentially related | Core topic |
| Intent match | Informational only | Commercial/transactional |
| Competition gap | All big brands | Forums, thin content |
| Business value | No conversion path | Direct product tie-in |
| Content feasibility | Need proprietary data | Can write from expertise |
Priority: Score ≥ 18 = write immediately. 13-17 = queue. < 13 = skip.
Before writing ANY article, create this brief:
# Content Brief: [Title]
**Target keyword**: [primary keyword]
**Secondary keywords**: [3-5 related terms to weave in naturally]
**Search intent**: [informational/commercial/transactional]
**Target word count**: [based on competitor analysis]
**Content type**: [guide/listicle/comparison/review/case study]
## Audience
- Who is searching this? [persona]
- What do they already know? [beginner/intermediate/advanced]
- What do they want to DO after reading? [action]
## Must-Cover Subtopics (from competitor analysis)
1. [Topic all competitors cover — table stakes]
2. [Topic all competitors cover — table stakes]
3. ...
## Differentiation Angles (our edge)
1. [Topic NO competitor covers — our advantage]
2. [Fresh data/perspective they're missing]
3. [Practical template/tool they don't provide]
## Internal Links
- Link TO: [existing content on your site]
- Link FROM: [update these older articles to link to this one]
## CTA
- Primary: [what should the reader do?]
- Secondary: [email signup, related article, tool]Organize articles into clusters:
PILLAR PAGE: "Complete Guide to [Topic]" (3,000-5,000 words)
├── CLUSTER: "How to [Subtopic A]" (1,500-2,500 words)
├── CLUSTER: "Best [Subtopic B] for [Audience]" (2,000-3,000 words)
├── CLUSTER: "[Subtopic C] vs [Subtopic D]" (1,500-2,000 words)
├── CLUSTER: "[Subtopic E] Template + Examples" (1,000-1,500 words)
└── CLUSTER: "Common [Topic] Mistakes" (1,500-2,000 words)Each cluster article links back to the pillar. The pillar links to all clusters. This builds topical authority.
Every article follows this skeleton:
✅ DO:
- Primary keyword in title (H1)
- Primary keyword in first 100 words
- Primary keyword in 1-2 H2 headings
- Primary keyword in conclusion
- Secondary keywords scattered in body (1-2 each)
- Semantic variants throughout (synonyms, related phrases)
❌ DON'T:
- Use exact keyword more than 1x per 200 words
- Force keywords into headings where they sound unnatural
- Use the same keyword phrase 3x in one paragraph
- Stuff keywords in image alt text unnaturallyRun this checklist on every article before publishing:
/best-project-management-tools{
"@context": "https://schema.org",
"@type": "Article",
"headline": "[Title]",
"description": "[Meta description]",
"author": {
"@type": "Person",
"name": "[Author]"
},
"datePublished": "[YYYY-MM-DD]",
"dateModified": "[YYYY-MM-DD]",
"publisher": {
"@type": "Organization",
"name": "[Site Name]"
}
}{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "[Question 1]",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Answer 1]"
}
}
]
}# Best [X] for [Y] in [Year]
[Hook: Stat about the problem or market size]
[Bridge: Why choosing the right X matters for Y]
## Quick Comparison Table
| Product | Best For | Price | Rating |
|---------|----------|-------|--------|
## 1. [Product Name] — Best Overall
### Why It Stands Out
### Key Features
### Pricing
### Who It's For
### Downsides
[Repeat for 7-10 products]
## How We Evaluated
[Methodology — builds trust]
## FAQ
## Final Verdict# How to [X]: Step-by-Step Guide ([Year])
[Hook: What you'll achieve by the end]
[Bridge: Common mistakes people make with X]
## What You'll Need
[Prerequisites, tools, time estimate]
## Step 1: [Action Verb + Outcome]
[Detailed instructions]
[Screenshot or example]
[Pro tip callout]
[Repeat for each step]
## Common Mistakes to Avoid
## Advanced Tips
## FAQ
## Next Steps# [X] vs [Y]: Which Is Better in [Year]?
[Hook: The core difference in one sentence]
[Bridge: When to choose X vs Y]
## Quick Verdict
[TL;DR comparison — who should choose what]
## Overview Comparison
| Feature | X | Y |
|---------|---|---|
## [Feature Category 1]: [X] vs [Y]
### How [X] Handles It
### How [Y] Handles It
### Winner: [X/Y] because [reason]
[Repeat for 5-7 feature categories]
## Pricing Breakdown
## Who Should Choose [X]
## Who Should Choose [Y]
## FAQ
## Our Recommendation# The Ultimate Guide to [Topic] ([Year])
[Hook: Why this topic matters now]
[Bridge: What this guide covers that others don't]
## Table of Contents
## Chapter 1: [Foundational Concept]
[Explain the basics — link to cluster article for deep dive]
## Chapter 2: [Core Strategy]
[Main approach — link to how-to cluster]
## Chapter 3: [Tools & Resources]
[Curated list — link to comparison cluster]
## Chapter 4: [Advanced Techniques]
[Expert-level tactics]
## Chapter 5: [Common Mistakes]
[What to avoid — link to mistakes cluster]
## Chapter 6: [Case Studies / Examples]
[Real-world applications]
## FAQ (10-15 questions for this one)
## Conclusion + What to Do Next1. READABILITY CHECK
- Flesch Reading Ease: aim for 60-70 (8th-9th grade level)
- No paragraphs over 4 sentences
- No sentences over 25 words without a break
- Subheading every 250-300 words
2. KEYWORD DENSITY CHECK
- Primary keyword: 0.5-1.5% density (not higher)
- If over 1.5%: replace some instances with synonyms
- If under 0.5%: add naturally in body paragraphs
3. LINK AUDIT
- Internal links: 3-5 per 1,500 words minimum
- External links: 2-3 to authoritative sources (.gov, .edu, industry leaders)
- No orphan pages (every article linked from at least one other)
4. MEDIA CHECK
- Featured image with alt text
- In-content images/diagrams every 300-500 words
- Tables where data comparison exists
- Callout boxes for key takeaways
5. CTA CHECK
- One primary CTA (not competing CTAs)
- CTA appears at end and optionally mid-article
- CTA is specific ("Download the template" not "Learn more")1. INDEX REQUEST
- Submit URL to Google Search Console
- Share on social media (generates initial signals)
2. INTERNAL LINKING UPDATE
- Find 3-5 existing articles related to this topic
- Add contextual links from those articles to this new one
- This distributes link equity and helps discovery
3. MONITOR (Week 1-4)
- Track ranking position for target keyword
- Monitor organic impressions in Search Console
- Check bounce rate and time on page
4. UPDATE CYCLE
- Refresh content every 6-12 months
- Update stats, add new sections, improve based on search performance
- Articles that rank page 2 (positions 11-20) = highest ROI to updateScore every article before publishing (aim for 85+):
| Criteria | Points | How to Score |
|---|---|---|
| Keyword optimization | /15 | Title + H2s + natural body placement |
| Content depth | /20 | Covers all subtopics competitors cover + unique angles |
| Readability | /15 | Short paragraphs, varied sentences, scannable |
| Practical value | /15 | Templates, examples, actionable steps (not just theory) |
| Structure | /10 | Clear H2/H3 hierarchy, logical flow, TOC for long articles |
| Internal links | /5 | 3+ contextual internal links |
| External links | /5 | 2+ authoritative external references |
| Media | /5 | Images, tables, or diagrams present |
| Meta tags | /5 | Title < 60 chars, description 150-160 chars, both include keyword |
| CTA clarity | /5 | Single clear CTA with specific action |
| TOTAL | /100 |
Score guide:
Use natural language to trigger these workflows:
| Command | What It Does |
|---|---|
| "Research keywords for [topic]" | Full keyword expansion + prioritization matrix |
| "Analyze competitors for [keyword]" | Top 5 SERP analysis with content gaps |
| "Create a content brief for [keyword]" | Full brief using the template above |
| "Write an article about [topic]" | Full article using HBCFC framework + on-page checklist |
| "Optimize this article for [keyword]" | Run the optimization workflow on existing content |
| "Score this article" | Apply the 100-point scoring rubric |
| "Plan a content cluster for [topic]" | Pillar + 5-6 cluster articles with internal linking map |
| "Generate schema for this article" | Article + FAQ JSON-LD markup |
| "Create a [listicle/guide/comparison]" | Use the specific template for that content type |
| "Audit my SEO" | Full on-page checklist against provided content |
Don't just target one keyword — own the entire topic:
To win featured snippets (position 0):
Google favors fresh content for time-sensitive queries:
Built by AfrexAI — AI agent infrastructure for businesses that ship.
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in skills/afrexai-seo-content-engine of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Afrexai SEO Content Engine 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 |
|---|---|---|---|---|---|---|
| Afrexai SEO Content Engine this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 19k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw | 23k | — | ~693 | Automated safety check: Pass | Apache-2.0 | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 455 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| AI Citability Scorerzubair-trabzada/geo-seo-claude | 11k | 2 repos | ~3.7k | Automated safety check: Notes | MIT |
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
NVIDIA/NemoClaw
Remove bracketed NemoClaw tags from GitHub issue and PR titles.
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
zubair-trabzada/geo-seo-claude
Scores how likely AI assistants are to quote passages from a web page and suggests rewrites that make those passages easier to extract.
AgriciDaniel/claude-seo
Captures baselines of a page's SEO-critical elements, compares later snapshots against them and flags regressions by severity, like version control for on-page SEO.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Complete SEO content creation system for AI agents. An agent skill from LeoYeAI/openclaw-master-skills. Afrexai SEO Content Engine is an agent skill from LeoYeAI/openclaw-master-skills. Complete SEO content creation system for AI agents.
Afrexai SEO Content Engine fits situations like: tasks that involve On-page SEO.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a claude-code`. Or copy the skill folder (skills/afrexai-seo-content-engine in LeoYeAI/openclaw-master-skills) into .claude/skills/afrexai-seo-content-engine in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a codex`. Or copy the skill folder (skills/afrexai-seo-content-engine in LeoYeAI/openclaw-master-skills) into .agents/skills/afrexai-seo-content-engine 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 LeoYeAI/openclaw-master-skills --skill afrexai-seo-content-engine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/afrexai-seo-content-engine, .gemini/skills/afrexai-seo-content-engine, .github/skills/afrexai-seo-content-engine and .opencode/skills/afrexai-seo-content-engine in your project.
SKILL.md names no scripts, command-line tools or credentials: Afrexai SEO Content Engine is instructions for the agent only.
SKILL.md names 2 domains. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. As links in the text: afrexai-cto.github.io. 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.
Afrexai SEO Content Engine is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k 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 Afrexai SEO Content Engine: SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 19k stars), Nemoclaw Maintainer Normalize Title Tags (NVIDIA/NemoClaw, 23k stars) and SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.