agentleFS
Sign inStart free
RelayStackRelayStack/astro-seo-skill/SKILL.md

astro-seo

Skill0 starsChanged 24 days agoMITView on GitHub

Implement SEO on Astro static sites: generate llms.txt, sitemap.xml, robots.txt, add JSON-LD schema (LocalBusiness, Service, FAQPage), submit URLs via IndexNow, run the GEO/AI-search launch checklist. Triggers on: astro seo, llms.txt, json-ld, sitemap, indexnow, robots.txt, schema markup, structured data, geo, ai search, astro launch.

  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 1

    1. RelayStack/astro-seo-toolkit★ 7100% same

    Edited · 0

    None found.

    Wrote their own version · 2

    1. jdevalk/skills★ 100same name
    2. Lexington-Themes/astro-skills★ 2same 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.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Default to implement when the request is vague ("seo this site", "launch checklist").

    line 28
  2. Distinctive:

    Verify with the audit command.

    line 41

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Astro SEO

Zero-dependency Node scripts in scripts/ plus Astro wiring guides in references/. Node 18+, no installs. Scripts run standalone (node scripts/<name>.mjs; usage errors list the flags) and as imports. scripts/integration.mjs writes every file in one pass.

Commands

User saysYou do
implementFull wiring into an Astro project (section below)
audit [path]Run every check in references/audit.md against source or dist/, report pass/fail
schema [page]Emit JSON-LD with scripts/json-ld.mjs; per-page recipes in references/astro-wiring.md
generateWrite llms.txt + sitemap.xml + robots.txt in one pass with scripts/integration.mjs
llms-txtGenerate public/llms.txt from the content dir, then validate it
llms-fullInline full page bodies into public/llms-full.txt (companion for agents that need more than the index)
sitemap / robotsGenerate public/sitemap.xml / public/robots.txt
submit [urls]IndexNow the changed URLs after deploy
geoWalk references/geo.md item by item, fix or file issues for each gap

Default to implement when the request is vague ("seo this site", "launch checklist").

Implement

  1. Locate the content dir (src/content/**, else src/pages/**) and the canonical URL (astro.config.mjs → site). Ask for the URL if site is unset.
  2. Best option when the project can take a dev dependency: add the integration to astro.config.mjs so the files regenerate on every build. npm install -D astro-seo-toolkit import astroSeo from "astro-seo-toolkit/integration"; → integrations: [astroSeo({ contentDir: <content> })]
  3. Otherwise generate into the project's public/ with a single command: node scripts/integration.mjs --dir <content> --site <url> --out <project>/public (or one file at a time: node scripts/llms-txt.mjs, scripts/sitemap.mjs, scripts/robots.mjs)
  4. Schema: one toScript(...) block per page type in the Astro layout via set:html (recipes in references/astro-wiring.md). Every public page gets exactly one valid JSON-LD block.
  5. Build hook: prepend generation to the project's build script so the files never go stale.
  6. Verify with the audit command. Fix failures, never hand-wave them.
  7. Post-deploy: submit changed URLs with scripts/indexnow.mjs (needs the site's IndexNow key file in place).

Ground rules

  • llms.txt is not a Google lever (Google ignores it). It serves Claude/GPT/Perplexity agents. Say so when asked.
  • AI citations require normal indexation first: sitemap submitted, URLs indexed. No index, no citations.
  • --disallow-ai only on explicit owner opt-out; it also kills AI citations.
  • references/ load on demand: astro-wiring.md for implementation detail, audit.md for verification, geo.md for launch review.

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.

Check your setup, free