# AI use cases for Botdirectory AI (elie222/botdirectory.ai) Repo: [elie222/botdirectory.ai](https://github.com/elie222/botdirectory.ai) | Use cases: 4 | Page: https://dedupedai.com/use-cases/elie222-botdirectory-ai/ An open-source, community-maintained directory of ready-to-use agent prompts for Grok Bot, Rakazo, and other agents, with a public read API, JSON feeds, and a pull request workflow for adding bots. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Find a ready-made bot prompt and paste it into your agent: https://dedupedai.com/use-cases/elie222-botdirectory-ai/find-ready-made-bot-prompt/ - Mirror the whole bot directory into your own catalog: https://dedupedai.com/use-cases/elie222-botdirectory-ai/mirror-full-bot-directory-feed/ - Scout new bot listings on a schedule without rereading the full feed: https://dedupedai.com/use-cases/elie222-botdirectory-ai/scout-new-bot-listings-recurring/ - Add your own bot prompt to the directory by pull request: https://dedupedai.com/use-cases/elie222-botdirectory-ai/contribute-bot-by-pull-request/ ## How to find a ready-made bot prompt and paste it into your agent with Botdirectory AI Repo: [elie222/botdirectory.ai](https://github.com/elie222/botdirectory.ai) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Search the directory by keyword, category, or integration and copy a prompt that sets up a scheduled bot. **Who it is for:** A founder or operator who needs an email triage or daily briefing bot and wants a prompt that already works instead of writing one from scratch. **The problem:** Writing a scheduled bot prompt from zero takes time, and it is unclear which integrations a setup needs. **The outcome:** A chosen listing with its integrations and prompt copied into an agent, which then walks through connecting the tools it lists. ### Steps 1. Open https://botdirectory.ai and filter by category or integration, or query `https://api.botdirectory.ai/api/bots?q=slack&category=Ops&page=1&limit=25&sort=newest` with your own keyword. 2. Open the listing you want and read its integrations list and integration_urls. 3. Copy the prompt text from the listing, or use the Add to Grok Bot link when the listing has one. 4. Paste the prompt into Grok Bot, Rakazo, or your agent and follow its steps to connect the listed integrations. 5. Confirm the bot runs on the schedule the prompt describes before you rely on it. ### Prompt to paste into your agent ```text Use the botdirectory.ai API at https://api.botdirectory.ai/api/bots?q=&limit=10 to find listings that match . Return the name, integrations, and detail URL of the top 3 results as a short list, and confirm each result has a non-empty prompt or description before you suggest it. ``` ### Caveat Listings are community-written prompts, so read the integrations and the steps before connecting any account to them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/elie222-botdirectory-ai/find-ready-made-bot-prompt/ ## How to mirror the whole bot directory into your own catalog with Botdirectory AI Repo: [elie222/botdirectory.ai](https://github.com/elie222/botdirectory.ai) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Pull the canonical raw feed once and store every listing in your own system. **Who it is for:** A developer or team lead who wants the full directory inside an internal tool, search index, or dataset. **The problem:** Copying listings by hand does not scale, and paging through search results is slower than one bulk request. **The outcome:** A local copy of every listing in the directory, which can be refreshed or searched without visiting the site. ### Steps 1. Request the canonical raw feed at `https://botdirectory.ai/api/bots.json`. 2. Save the response to a local file with a timestamp in its name. 3. Parse the JSON and load each listing into your own store, keyed by its slug or name. (inferred, check the README) 4. Compare the count and names against the previous snapshot to list what was added or changed. (inferred, check the README) 5. Run `pnpm install` and `pnpm build` only if you also want a local copy of the site source, then check that your store matches the feed. ### Prompt to paste into your agent ```text Fetch https://botdirectory.ai/api/bots.json, save it as bots-.json, and report the total number of listings and the names of up to 5 listings that are new since the last saved file. Verify that the count in the saved file matches the number of entries parsed. ``` ### Caveat The feed reflects whatever the directory publishes at fetch time, so keep dated snapshots if you need an audit trail. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/elie222-botdirectory-ai/mirror-full-bot-directory-feed/ ## How to scout new bot listings on a schedule without rereading the full feed with Botdirectory AI Repo: [elie222/botdirectory.ai](https://github.com/elie222/botdirectory.ai) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Check the small updates feed on a schedule and surface only listings you have not seen. **Who it is for:** An agent operator who runs a recurring scout and wants a cheap daily check for new community bot prompts. **The problem:** Pulling every full prompt on each run is slow and sends the same items again and again. **The outcome:** A recurring report of new listings with their integrations and detail links, with no repeats across runs. ### 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 to paste into your agent ```text Fetch https://botdirectory.ai/updates.json and compare its listing identifiers with the seen list in . Output only the new listings with name, integrations, and detail URL, then write the updated seen list back to . 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/elie222-botdirectory-ai/scout-new-bot-listings-recurring/ ## How to add your own bot prompt to the directory by pull request with Botdirectory AI Repo: [elie222/botdirectory.ai](https://github.com/elie222/botdirectory.ai) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Write one markdown file in bots/, validate it locally, and open a PR that CI checks. **Who it is for:** A prompt writer who has a working scheduled bot setup and wants it listed for others to copy. **The problem:** Good prompts stay private, so other people rebuild the same setup from scratch. **The outcome:** A merged pull request that adds your bot to the directory once CI passes and the change is merged. ### Steps 1. Fork the repo at https://github.com/elie222/botdirectory.ai. 2. Add `bots/.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 to paste into your agent ```text In a fork of https://github.com/elie222/botdirectory.ai, create bots/.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/.md. ``` ### Caveat The README asks for the full contract and quality bar in CONTRIBUTING.md, which you should read before opening the pull request. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/elie222-botdirectory-ai/contribute-bot-by-pull-request/