dependency-research
Research before guessing: official docs first, then repo, changelog, examples, RFCs. Never treat memory as docs.
SKILL.mdskills/core/dependency-research/SKILL.md
GitHubdependency-research
Need it? Prove it. Then pin it, license-check it, and own its updates.
Activate when
- Considering a new dependency, evaluating alternatives, or checking compatibility/version behavior.
Do NOT activate for
- Version-pinned API lookups (see research/documentation-search).
Procedure
- Justify: existing capability → framework-native → stdlib → existing dep → new dep. "Do we need a dependency at all?" first.
- Evaluate candidates: maintenance (releases, bus factor), security history, license compatibility, bundle/runtime cost, API quality, type support, docs, version compatibility with the pinned stack.
- Check supply chain: advisory history, maintainer trust, dependency-confusion risk; record the decision rationale.
- Install pinned (lockfile updated), minimal scope; add a removal path note.
- Verify: build + tests green, license check recorded,
auditclean or findings triaged.
References
- Related:
../../research/dependency-evaluation/,../../security/secrets-supply-chain/.