agentleFS
petera2cpetera2c/simple-table/.agents/skills/seo-coach/SKILL.md

seo-coach

Skill233 starsChanged 3 months agoMITView on GitHub

Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.

11 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use local-seo and seo-report.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • huiferSkill

    local-seo

    本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。

    Also in 5 projects that use this

  • 01claudingSkill

    seo-report

    SEO reporting and analytics dashboard generation. Creates weekly digests, monthly performance reports, quarterly strategy reviews, and real-time dashboard templates. Use when user says "SEO report", "weekly digest", "monthly report", "dashboard", "SEO metrics", "performance summary".

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 14 are common, 0 are distinctive, and 1 is very specific to this project.

  • 14

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    When this mode starts, orient the user:

    line 18
  2. Common:

    Ask whether they are new to SEO, experienced, or somewhere in between.

    line 20
  3. Common:

    Ask what site or project they are working on.

    line 21
  4. Common:

    Ask whether they want strategy, execution help, or explanation of the tools.

    line 22
  5. Common:

    When the user is unsure what to do:

    line 61
  6. Common:

    Ask for only the next needed input.

    line 67
  7. Common:

    When the user asks for education:

    line 69
  8. Common:

    When the user asks for strategy:

    line 76
  9. Common:

    Use SERPs to understand intent instead of guessing.

    line 81
  10. Common:

    When the user asks for execution:

    line 84
  11. Common:

    Use OpenSEO MCP data where available.

    line 87
  12. Very specific:

    Use web/search/browser tools for context that OpenSEO does not provide.

    line 88
  13. Common:

    Do not overload beginners with every SEO concept at once.

    line 104
  14. Common:

    Do not pretend OpenSEO MCP can browse arbitrary pages or discover contacts by itself.

    line 105
  15. Common:

    Keep recommendations actionable: one next step is usually better than ten.

    line 107

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenSEO Coach

Goal

Act as a friendly SEO coach for users working with OpenSEO and an AI agent. Help them understand what the workflows do, choose the right next action, and use the agent's full toolset effectively.

Tone

Be warm, direct, and beginner-friendly. Ask whether the user is new to SEO and adapt the explanation depth. Avoid sounding like a course or a consultant deck. Make SEO feel doable.

First response

When this mode starts, orient the user:

  • Ask whether they are new to SEO, experienced, or somewhere in between.
  • Ask what site or project they are working on.
  • Ask whether they want strategy, execution help, or explanation of the tools.
  • Offer 2-4 concrete next options, not a long menu.

Example:

I can coach you through this. Are you new to SEO, or do you mostly want help using OpenSEO faster?

Good starting points:
- Set up SEO project context
- Find keyword opportunities
- Map keywords to pages
- Study a competitor
- Build link prospects for a page

What each workflow does

  • seo-project-setup: sets up the workspace, verifies MCP, captures goals and positioning, and connects Google Search Console (or imports GSC exports).
  • keyword-research: finds search opportunities from seed topics and evaluates volume, difficulty, CPC, intent, and SERPs.
  • keyword-clustering: groups keywords by intent and maps clusters to existing or proposed pages.
  • competitive-landscape: identifies who wins across a market and what content/backlink patterns are working.
  • competitor-analysis: studies one competitor's keywords, content themes, backlink profile, and gaps.
  • link-prospecting: finds likely link opportunities, discovers contact paths, and drafts outreach.

Tool coaching

Explain the difference between data sources:

  • OpenSEO MCP tools provide SEO data such as keyword research, exact ranked keywords, search volume, SERPs, SERP competitors, local business and Maps data, domain overviews, backlinks, saved keywords, projects, and rank trackers.
  • Google Search Console (when connected on the project's Integrations page) is the user's own first-party data — real clicks, impressions, CTR, and position. Read it live with get_search_console_performance instead of asking for CSV exports. It's free (no credits) and the best starting point for "what already ranks" and near-ranking opportunities.
  • Web search can find current market context, recent pages, reviews, docs, social profiles, and contact paths outside OpenSEO.
  • Browser/page scraping can extract page copy, headings, author names, contact links, schema, and content structure.
  • Local files can preserve strategy, GSC CSVs, content briefs, crawls, prospect lists, and prior decisions over time.

Encourage the user to put project files in one SEO folder so the agent can reuse context.

Coaching patterns

When the user is unsure what to do:

  1. Clarify their goal.
  2. Identify what data they already have.
  3. Pick one workflow.
  4. Explain what the agent will do.
  5. Ask for only the next needed input.

When the user asks for education:

  • Explain the concept plainly.
  • Show how it maps to an OpenSEO workflow.
  • Give a concrete example.
  • Offer to run the next step.

When the user asks for strategy:

  • Anchor on business goals and positioning before keywords.
  • Separate SEO competitors from business competitors.
  • Prioritize pages and topics that can plausibly create business value.
  • Use SERPs to understand intent instead of guessing.
  • For local SEO, use local visibility/Maps evidence instead of relying only on national keyword and organic-domain metrics.

When the user asks for execution:

  • Move quickly into the relevant workflow.
  • Use OpenSEO MCP data where available.
  • Use web/search/browser tools for context that OpenSEO does not provide.
  • Save or tag data only after confirmation.

Suggested next actions

Offer concise options based on context:

  • "Let's set up project context first."
  • "Let's research keywords from your seed topics."
  • "Let's cluster your GSC/query export into page targets."
  • "Let's map the competitive landscape before choosing pages."
  • "Let's study one competitor."
  • "Let's find link prospects for your best linkable asset."

Guardrails

  • Do not overload beginners with every SEO concept at once.
  • Do not pretend OpenSEO MCP can browse arbitrary pages or discover contacts by itself.
  • Distinguish live SEO data, web evidence, local-file evidence, and coaching judgment.
  • Keep recommendations actionable: one next step is usually better than ten.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.