fetch-sitemap

Fetches and parses XML sitemaps and RSS/Atom feeds to inventory UK Parliament web pages.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/danbri/forgetmenot --skill fetch-sitemap-danbri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-sitemap
Source: https://github.com/danbri/forgetmenot/tree/main/skills/fetch-sitemap
Command: npx skills add https://github.com/danbri/forgetmenot --skill fetch-sitemap-danbri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the visibility gap where large portions of the UK Parliament web presence, such as corporate, visiting, and library pages, lack structured API representations. It provides a comprehensive way to inventory and track updates across over one million public web pages.

Core Features & Use Cases

  • Comprehensive Enumeration: Recursively parses XML sitemaps to map the entire public web estate, including pages hidden from REST APIs.
  • Update Tracking: Monitors 918 RSS/Atom feeds to track content changes and liveness across the Parliament domain.
  • Use Case: Use this to identify all public-facing pages under the /about/ or /visiting/ sections that are not covered by the official Parliament REST APIs, or to build a real-time feed reader for library updates.

Quick Start

Use the fetch-sitemap skill to enumerate all public URLs from the main parliament sitemap index with a delay of 300 milliseconds between requests.

Frequently Asked Questions about fetch-sitemap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory web pages that lack a structured REST API?

To inventory web pages without a structured REST API, you can recursively fetch and parse XML sitemaps to map the entire public web estate, including hidden corporate and library pages.

How do I track content updates across large RSS and Atom feeds?

You can track content updates by monitoring RSS and Atom feeds to detect content changes and liveness across thousands of public web pages within a large domain.

What is the best way to discover non-API web content on a massive site?

Discovering non-API web content involves recursively parsing XML sitemap indexes to enumerate all public-facing URLs, bridging the visibility gap left by official REST APIs.

Do I need Node.js fetch capabilities to parse large-scale XML sitemaps?

Yes, you need Node.js fetch capabilities to navigate managed web challenges and process large-scale URL datasets when recursively parsing XML sitemaps.

Can I enumerate over one million public web pages without hitting rate limits?

You can enumerate large web estates by implementing a delay, such as 300 milliseconds between requests, to manage server load while recursively fetching XML sitemaps.

Why use XML sitemaps instead of REST APIs for web estate discovery?

Use XML sitemaps when large portions of a web presence lack structured API representations, providing a comprehensive way to inventory and track updates across public pages.