agentleFS
getvibekitsgetvibekits/vibe-coding-rules/skills/seo-check/SKILL.md

seo-check

Skill0 starsChanged 22 days agoMITView on GitHub

Check every public page's title, description and headings before publishing.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check there's exactly one h1 and it says what the page is about.

    line 11
  2. Distinctive:

    Check every image has alt text.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 5 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

For every public page:

  1. List the title tag and its length. Flag any over 60 characters or duplicated.
  2. List the meta description and its length. Flag any missing or over 155 characters.
  3. Check there's exactly one h1 and it says what the page is about.
  4. Check every image has alt text.
  5. Show the results as a table, then the 3 most important fixes. Don't edit anything until I say so.

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.