sitemapkit
SitemapKit discovers and extracts URLs from website sitemaps using three tools: discover_sitemaps finds all sitemap files for a domain by checking robots.txt and common paths; extract_sitemap retrieves URLs from a specific sitemap URL; and full_crawl discovers all sitemaps and returns every URL across them in one call. Use this skill when users need to find pages on a website, audit site structure, get complete URL lists, or check what pages exist on a domain, even if they don't explicitly mention sitemaps.
git clone --depth 1 https://github.com/aiskillstore/marketplace /tmp/sitemapkit && cp -r /tmp/sitemapkit/skills/0nl1n1n/sitemapkit ~/.claude/skills/sitemapkitSKILL.md
# SitemapKit Use the SitemapKit MCP tools to discover and extract URLs from any website's sitemaps. ## Tools available - **discover_sitemaps** — finds all sitemap files for a domain (checks robots.txt, common paths, sitemap indexes). Use this first when you just want to know what sitemaps exist. - **extract_sitemap** — fetches all URLs from a specific sitemap URL. Use when the user gives you a direct sitemap URL. - **full_crawl** — discovers all sitemaps for a domain and returns every URL across all of them in one call. Use this when the user wants the complete list of pages on a site. ## When to use which tool | User says | Use | |-----------|-----| | "find sitemaps for X" / "does X have a sitemap?" | `discover_sitemaps` | | "extract URLs from X/sitemap.xml" | `extract_sitemap` | | "get all pages on X" / "crawl X" / "list all URLs on X" | `full_crawl` | ## Usage guidelines - Always pass a full URL including protocol: `https://example.com` - `full_crawl` and `discover_sitemaps` only use the domain — paths are ignored - `extract_sitemap` needs the exact sitemap URL, e.g. `https://example.com/sitemap.xml` - Default `max_urls` is 1000. If the user wants more, pass a higher value (up to plan limit) - If `truncated: true` appears in the result, tell the user there are more URLs and suggest increasing `max_urls` - Check `meta.quota.remaining` in the response — if it's low, warn the user proactively ## Error handling | Error | What to tell the user | |-------|-----------------------| | `Unauthorized` | API key is missing or invalid. Get one at https://app.sitemapkit.com/settings/api | | `Monthly quota exceeded` | Plan limit reached. Upgrade at https://sitemapkit.com/pricing | | `Rate limit exceeded` | Too many requests per minute. Wait and retry — the response includes a `retryAfter` timestamp | ## Example interactions **"What pages does stripe.com have?"** → Call `full_crawl` with `url: "https://stripe.com"`, present the URL list. **"Find all sitemaps for shopify.com"** → Call `discover_sitemaps` with `url: "https://shopify.com"`, list the sitemap URLs found and which sources they came from (robots.txt, common paths, etc.). **"Extract https://example.com/sitemap-posts.xml"** → Call `extract_sitemap` with `url: "https://example.com/sitemap-posts.xml"`, present the URLs with lastmod dates if available. **"How many pages does vercel.com have?"** → Call `full_crawl`, report `totalUrls` and whether the result was truncated.
Let Codex use Google Antigravity CLI (agy) for repository exploration, bounded feature work, and project-scale implementation. Use when a Codex task benefits from delegated repository work while Codex retains diff review, verification, repair, and delivery assurance.
Use when replying. Refresh current date and time.
Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.
Design systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.
Use when automating iOS Simulator interactions, capturing screenshots/video, or inspecting accessibility via AXe CLI.
Use when working with Canton Network participants, DAML smart contracts, Splice applications, or debugging LF version and package ID issues.
>
HSK4級レベルから流暢さを目指す学習者向け。中国語表現の使用場面・自然さを分析し、作文を「ネイティブらしい流暢な表現」に改善。bilibili等のコンテンツ理解とネイティブとの会話をサポート。実際の用例をWeb検索で提示