Canonical: https://botbento.com/usecases/audit-a-developer-tool-directory-for-stale/
Format: Markdown representation of the public HTML page.

# Audit a developer-tool directory for stale or unverifiable claims

[Research](https://botbento.com/usecases/research/) · Intermediate

Cross-check each listing against its own docs and flag the drift

Tool directories age fast: a capability gets claimed on the card, half-documented on the vendor site, and the screenshot stops matching the product. The bot works through a batch of listings, tests each claim against the tool's own documentation, and records where the evidence is thin, missing or contradicted, leaving a review queue instead of silent edits.

## Quick answers

**What does it do?** Cross-check each listing against its own docs and flag the drift. Result: Flagged review queue.

**What does it need?** Tools: Google Sheets, Browser, Docs. Intermediate: some setup. The prompt includes an approval step.

**How do I run it?** On a schedule: Weekly listing audit batch. Copy the prompt below into a bot in BotBento.

## How it works

1. On a schedule: Weekly listing audit batch
2. Then: Check claims against vendor docs
3. Result: Flagged review queue

## Prompt to start with

```text
You receive a batch of directory listings in a spreadsheet. For each one, open the vendor's own documentation and check whether every claimed capability, comparison and screenshot is actually supported there. Mark each claim as supported, unverified or contradicted, and add a short note naming the evidence that is missing. Do not edit the directory, publish changes or contact vendors yourself; write findings into the review queue and wait for the user's approval before anything is updated or sent.
```

## Tools it uses

Browser, Docs, Google Sheets

## Works with

BotBento

## Tags

research, data-quality, directory, verification

## Source

[Show HN: ADE Index – a sourced and ranked index of 975 agentic coding tools](https://news.ycombinator.com/item?id=50554973) — Hacker News · checked 2026-11-21

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-21: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-21 · Updated 2026-11-21 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Verifying claims in online articles and media](https://botbento.com/usecases/verifying-claims-in-online-articles-and-media/) — Extract factual statements from content and cross-check them against reliable reference sources.
- [Venue directory data enrichment and verification](https://botbento.com/usecases/venue-directory-data-enrichment-and-verification/) — Cross-reference geographic map listings with official venue websites and update directory records.
- [Check sales transcript budget figures for arithmetic conflicts](https://botbento.com/usecases/check-sales-transcript-budget-figures-for-arithmetic/) — Extract numeric claims and flag mismatches before handoff
