RSS Feed Generator

Generate a validated Atom XML feed from markdown articles with change detection.

6|2|Updated May 21, 2026

Search Tags:#notifications #git commit #change detection #rss #atom #xml validation #feed generation

Ready to run

npx skills add https://github.com/anajuliabit/aeon --skill rss-feed-generator-anajuliabit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: RSS Feed Generator
Source: https://github.com/anajuliabit/aeon/tree/main/skills/rss-feed
Command: npx skills add https://github.com/anajuliabit/aeon --skill rss-feed-generator-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents noisy, unnecessary RSS/Atom updates by generating a validated Atom feed from your articles and notifying subscribers only when the feed content truly changes.

Core Features & Use Cases

Atom feed generation from articles: Creates an Atom XML feed based on markdown articles stored in articles/.
Validation-first safety: Ensures the generated XML is well-formed (uses xmllint when available, otherwise performs basic structural checks) and blocks commits on validation failures.
Change detection with subscriber-aware notifications: Snapshots the previous feed state, regenerates, classifies the outcome (no change vs metadata-only vs content change), commits only when appropriate, and notifies only on meaningful updates.
Use case: Maintain a clean public feed for a documentation or changelog site where new posts should trigger subscriber alerts, but timestamp-only differences should not.

Quick Start

Use the rss-feed skill to generate articles/feed.xml from the current articles/ inputs and commit plus notify only if the feed content has changed.

Frequently Asked Questions about RSS Feed Generator

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

FAQPage Schema

How do I generate an Atom feed from markdown articles without triggering unnecessary subscriber notifications?▼

To generate an Atom feed from markdown articles without triggering unnecessary subscriber notifications, use a change detection workflow that snapshots the previous feed state and only commits or notifies when actual content changes occur, ignoring metadata-only differences like timestamps.

How does change detection work when regenerating RSS feeds from a markdown articles directory?▼

Change detection works by snapshotting previous feed titles, regenerating the XML, and classifying the outcome as no change, metadata-only, or content change, ensuring that commits and RSS subscriber notifications happen only when meaningful updates are detected.

How do I validate Atom XML feeds before committing them to a content syndication workflow?▼

To validate Atom XML feeds before committing them to a content syndication workflow, the feed generation process uses xmllint when available or performs basic structural checks, automatically blocking the commit if the generated XML is not well-formed.

Can I use a custom repository slug when generating an Atom feed for a changelog site?▼

Yes, you can use a custom repository slug when generating an Atom feed for a changelog site by applying an optional repo slug override, allowing you to tailor the feed identity for specific documentation digests or content syndication targets.

What is the best way to automate changelog publishing via RSS without creating subscriber noise from timestamp updates?▼

The best way to automate changelog publishing via RSS without creating subscriber noise is to use a feed generator that distinguishes between actual content changes and metadata-only updates, committing new feed versions and sending notifications only for meaningful RSS_FEED_OK changes.

Why does my Atom feed generation block commits when XML validation fails?▼

Atom feed generation blocks commits when XML validation fails to ensure validation-first safety, guaranteeing that only well-formed XML is published to your content syndication feed and preventing malformed documents from reaching subscribers.