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

How to scout new bot listings on a schedule without rereading the full feed with Botdirectory AI

Check the small updates feed on a schedule and surface only listings you have not seen.

Who it is forAn agent operator who runs a recurring scout and wants a cheap daily check for new community bot prompts.

The problemPulling every full prompt on each run is slow and sends the same items again and again.

The outcomeA recurring report of new listings with their integrations and detail links, with no repeats across runs.

What you need first

  • A browser or HTTP client to read the site and API
  • Git and a GitHub account to contribute by pull request
  • Node.js with pnpm to run the local validation and build
  • An agent or Grok Bot or Rakazo account to run a copied prompt

Steps

  1. Read the connect guide at https://botdirectory.ai/connect/ for the seen-item workflow it describes.
  2. Fetch the smaller feed at https://botdirectory.ai/updates.json.
  3. Keep a local list of item identifiers from earlier runs and skip any listing already in that list.
  4. For each new listing, record its name, integrations, source link, and canonical detail URL in your report. (inferred, check the README)
  5. Save the updated seen list so the next scheduled run starts from it.

Prompt for your agent

Fetch https://botdirectory.ai/updates.json and compare its listing identifiers with the seen list in <seen-file>. Output only the new listings with name, integrations, and detail URL, then write the updated seen list back to <seen-file>. Verify that no identifier appears twice in the seen file after the run.

Caveat. The seen-item workflow is described on the connect page, so confirm its current steps there before you automate them.

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