DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to pull feeds for a topic from the JSON catalog with Tidings RSS

Have an agent read data/feeds.json and list feeds for a chosen bundle with their feed URLs.

Who it is forA developer or automation builder who needs a structured list of feed URLs for a topic to feed into a pipeline.

The problemFeed lists in OPML are hard to filter programmatically, and a topic search across hundreds of sources is slow by hand.

The outcomeA filtered list of feed names, homepages, and RSS URLs for one bundle, returned as structured data.

What you need first

  • An OPML-compatible feed reader, such as Tidings on macOS 12 or later
  • Internet access to download the OPML files from GitHub releases
  • Optional: a terminal, if you want to verify the SHA-256 checksums

Steps

  1. Open data/feeds.json in the Tidings RSS repository on GitHub or from a local clone.
  2. Find the bundle names in each feed's bundles field, such as ai, research, or podcasts.
  3. Filter the records to the bundle you want and keep the source name and feed URL fields.
  4. Check a few returned feed URLs in a browser or reader to confirm they load.

Prompt for your agent

Read data/feeds.json from the fuxiaoai/tidings-rss repo and return every feed whose bundles include <bundle-name> as a JSON list of name and feed URL. Verify that the count matches the bundle size shown in the README table for that bundle.

Caveat. The README says the catalog was last checked on 2026-10-01 and feeds move or disappear, so filtered lists can go stale.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page