Monitor industry and competitor blog posts
blog-feed-monitorskillsetup L2★679
gooseworks-ai/goose-skills ↗What it does
Scrape blog posts via RSS feeds with optional Apify fallback
Best for
Monitoring competitor or industry blogs for keyword mentions when the blog has a public RSS feed — not for blogs without feeds or real-time monitoring.
Inputs
- · Blog URL(s) (comma-separated)
- · Optional: keywords to filter (comma-separated, OR logic)
- · Optional: date range (days back, default 30)
- · Optional: max posts to return (default 50)
Outputs
- · JSON or summary format of blog posts
- · Title, publication date, content excerpt
- · Direct feed URL if discovered
Requires
- · RSS/Atom feed discovery (built-in)
- · Apify token (optional, for JS-heavy site fallback)
Preconditions
- · Target site must have RSS feed or be JS-renderable (for Apify fallback)
- · If Apify mode: token must be in env or --token flag
Failure modes
- · Fails silently if RSS feed path is non-standard
- · Apify fallback actor (jupri/rss-xml-scraper) unverified recently — may require updates
- · Keyword filtering is client-side only — cannot filter by feed entry content, only title/description
- · JS-heavy sites without RSS feed require Apify credits
Trust signals
- · Three modes explicitly documented (auto, RSS-only, Apify-only)
- · Feed discovery probes 7 common paths (/feed, /rss, /atom.xml, /feed.xml, /rss.xml, /blog/feed, /index.xml)
- · CLI reference table with all flags and defaults
- · Free RSS mode requires zero API keys or tokens
- · Supports both RSS 2.0 and Atom formats