Seog
TerminalSkills/skills
Run local SEO from your terminal via the SEOG MCP server — Google Business Profile management, map-pack rank tracking and geo-grid scans, review sync and replies published to Google, competitor…
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
$ npx skills add petera2c/simple-table --skill seo-project-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install petera2c/simple-table seo-project-setup --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/petera2c/simple-table.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/seo-project-setup .claude/skills/seo-project-setup && 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-project-setup" agent skill from https://github.com/petera2c/simple-table/tree/main/.agents/skills/seo-project-setup into .claude/skills/seo-project-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-project-setup", 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/petera2c/simple-table/tree/main/.agents/skills/seo-project-setupType 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 petera2c/simple-table --skill seo-project-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install petera2c/simple-table seo-project-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petera2c/simple-table.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/seo-project-setup .agents/skills/seo-project-setup && 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-project-setup" agent skill from https://github.com/petera2c/simple-table/tree/main/.agents/skills/seo-project-setup into .agents/skills/seo-project-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-project-setup", 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 petera2c/simple-table --skill seo-project-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install petera2c/simple-table seo-project-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petera2c/simple-table.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/seo-project-setup .cursor/skills/seo-project-setup && 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-project-setup" agent skill from https://github.com/petera2c/simple-table/tree/main/.agents/skills/seo-project-setup into .cursor/skills/seo-project-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-project-setup", 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/petera2c/simple-table.git --path .agents/skills/seo-project-setup--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 petera2c/simple-table --skill seo-project-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install petera2c/simple-table seo-project-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petera2c/simple-table.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/seo-project-setup .gemini/skills/seo-project-setup && 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-project-setup" agent skill from https://github.com/petera2c/simple-table/tree/main/.agents/skills/seo-project-setup into .gemini/skills/seo-project-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-project-setup", 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 petera2c/simple-table seo-project-setupInstalls 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 petera2c/simple-table --skill seo-project-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/petera2c/simple-table.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/seo-project-setup .github/skills/seo-project-setup && 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-project-setup" agent skill from https://github.com/petera2c/simple-table/tree/main/.agents/skills/seo-project-setup into .github/skills/seo-project-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-project-setup", 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 petera2c/simple-table --skill seo-project-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install petera2c/simple-table seo-project-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/petera2c/simple-table.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/seo-project-setup .opencode/skills/seo-project-setup && 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-project-setup" agent skill from https://github.com/petera2c/simple-table/tree/main/.agents/skills/seo-project-setup into .opencode/skills/seo-project-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-project-setup", 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-project-setupSet up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
SEO Project Setup is an agent skill from petera2c/simple-table. Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
Its SKILL.md is about 1.5k 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 Local SEO and Positioning and messaging. It works with Model Context Protocol and Google Search Console. The repository describes itself as: Lightweight data grid/table for fast, modern web apps. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit df2dda2. 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.
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 Project Setup loads about 1.5k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 827 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 petera2c/simple-table at commit df2dda2, republished under its MIT licence (© petera2c). 827 words, ~1,549 tokens.
.claude/skills/seo-project-setup/SKILL.md (or your agent's skills folder).Help the user set up a local SEO workspace for one website or SEO project. The folder is where the agent saves notes, goals, exports, briefs, reports, preferences, and project context over time. This is a workspace and context setup workflow, not a full audit.
Be friendly, practical, and structured. Ask questions in small batches. Explain why each item matters only when useful. Do not overwhelm a beginner with jargon.
Suggest that the user choose or create a local folder for SEO work, for example:
~/SEO/<company-or-site>/~/Documents/SEO/<company-or-site>/Explain that keeping notes, exports, briefs, scraped pages, reports, and preferences in one folder helps the agent build context over time. Future SEO workflows can use that folder rather than starting from a blank conversation.
Recommended starter structure:
seo-workspace/
README.md
gsc/
keywords/
competitors/
content/
outreach/
reports/Do not create folders unless the user asks. If file tools are available and the user asks, create a simple structure and a short README.md with the current goals, known sites, and user preferences for how the agent should approach SEO for this project.
Ask for:
Ask the user what they want from SEO:
Ask for success metrics and timeframe. If goals are vague, help turn them into measurable goals such as "increase non-branded organic signups" or "rank top 10 for 20 buying-intent terms."
Ask what research they have already done about the company, product, audience, and competitors. Request any notes, docs, customer interviews, positioning docs, pitch decks, landing pages, or strategy memos they can share.
Probe for:
If the user has not done this yet, offer to help research positioning using the company website, competitor pages, reviews, forums, and web search.
After the user has described the company, website, goals, and positioning, check that OpenSEO MCP is configured and mapped to the right project:
whoami if available.list_projects to confirm the user can access projects.Do not run research tools just to test connectivity; whoami and list_projects are enough.
GSC is the richest first-party signal: existing impressions, near-ranking terms, cannibalization, and pages that already have search demand.
Preferred (hosted): connect it natively. On the project's Integrations page, connect Google Search Console and pull live data with get_search_console_performance. Once connected, the agent reads it directly in keyword-research and keyword-clustering — no manual files to maintain.
Fallback (self-hosted, or if the user prefers files): ask the user to export CSVs from Search Console into the SEO working folder.
Recommended exports:
Ask them to drop files into gsc/ and use names like:
gsc/queries-last-3-months.csv
gsc/pages-last-3-months.csv
gsc/queries-last-16-months.csv
gsc/pages-last-16-months.csvAsk for or discover:
After intake, recommend one next OpenSEO workflow:
keyword-research: when the user needs ideas from seed topicskeyword-clustering: when they have keywords or GSC data to map to pagescompetitive-landscape: when the market is unclearcompetitor-analysis: when they know a competitor to studylink-prospecting: when they have a linkable asset or target pageUse a checklist with statuses:
| Step | Status | Notes | Next action |
|---|
Then summarize:
get_search_console_performance confirms it (it returns a "not connected" message otherwise).© petera2c, 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 .agents/skills/seo-project-setup of petera2c/simple-table.
Open the folder on GitHubat commit df2dda2
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in petera2c/simple-table, which our catalogue first saw on October 7, 2026.
SEO Project Setup 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 Project Setup this skillpetera2c/simple-table | 229 | 2 repos | ~1.5k | Automated safety check: Pass | MIT | |
| SeogTerminalSkills/skills | 163 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| SEO Project Setupevery-app/open-seo | 23k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Google Mapscablate/mcp-google-map | 468 | — | ~909 | Automated safety check: Pass | MIT | |
| Google Maps Local SEOcablate/mcp-google-map | 468 | — | ~633 | Automated safety check: Pass | MIT |
TerminalSkills/skills
Run local SEO from your terminal via the SEOG MCP server — Google Business Profile management, map-pack rank tracking and geo-grid scans, review sync and replies published to Google, competitor…
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.
every-app/open-seo
Populate a project's shared OpenSEO context — site scope, goals, positioning, competitors, key pages, and preferences — plus MCP checks and Search Console intake.
cablate/mcp-google-map
Search places, resolve addresses, compare routes, inspect neighborhoods, and retrieve geographic or environmental facts through the standalone @cablate/mcp-google-map CLI.
cablate/mcp-google-map
Analyze Google Business Profile visibility, geographic grid rankings, local search keywords, and nearby competitors through the standalone Google Maps CLI.
cablate/mcp-google-map
Build evidence-backed day trips, multi-day itineraries, and efficient stop sequences with Google Maps data through the standalone CLI.
petera2c/simple-table
Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.
petera2c/simple-table
Write Simple Table changelog entries and bump package versions.
petera2c/simple-table
Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.
petera2c/simple-table
Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps.
petera2c/simple-table
Cluster keywords by intent and map them to existing or proposed pages.
petera2c/simple-table
Discover keyword opportunities, evaluate metrics and SERPs, and save/tag promising terms.
Categories
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake. SEO Project Setup is an agent skill from petera2c/simple-table. Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
SEO Project Setup fits situations like: tasks that involve Local SEO; tasks that involve Positioning and messaging.
Run `npx skills add petera2c/simple-table --skill seo-project-setup -a claude-code`. Or copy the skill folder (.agents/skills/seo-project-setup in petera2c/simple-table) into .claude/skills/seo-project-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add petera2c/simple-table --skill seo-project-setup -a codex`. Or copy the skill folder (.agents/skills/seo-project-setup in petera2c/simple-table) into .agents/skills/seo-project-setup 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 petera2c/simple-table --skill seo-project-setup -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-project-setup, .gemini/skills/seo-project-setup, .github/skills/seo-project-setup and .opencode/skills/seo-project-setup in your project.
SKILL.md names no scripts, command-line tools or credentials: SEO Project Setup 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 Project Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Project Setup: Seog (TerminalSkills/skills, 163 stars), SEO (Nexus-JPF/note-companion, 870 stars), SEO Project Setup (every-app/open-seo, 23k stars) and Google Maps (cablate/mcp-google-map, 468 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
petera2c (a GitHub user) maintains it in petera2c/simple-table, which has 229 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 4, 2026.
Source: petera2c/simple-table on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.