Global SEO Growth
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
Install SEO
$ npx skills add Nexus-JPF/note-companion --skill seo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Nexus-JPF/note-companion seo --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/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/seo .claude/skills/seo && 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" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/seo into .claude/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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/Nexus-JPF/note-companion/tree/master/.agents/skills/seoType 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 Nexus-JPF/note-companion --skill seo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Nexus-JPF/note-companion seo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/seo .agents/skills/seo && 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" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/seo into .agents/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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 Nexus-JPF/note-companion --skill seo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Nexus-JPF/note-companion seo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/seo .cursor/skills/seo && 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" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/seo into .cursor/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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/Nexus-JPF/note-companion.git --path .agents/skills/seo--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 Nexus-JPF/note-companion --skill seo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Nexus-JPF/note-companion seo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/seo .gemini/skills/seo && 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" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/seo into .gemini/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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 Nexus-JPF/note-companion seoInstalls 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 Nexus-JPF/note-companion --skill seo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/seo .github/skills/seo && 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" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/seo into .github/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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 Nexus-JPF/note-companion --skill seo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Nexus-JPF/note-companion seo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/seo .opencode/skills/seo && 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" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/seo into .opencode/skills/seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo", 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.
Facts
- Skill name
seo- GitHub stars
- 870
- Token cost
- ~2.2k tokens
- SKILL.md length
- 972 words
- Files
- 2
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
- Works in 3 steps: seo_list_reports returns report ids and… → seo_describe_report returns one report's… → seo_run_report runs bounded params. Read…
- Tasks that involve AI search optimization
- SKILL.md covers Discover, describe, run, Setup and selection, Common jobs and Create a client HTML report, plus 2 more sections
- Reaches seoskill.dev
What it does
SEO is an agent skill from Nexus-JPF/note-companion. Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, keyword research, competitors, backlinks, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data, Core Web Vitals, internal links, content opportunities, programmatic SEO, local search, Search Console or Google Analytics questions, Google update impact, llms.txt, AI search visibility in ChatGPT…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Marketing & SEO, covering AI search optimization, Technical SEO and Web performance. It works with Model Context Protocol, Google Analytics, Google Search Console and OpenAI. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.
When your agent uses it
- Tasks that involve AI search optimization
- Tasks that involve Technical SEO
- Tasks that involve Web performance
Example prompts
- “/seo”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- seo_list_reports returns report ids and purposes, optionally by category.
- seo_describe_report returns one report's usage, schema, reading order,
- seo_run_report runs bounded params. Read structuredContent, not display
What it can do on your machine
Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
seoskill.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
SEO loads about 2.2k tokens when it runs. Until then it costs about 166 tokens; SKILL.md has 972 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 972 words, ~2,180 tokens.
Download SKILL.mdSave it as
.claude/skills/seo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- seo
- description
- Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, keyword research, competitors, backlinks, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data, Core Web Vitals, internal links, content opportunities, programmatic SEO, local search, Search Console or Google Analytics questions, Google update impact, llms.txt, AI search visibility in ChatGPT, Claude, Perplexity, or Google AI Overviews, and client SEO reporting. Routes to evidence-backed local reports through the SEO CLI and MCP server.
seo
seo is a local CLI, MCP server, and report engine using crawl, Search Console,
Google Analytics, optional Bing evidence, and optional research providers.
Reports keep observations, estimates, findings, caveats, costs, and provenance
separate. Storage stays local; requested crawls and provider operations still
make direct network requests. Discover reports at runtime instead of
memorising them.
Discover, describe, run
With the MCP server (preferred):
seo_list_reportsreturns report ids and purposes, optionally by category.seo_describe_reportreturns one report's usage, schema, reading order, limits, verification, and related ids.seo_run_reportruns boundedparams. ReadstructuredContent, not display text.
The same catalog exists without MCP:
seo reports list --json
seo reports describe <report-id> --json
seo reports run <report-id> --params '<json>' --jsonDescribe a report before its first run. Follow readOrder, doNotClaim, and
related; reuse its schema and do not guess parameters. When fixableChecks
exists, fetch guidance only for failed or warning ids in topActions with
seo_describe_report using id and check (CLI:
seo reports describe <report-id> --check <check-id>).
Setup and selection
Use setup-check or seo doctor when auth is unknown. Select profiles with
--project <id> and list them with seo projects list --json. Without one,
pass --site sc-domain:example.com or --url https://example.com. Crawl audits
need no Google connection. Agent commands use --json, which never prompts.
Common jobs
Run the first report, read it, then decide. Do not run a whole chain blindly.
| Job | Reports |
|---|---|
| Page not indexed or missing from Google | index-coverage, index-monitor (URL Inspection), audit-page, redirect-trace |
| Traffic or clicks dropped | search-performance-overview, traffic-anomaly, update-correlation, segment-impact, decaying-pages, link-recovery |
| Audit a whole site | site-crawl with health: true, report command (main report), full site-crawl only if needed, top-fixes, ai-search-scorecard |
| More clicks from existing pages | quick-wins, ctr-underperformers, striking-distance, second-page, internal-links |
| AI agent readiness for a content site | agent-readiness, ai-readiness, entity-readiness, llms-txt-audit |
| AI search visibility and eligibility | ai-readiness, geo-gaps, ai-mention-research, ai-prompt-observations, ai-referrals, seo-to-ai-query |
| Plan content from real demand | query-clusters, page-opportunities, content-optimization, cannibalisation |
| Research keywords and current results | keyword-research, keyword-metrics, saved-keywords, serp-results |
| Turn a topic into a keyword and competitor shortlist | competitive-opportunities, then inspect the decision-critical pages or links |
| Research local demand and page patterns | local-search-demand, then serp-results or rank-tracking for a fixed market when needed |
| Find search competitors and plausible gaps | serp-competitors, domain-overview, ranking-pages, ranked-keywords, competitor-keyword-gap |
| Research programmatic SEO patterns | pseo-patterns for observed queries and declared term, pair, or matrix sets; pseo-opportunities, ranking-pages, or competitor-keyword-gap for deeper research; then pseo-audit for existing templates |
| Catch regressions over time | technical-watch, crawl-diff, index-watch, measure-change after a fix ships |
| Track exact keyword positions | rank-tracking for a saved set and fixed market/device; serp-results for one current query |
| Review Bing traffic, crawl, query, and page insights | bing-webmaster-overview, then site-crawl when live page evidence is needed |
| Review backlink context and linked targets | domain-rating, link-evidence, then verify selected results, referring URLs, and flagged targets directly |
| Review real crawler requests in a server log | server-log-analysis, then verify important errors against the original log and server configuration |
| Client-ready reporting | monthly-report, narrative-report, monthly-action-plan |
| Turn crawl findings into tickets | top-fixes, affected-urls, explain-crawl-issue |
Without provider API access, describe ranked-keywords, ranking-pages,
serp-competitors, or competitor-keyword-gap and pass one to four local
ranked-keyword exports through researchFiles. Read evidence.imports before
using the rows. If headings are unfamiliar, use the report schema's explicit
columns map rather than guessing. File dates, hashes, included fields, column
mappings, filtered historical rows, rejected rows, and caps define the evidence
boundary.
Use seo report first for a broad performance question with a known project.
For a large or unfamiliar URL, run sitemap health before a full crawl.
Show full SKILL.md (413 more words)Show less
Create a client HTML report
For a polished or branded report, create one standalone HTML file from
structured data. Built-in --format html is a predictable fallback. Start with
compact JSON and request --full only when deeper evidence is needed. Follow
supplied brand direction and design for the findings. Use responsive,
accessible, print-friendly HTML, embedded CSS, noindex,nofollow, and no remote
scripts or assets.
Show site, period, generated date, provider labels, data status, priorities, limitations, and verification. Preserve partial, capped, sampled, missing, and skipped states. Keep observations separate from interpretation and providers separate from each other. Never invent scores, forecasts, causes, or missing values. Omit secrets and unnecessary raw rows. Save locally and report the path.
For a large site, run site-crawl with health: true and an explicit
sitemapUrl when known. Read config.strategy, access, failures, limits, and
sitemap completeness. Full crawl second only for page content, metadata,
canonicals, links, structured data, or rendered HTML.
Requests use SEO-Skill/<version> (+https://seoskill.dev). For
access.blockedRequests, show provider evidence and the identity. Ask for a
temporary exception scoped by audit IP, host or paths, and blocking rule. Never
recommend a User-Agent-only bypass.
Evidence rules
- Check
dataStatus, selection counts,caveats, andwarningsbefore summarising any report. Name skipped or incomplete evidence first. - Partial, capped, filtered, or sampled sources never support a zero or an all-clear. Grouped Search Console totals undercount because anonymised query rows are withheld.
- Values marked heuristic are prioritisation aids, not forecasts. Never promise clicks, rankings, indexing, or AI citations from any report.
- Quote
principleandevidenceRefwhen explaining a recommendation, and give the user the report's verification step alongside any suggested change. - If a report returns no rows, say so plainly.
- Intentional controls such as
noindex, canonicals, and robots rules are observations until the user confirms they are unintended. - Provider traffic, volume, difficulty, visibility, intent, authority, and ranking history are estimates. Keep them separate from Search Console, Google Analytics, crawl, and live result evidence.
Beyond the report catalog
Use seo help all for direct provider and administration commands. Bing setup
uses seo providers bing; link evidence uses seo links --project <id> --json,
seo links --provider ahrefs --target <domain> --json,
seo links --provider dataforseo --target <domain> --json, or a local file.
IndexNow writes externally: validate with
seo indexnow submit --dry-run --json and remove dry run only when authorised.
Receipt does not prove crawling or indexing. Prefer registered reports.
Use refresh: true or --refresh only when fresh data is requested. Sitemap
health always bypasses page-body cache and never writes page responses.
© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/seo of Nexus-JPF/note-companion.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 9cad635
Compare with similar skills
SEO 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 this skillNexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Global SEO Growthminhnv0807/ai-business-skills | 610 | — | ~5k | Automated safety check: Pass | MIT | |
| 32 SEO Growthminhnv0807/ai-business-skills | 610 | — | ~5k | Automated safety check: Pass | MIT | |
| SEOAgriciDaniel/seo-os | 135 | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| SEOAgriciDaniel/codex-seo | 797 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Money SEOiamzifei/show-me-the-money | 1k | — | ~4.4k | Automated safety check: Pass | Custom licence |
Similar skills
32 SEO Growth
minhnv0807/ai-business-skills
Khi nguoi dung muon tang traffic tu SEO, AI SEO, GEO/AEO, Google, ChatGPT, Perplexity, schema, structured data, llms.txt, programmatic SEO, local SEO, directory submissions, Product Hunt…
SEO
AgriciDaniel/seo-os
Comprehensive SEO analysis for any website or business type.
SEO
AgriciDaniel/codex-seo
Comprehensive SEO analysis for any website, page, business, or topic.
Money SEO
iamzifei/show-me-the-money
SEO and GEO (Generative Engine Optimization) for organic traffic and AI search visibility.
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
More from Nexus-JPF/note-companion
All 18 skills in this repoAnalytics
Nexus-JPF/note-companion
When the user wants to set up, improve, or audit analytics tracking and measurement.
Customer Research
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
Marketing Plan
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
Competitor Profiling
Nexus-JPF/note-companion
When the user wants to research, profile, or analyze competitors from their URLs.
Onboarding
Nexus-JPF/note-companion
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
Image
Nexus-JPF/note-companion
When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.
Related
Categories
Questions about SEO
What does SEO do?
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. SEO is an agent skill from Nexus-JPF/note-companion. Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
When should I use SEO?
SEO fits situations like: tasks that involve AI search optimization; tasks that involve Technical SEO; tasks that involve Web performance.
How do I install SEO in Claude Code?
Run `npx skills add Nexus-JPF/note-companion --skill seo -a claude-code`. Or copy the skill folder (.agents/skills/seo in Nexus-JPF/note-companion) into .claude/skills/seo in your project. Claude Code loads it when a task matches its description.
How do I install SEO in Codex?
Run `npx skills add Nexus-JPF/note-companion --skill seo -a codex`. Or copy the skill folder (.agents/skills/seo in Nexus-JPF/note-companion) into .agents/skills/seo in your project. Codex loads it when a task matches its description.
Can I use SEO in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill seo -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, .gemini/skills/seo, .github/skills/seo and .opencode/skills/seo in your project.
What does SEO need to run?
SKILL.md names no scripts, command-line tools or credentials: SEO is instructions for the agent only.
Does SEO access the network?
SKILL.md names 1 domain. In commands or code: seoskill.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is SEO safe to install?
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.
What licence does SEO use?
SEO is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does SEO use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to SEO?
Skills that share tags, products or a category with SEO: Global SEO Growth (minhnv0807/ai-business-skills, 610 stars), 32 SEO Growth (minhnv0807/ai-business-skills, 610 stars), SEO (AgriciDaniel/seo-os, 135 stars) and SEO (AgriciDaniel/codex-seo, 797 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains SEO?
Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 870 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.
Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.