Suggest Dependencies to Index

To find important project dependencies to add to your knowledge base, this Skill analyzes manifest files like package.json and requirements.txt, then ranks libraries by import frequency in your source code. It provides repository URLs for the top suggested dependencies.

The best way to identify unindexed dependencies is by parsing project manifests such as package.json, requirements.txt, go.mod, and Cargo.toml. The tool scans source code imports, filters out already indexed packages, and suggests the most frequently used libraries.

Yes, you can use dependency analysis to suggest libraries from a Cargo.toml or go.mod file. The Skill parses these manifest files to identify declared dependencies and evaluates their usage frequency by analyzing import statements across your source files.

To rank package dependencies by usage frequency in your source code, the Skill analyzes import statements across your project files. It counts how often each declared library from your manifests appears and prioritizes the most frequently imported ones.

Your dependency indexing setup misses critical libraries during project onboarding because manual selection often overlooks frequently imported packages. This Skill automates discovery by scanning manifests and source code to suggest high-priority dependencies with their repository URLs.