agentleFS
mazreanmazrean/agent-skills/skills/building-static-site-rss-feeds/SKILL.md

building-static-site-rss-feeds

Skill2 starsChanged 8 months agoMITView on GitHub

Creates static websites with RSS/Atom/JSON Feed support for content syndication. Use when building static sites with feeds, implementing RSS in Hugo/Jekyll/custom generators, adding feed autodiscovery, or when user mentions RSS, Atom, feeds, or content syndication.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create static websites that support RSS/Atom feeds for content syndication, allowing readers to subscribe via feed readers.

    line 8
  2. Distinctive:

    Add feed support to a static site:

    line 16
  3. Distinctive:

    Validate: Use W3C Feed Validator

    line 21
  4. Distinctive:

    Recommendation: Use RSS 2.0 for broad compatibility.

    line 31
  5. Very specific:

    Add to <head> of every page:

    line 57
  6. Very specific:

    Absolute URLs: All links must be absolute (https://...)

    line 103
  7. Distinctive:

    Unique GUIDs: Use permalink URLs as identifiers

    line 104
  8. Very specific:

    Add autodiscovery in layouts/partials/head.html:

    line 123
  9. Distinctive:

    Always validate feeds before deployment:

    line 132

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

Building Static Sites with RSS Feeds

Create static websites that support RSS/Atom feeds for content syndication, allowing readers to subscribe via feed readers.

Use this skill when implementing RSS feeds in static sites, choosing feed formats, setting up autodiscovery, or generating feeds from content.

Supporting files: SPECIFICATION.md for feed format details, IMPLEMENTATION.md for code examples.

Quick Start

Add feed support to a static site:

  1. Choose format: RSS 2.0 (most compatible) or Atom 1.0 (more features)
  2. Generate feed XML: From content metadata (title, date, description)
  3. Add autodiscovery: Link tag in HTML head
  4. Validate: Use W3C Feed Validator

Feed Format Selection

FormatBest ForNotes
RSS 2.0Maximum compatibility, podcastsFrozen spec, simpler
Atom 1.0International content, strict validationRFC 4287, better date handling
JSON FeedModern APIs, developer preferenceSimpler parsing, less support

Recommendation: Use RSS 2.0 for broad compatibility. Add Atom if you need internationalization.

Minimal RSS 2.0 Structure

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Site Title</title>
    <link>https://example.com</link>
    <description>Site description</description>
    <lastBuildDate>Sat, 01 Feb 2026 12:00:00 +0000</lastBuildDate>

    <item>
      <title>Article Title</title>
      <link>https://example.com/article</link>
      <description>Article summary or full content</description>
      <guid isPermaLink="true">https://example.com/article</guid>
      <pubDate>Fri, 31 Jan 2026 10:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>

HTML Autodiscovery

Add to <head> of every page:

<link rel="alternate" type="application/rss+xml"
      title="RSS Feed" href="https://example.com/feed.xml">

For Atom:

<link rel="alternate" type="application/atom+xml"
      title="Atom Feed" href="https://example.com/atom.xml">

Go Implementation

Using gorilla/feeds library:

import "github.com/gorilla/feeds"

feed := &feeds.Feed{
    Title:       "Site Title",
    Link:        &feeds.Link{Href: "https://example.com"},
    Description: "Site description",
    Updated:     time.Now(),
}

feed.Items = []*feeds.Item{
    {
        Title:       "Article Title",
        Link:        &feeds.Link{Href: "https://example.com/article"},
        Description: "Article content",
        Id:          "https://example.com/article",
        Created:     time.Now(),
    },
}

rss, _ := feed.ToRss()    // RSS 2.0
atom, _ := feed.ToAtom()  // Atom 1.0
json, _ := feed.ToJSON()  // JSON Feed

Best Practices

Content

  • Full content: Include complete articles, not just excerpts
  • Absolute URLs: All links must be absolute (https://...)
  • Unique GUIDs: Use permalink URLs as identifiers

Performance

  • Keep under 150KB: Some readers have size limits
  • Limit items: 10-20 recent items is typical
  • Support caching: Return ETag and Last-Modified headers

Dates

  • RSS 2.0: RFC 822 format (Sat, 01 Feb 2026 12:00:00 +0000)
  • Atom: RFC 3339 format (2026-02-01T12:00:00Z)

Hugo Integration

Hugo generates RSS automatically at /index.xml. Customize:

layouts/_default/rss.xml

Add autodiscovery in layouts/partials/head.html:

{{ with .OutputFormats.Get "RSS" }}
<link rel="alternate" type="{{ .MediaType }}" href="{{ .Permalink }}" title="{{ $.Site.Title }}">
{{ end }}

Validation

Always validate feeds before deployment:

Common errors:

  • Relative URLs (must be absolute)
  • Invalid date formats
  • Missing required elements
  • Encoding issues with special characters

Checklist

  • Feed generates valid XML/JSON
  • All URLs are absolute
  • Dates use correct format (RFC 822 for RSS, RFC 3339 for Atom)
  • GUIDs are unique and stable
  • Autodiscovery link in HTML head
  • Feed validates with W3C validator
  • Content encoding is UTF-8

Resources

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.