agentleFS
AkashPriyadarshiiAkashPriyadarshii/jev-seo/skills/jev-audit/SKILL.md

jev-audit

Skill100 starsChanged 9 days agoMITView on GitHub

Audit any site or docs folder for SEO and GEO with jev-seo. Use when the user asks to audit SEO, check rankings, score AI visibility, validate schemas, inspect robots.txt, crawl for broken links, or gate a deploy on search health.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. OneWave-AI/claude-skills★ 378same name
    2. Flyozzzz/omp-tandem-public★ 3same name
    3. idogoldd/skills★ 1same name
    4. kk29siisu129t-debug/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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:

    Keep crawls polite: default 50 pages, robots.txt honored.

    line 27

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

Audit with the jev-seo binary. Prefer JSON output when chaining commands. Never invent scores; every number comes from a command.

Fast paths

  • Full site picture: jev-seo crawl <url> --max-pages 50 then jev-seo llms <domain>.
  • Docs folder gate: jev-seo audit docs/ --min-pass 60 --html report.html --md report.md.
  • One question, one answer: jev-seo geo <file> --query "<query>", jev-seo robots <domain>, jev-seo schema <file>, jev-seo sitemap <url>.
  • MCP over stdio: jev-seo mcp. Remote: https://jev-seo.de.deplexo.com/mcp.

Reading output

  • Health, Score, and Grade lines are deterministic 0-100 values with A-F grades.
  • Top Actions are ranked by impact with effort bands; ids like RULE-R01 map to the rule registry (R01-R64).
  • Completeness says what was skipped (caps, missing sitemap, missing robots). A capped crawl is a sample, not a verdict.
  • --json keeps stdout machine-clean; progress goes to stderr.

Rules for agents

  1. Crawl before judging. Never score pages the crawl has not fetched.
  2. Quote the completeness line alongside any score.
  3. Gate deploys with audit --min-pass or crawl health deltas, not vibes.
  4. Keep crawls polite: default 50 pages, robots.txt honored.

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.