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

BWE-SEO-QA

Skill0 starsChanged 22 days agoNo licenceView on GitHub

SEO QA gate for a page in the current website project using the BWE-SEO engine — content checks (every claim verified, no fabricated proof, labeled demos, clear intent, no stuffing, no cannibalization), on-page checks (unique title/description, one H1, canonical, indexability, schema validity, internal links, CTA, images/alt) and technical checks (build, tests, SSR/200/404, mobile, accessibility, sitemap). Any blocking failure fails QA. `/BWE-SEO-QA <page> staging` is the STAGING REVIEW: page function, SEO, environment (hidden from search engines, no production contamination) and content checks on the staging URL with SEARCH ENGINE INDEXING ACTIONS DISABLED, visual checks listed for the owner, then it stops at the owner's staging approval. Use when the user says \"SEO QA\", \"check this page before publishing\", \"staging review\", \"review the page on staging\", or invokes /BWE-SEO-QA <page> [staging], in any website project.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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