agentleFS
Sign inStart free
BWERepoBWERepo/ClaudeSkills/skills/BWE-SEO/SKILL.md

BWE-SEO

Skill0 starsChanged 21 days agoNo licenceView on GitHub

The SEO front door — the state-aware, environment-aware master controller of the BWE-SEO engine. Inspects the current website project's real SEO state (setup, business profile and open questions, audit, opportunities, roadmap, and every page's approval, build, SEO QA, staging deployment, staging review, the owner's staging approval, production deployment, post-publication check, Search Console, Google index monitoring (what Google has indexed, sitemap health, URLs needing attention) and 7/30/90-day monitoring status, plus site issues, with read-only live checks of production AND staging), shows a short status dashboard in plain language that always starts with the environment being evaluated (LOCAL / STAGING / PRODUCTION, production and staging domains, whether indexing actions are allowed) and recommends the ONE best next action and the specialized BWE-SEO skill that does it, then asks before proceeding. Never skips an approval gate, never recommends indexing for a staging URL; says "wait" when waiting is right. Recognizes projects with no SEO yet and offers setup. Use when the user says "SEO", "work on SEO", "what's next for SEO", "SEO status", "where are we with SEO", "run SEO", "SEO workflow", "what SEO should we do", or invokes /BWE-SEO, in any website project. "show details" / "full SEO status" gives the detailed view. "/BWE-SEO keyword <phrase>" analyzes one Google keyword from the site's own Search Console data (target page, indexing, impressions, clicks, CTR, average position, wrong-page and cannibalization checks, the next action) - it is not a Google search.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 3 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.

Check your setup, free