zhizdev/sitemap
source/skills/sitemap/SKILL.md
Audit an existing sitemap.xml / robots.txt or generate new ones following sitemaps.org protocol and Google Search Central guidance, with a growth-first default that allows every crawler including AI search and AI training bots. Use this skill whenever the user asks to "build a sitemap", "generate sitemap.xml", "audit the sitemap", "refresh sitemap", "write robots.txt", "check robots", "allow AI crawlers", "block AI crawlers", "fix crawl budget", "submit to Google", or any other discovery / indexing configuration task. Output is a valid sitemap.xml (or sitemap index) and/or robots.txt, plus a written audit when auditing.
$ install --global
skillsauthnpx skillsauth add zhizdev/overgrow sitemapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 3:05 AM10.9s1 file scanned
SKILL.md
- name:
- sitemap
- description:
- Audit an existing sitemap.xml / robots.txt or generate new ones following sitemaps.org protocol and Google Search Central guidance, with a growth-first default that allows every crawler including AI search and AI training bots. Use this skill whenever the user asks to "build a sitemap", "generate sitemap.xml", "audit the sitemap", "refresh sitemap", "write robots.txt", "check robots", "allow AI crawlers", "block AI crawlers", "fix crawl budget", "submit to Google", or any other discovery / indexing configuration task. Output is a valid sitemap.xml (or sitemap index) and/or robots.txt, plus a written audit when auditing.
- user-invocable:
- true
- argument-hint:
- [audit | build] [optional: site origin]
- license:
- MIT
- allowed-tools:
- WebSearch,Bash,Read,Edit,Write,Glob,Grep
Overgrow — Sitemap & robots.txt
This skill is the deterministic pipeline for producing and auditing sitemap.xml, sitemap indexes, and robots.txt. It is tuned for growth — by default it invites every compliant crawler, including AI search and AI training bots, unless the user explicitly opts out per user-agent.
Primary reference
Read knowledge/sitemap.md from the plugin root before doing anything. That file is the canonical, rule-by-rule pipeline this skill implements. Follow it exactly. This SKILL.md is the entry-point summary; knowledge/sitemap.md is the source of truth.
Also consult knowledge/geo.md sections on technical SEO and indexability for AI visibility considerations that affect sitemap/robots decisions.
Mode selection
Parse $ARGUMENTS:
audit(or no args, existing sitemap present) → run the audit flow.build(or no args, no sitemap present) → run the generation flow.- A full origin URL like
https://example.com→ use as the canonical origin.
If mode is ambiguous, {{ask_instruction}}
Audit flow
- Read
.overgrow/inventory.mdfor the authoritative page list. If missing, runinitfirst. - Locate existing sitemap(s):
public/sitemap.xml,static/sitemap.xml,sitemap.xml.ts, Next.jsapp/sitemap.ts, framework-generated routes. If none found, switch to build mode. - Locate existing
robots.txt:public/robots.txt,static/robots.txt,app/robots.ts, or config-driven. - Validate against
knowledge/sitemap.md. Report findings:- Protocol violations (invalid URL, missing
<loc>, bad encoding, over 50k URLs in one file, over 50MB uncompressed). - Coverage gaps (pages in inventory missing from sitemap, sitemap URLs missing from inventory — possible 404s or stale entries).
lastmodhygiene (missing, future-dated, identical across all entries).- Canonical mismatches (sitemap URL vs. rendered canonical tag).
- robots.txt issues (blocking assets needed for render, blocking sitemap path, contradictory allow/disallow, outdated AI-bot rules).
- AI-crawler posture (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot — flag if silently blocked).
- Protocol violations (invalid URL, missing
- Write findings to
.overgrow/sitemap-audit.mdwith severity (critical / high / medium / low) and specific fixes.
Build flow
- Read
.overgrow/inventory.mdfor the list of indexable pages. Excludeutilityand anything the user flags. - Collect inputs (see
knowledge/sitemap.md§ "Inputs to collect"). If any input is missing, ask once in a single message. - Generate
sitemap.xmlfollowing the rules inknowledge/sitemap.md. For > 50k URLs, emit a sitemap index plus shard files. - Generate or update
robots.txt. Default posture:open(allow all user-agents, disallow explicit exclusion paths, reference the sitemap). Only switch torestrictedorclosedwhen the user says so — typically for staging, internal, or compliance-locked sites. - Write the files to the project's static root (
public/,static/, framework-specific path). Do not overwrite existing files without asking; produce.next/.proposedvariants if there's an existing file. - Print a short summary: URL count, shard count, AI-crawler posture, where the files were written.
Defaults for AI bots (growth-first)
Unless the user says otherwise, robots.txt explicitly allows:
GPTBot(OpenAI)ChatGPT-UserOAI-SearchBotClaudeBot/anthropic-ai/Claude-WebPerplexityBotGoogle-ExtendedApplebot-ExtendedBingbot(always)CCBot(Common Crawl)
Explicit allow lines beat silence — spell them out so the posture is auditable. If the user wants to restrict one or more, ask for the list and write Disallow: / blocks per user-agent.
Constraints
- Never emit sitemap entries for routes that do not exist in the inventory.
- Never include query-stringed URLs unless the user intentionally exposes them.
- Respect canonical tags — the sitemap URL must match the page's own canonical.
- Follow
knowledge/sitemap.mdfor encoding, escaping,lastmodformatting, and sharding rules. Do not improvise. - Output must pass XML validation against the sitemaps.org schema.
What this skill does NOT do
- Does not submit sitemaps to Search Console / Bing Webmaster — print the URL for the user to submit.
- Does not generate HTML sitemaps (user-facing navigation pages).
- Does not touch
hreflangbeyond noting issues in the audit — i18n link generation lives in a dedicated sitemap that this skill will build if the inventory declares locales.
Related Skills
zhizdev/grow
tools
VerifiedTrustedCommunity
Pull the open Bonemeal action queue (landing pages and blog posts the user has not built yet) via the bonemeal MCP server, let the user pick which ones to build, dispatch each to the spawn-pages or spawn-blogs skill with the action's brief, and mark each completed in Bonemeal once the file is written. Use this whenever the user says "grow", "/grow", "build my Bonemeal queue", "what's in my Bonemeal queue", "build the suggested pages", or wants to act on Bonemeal's content suggestions. Stop and ask the user before marking actions complete the first time, then remember their preference.
5SKILL.mdUpdated Apr 28, 2026
zhizdev/spawn-pages
development
VerifiedTrustedCommunity
Given the product offering and existing page inventory, create new core landing and resource pages (homepage refresh, features, solutions, pricing, comparison, resource hubs, about) that capture core product intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn pages", "generate landing pages", "create marketing pages", "build a pricing page", "add a solutions page", "build out the site", "fill in missing pages", or wants new top-level marketing/product pages. Output is one new page per route in the project's native file format (component or markdown), matching the existing page style and framework idiom.
2SKILL.mdUpdated Apr 21, 2026
zhizdev/spawn-internal-links
development
VerifiedTrustedCommunity
Examine every existing page on the site, build a semantic map across pillars, and add missing internal links so the site becomes a semantic graph anchored on clear topical pillars. Use this skill whenever the user asks to "add internal links", "build internal linking", "build a semantic graph", "link related pages", "strengthen topical authority", "fix orphan pages", "add pillar linking", or wants hub-and-spoke linking between pillars, hubs, and supporting content. Output is an edit list (proposed link insertions) plus optionally direct edits to page source files.
2SKILL.mdUpdated Apr 21, 2026
zhizdev/spawn-blogs
development
VerifiedTrustedCommunity
Given the product and the existing page inventory, identify missing blog topics and generate new blog posts that capture search/AI intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn blogs", "generate blog posts", "expand the blog", "build out a content cluster", "write blog ideas", "cover more search intents", "query fanout for blogs", or wants new long-form content that supports existing pillars. Output is one new post per topic in the project's existing post format (markdown, MDX, component, or CMS migration note), with frontmatter shape mirrored from an existing post.
2SKILL.mdUpdated Apr 21, 2026