Finding an Existing Tool
New task → existing solution before developing a duplicate
In short
When scripts, agents, and integrations become numerous, a new session only sees the current folder and may re-create an already existing capability.
Outcome
A crawler collects safe capability descriptions into a unified index, search works by function, and prior-art checks become a mandatory input for new development.
How the automation runs
Trigger
An agent session started or a request for a new tool appeared
Automation steps
- Scans authorized description sources without secret content
- Normalizes name, type, purpose, owner, and freshness
- Builds search by capability, not just by name
- Shows nearest matches before design
- Records the decision to extend, link, or create a new capability
Human check
A person defines authorized sources and makes decisions in case of significant overlap; the registry does not open private files or automatically delete similar tools.
Outcome
A crawler collects safe capability descriptions into a unified index, search works by function, and prior-art checks become a mandatory input for new development.
Automation diagram
The overall logic is publicUsing it
When to use it
The ecosystem already has dozens of projects, scripts, or agents, and the team regularly learns about existing solutions too late.
How to verify
Control functional queries find known tools, secret fields are absent from the index, and creating a new project records a prior-art decision.
Tools
Recipe details
Open every recipe through @venturehunter
We ask for no phone number, no password and no Telegram login on the site. @penioza_bot checks your subscription inside Telegram and brings you back here with access to every kit, not just this one recipe.
Need help putting this in place?
We will walk through your process and build this loop around your data, your limits and your people.
Message me — I will help
