Claude-toolbox dependency-handling

Name: dependency-handling
Author: serpro69

install

source · Clone the upstream repo

git clone https://github.com/serpro69/claude-toolbox

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/serpro69/claude-toolbox "$T" && mkdir -p ~/.claude/skills && cp -r "$T/klaude-plugin/skills/dependency-handling" ~/.claude/skills/serpro69-claude-toolbox-dependency-handling && rm -rf "$T"

manifest: klaude-plugin/skills/dependency-handling/SKILL.md

source content

Dependency & External API Handling

Conventions

Read capy knowledge base conventions at shared-capy-knowledge-protocol.md.

Rules

Prefer the latest stable version when introducing a new dependency. Pin deliberately; don't inherit a stale version by copy-paste.
Never assume how an external dependency behaves. If you are not 100% sure of the signature, config, or semantics, look it up. Guessing is the failure mode this skill exists to prevent.
Capy search first. Before hitting external docs, search
```
kk:lang-idioms
```
and
```
kk:project-conventions
```
for previously indexed knowledge about the dependency.
Context7 second. Use the context7 MCP to fetch documentation for libraries, SDKs, APIs, and frameworks.
- IMPORTANT: the doc version MUST match the declared dependency version. A right answer against the wrong version is a wrong answer.
- Only fall back to web search if context7 has no coverage.
Index what you learn. If context7 or web search yields a best-practice nugget that isn't obvious from the docs themselves, index it as
```
kk:lang-idioms
```
so the next agent doesn't pay the lookup cost again.