Vendor collections, marketplaces or community repositories?
Start with your task, provenance and maintenance evidence. Directory inclusion and curated-release approval are separate judgments.
Maintained · Product guidance, not an external skill evaluation
Describe the result you need
Describe the input and expected output in one sentence, such as turning interview notes into findings with evidence references. Check the host and whether network or code execution is permitted. A familiar source does not guarantee a task fit.
Read the original description
Open a source detail page and inspect its purpose, original links, license and maintenance date. Directory labels are editorial metadata, not proof that every package was tested. Confirm current terms and repository status at the original source.
Use the curated library for platform-maintained releases
A curated detail page identifies an exact release. Review safety checks, the public test summary, host checks, permissions and dependencies. If no qualified release fits, research external sources without treating them as already approved packages.
Verify suitability in a separate project
After reviewing limitations and examples, try the release in a test project without production secrets. Record where it works and where it does not. A usage-test summary helps selection but cannot guarantee identical results across models and tasks.