agentleFS
BWERepoBWERepo/ClaudeSkills/skills/BWE-SEO-SETUP/SKILL.md

BWE-SEO-SETUP

Skill0 starsChanged 22 days agoNo licenceView on GitHub

Configures BWE-SEO for the current customer's website project AFTER the engine is installed (/BWE-SEO-ENGINE install) — creates the customer-specific seo/seo-config.json, business profile and content inventory (and docs/seo/), picks the stack adapter, and builds a verified business profile from the customer questionnaire, the live site and the owner's answers, flagging missing facts instead of inventing them. Determines the project's environments (verified production URL, staging URL or STAGING ENVIRONMENT - NOT CONFIGURED, preview, deployment architecture, how staging is kept out of search results), the sitemap URL, the Search Console property and who owns it, whether the optional Search Console API integration will be used and where its credential lives (a NAME, never the credential), and the analytics status. Use when the user says "set up SEO", "configure SEO for this client", "SEO onboarding", or invokes /BWE-SEO-SETUP, in any website project.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    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.