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

How to add your own bot prompt to the directory by pull request with Botdirectory AI

Write one markdown file in bots/, validate it locally, and open a PR that CI checks.

Who it is forA prompt writer who has a working scheduled bot setup and wants it listed for others to copy.

The problemGood prompts stay private, so other people rebuild the same setup from scratch.

The outcomeA merged pull request that adds your bot to the directory once CI passes and the change is merged.

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. Fork the repo at https://github.com/elie222/botdirectory.ai.
  2. Add bots/<slug>.md with frontmatter (name, category, added_at, contributor, integrations) and a second-person prompt that leads with **You…**.
  3. Run pnpm install and then pnpm validate to check every file in bots/.
  4. Open a pull request. CI validates the file, and once merged the bot is live.
  5. If you have an official Grok Bot share link, set grok_share_url in the frontmatter instead of pasting a packed config.

Prompt for your agent

In a fork of https://github.com/elie222/botdirectory.ai, create bots/<slug>.md with valid frontmatter and a prompt that starts with You, then run pnpm validate. Report the validation output and the pull request URL, and verify that the file changes only bots/<slug>.md.

Caveat. The README asks for the full contract and quality bar in CONTRIBUTING.md, which you should read before opening the pull request.

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