Docs: preferred way to list an externally-published community tool package (crewai-perseus-vault)?

[tcconnally]

Question / docs contribution

I maintain a community memory tool for CrewAI, published as a standalone PyPI package crewai-perseus-vault. It exposes two BaseTools — perseus_vault_remember / perseus_vault_recall — giving agents explicit, durable long-term memory backed by Perseus Vault (an open-source, local-first, single-binary memory engine: SQLite + FTS5 + dense hybrid search, optional AES-256-GCM encryption, fully offline).

I'd like to document it, but I want to follow your preferred path rather than guess. Every tool currently under docs/.../tools/ ships inside the crewai_tools package, so there's no existing precedent for listing an externally-published tool package.

What's your preferred mechanism?

1. A docs-only PR adding a page under an existing category (e.g. tools/database-data/) that documents the external crewai-perseus-vault package — analogous to how existing external-service tools are documented; or
2. Contributing the tool into the crewai_tools package (per BUILDING_TOOLS.md); or
3. Something else / a dedicated place for community/third-party tools?

Happy to open the PR immediately once you point me at the right approach. Thanks!

[kmishra1204]

I opened #6460 with a neutral docs clarification for this path. It keeps package READMEs as the source of truth, and adds a checklist for what community tool maintainers should provide when asking for a CrewAI docs mention. I avoided documenting any specific external package so maintainers can decide the general policy first.