vet-dependencylisted
Install: claude install-skill ValentinNikolaev/agent-skills
# Vet a Candidate Dependency
Evaluate a named package before adopting, replacing, or dropping it. Use current registry, published-artifact, and maintainer evidence. Return a decision with limits; do not modify the project's dependency manifests or install a package into its environment.
## Route precisely
- Use when the decision is whether a specific library can satisfy this project's protocol, schema, API, runtime, or maintenance needs.
- Use `code-review` for a diff that happens to change dependencies; invoke this deeper vetting only when adoption or replacement is the question.
- Use a security audit for a known vulnerability in an already adopted package. Do not turn an ordinary API question into an adoption review.
## Fix the required contract
1. Read repository instructions, manifests, lockfiles, and relevant specification or integration code. Write the required version, protocol revision, runtime range, and observable behavior as exact values. If the project has no fixed contract, state the assumption that drives the comparison.
2. Resolve the package through registry or module metadata to the published artifact and declared source repository. Verify tags, subdirectories, forks, and redirects before attributing repository activity to the artifact. If the source repository cannot be established, mark maintenance evidence unknown rather than substituting a search result.
3. Check the exact published version against the required contract. Prefer source code, package