agentsclimarketplace

Dependency handling

Skill serpro69/claude-toolbox/klaude-plugin/skills/dependency-handling

Minimal by design, explicitly multi-lang, production-ready and battle-tested collection of configs and plugins for your Claude Code agentic development workflows: mcp, configs, skills, agents and more.

Install
npx -y skills add serpro69/claude-toolbox --skill dependency-handling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.

SKILL.md

3.1 KB, 664 tokens by cl100k_base, as published. Nobody here has run it

Dependency & External API Handling

Conventions

Workflow

Mandatory order — lookup before usage. Do not write, modify, or recommend any call, import, config key, or version specifier involving the dependency until you have completed the lookup cascade below. Guessing a signature or API version and fixing it after the fact is the failure mode this skill exists to prevent.

  1. Extract the dependency identity. From the calling context, identify the dependency name, the version constraint (declared or inferred), and the specific API surface being used (function, config key, API version, image tag). This is the minimal scope — enough to drive the lookup, not enough to guess the answer.
  2. Capy search. Search kk:lang-idioms and kk:project-conventions for previously indexed knowledge about this dependency.
  3. Context7 lookup. Use the context7 MCP to fetch documentation. The doc version MUST match the declared dependency version.
  4. Web fallback. Only if context7 has no coverage.
  5. Apply. With verified knowledge now loaded, write or recommend the call, import, or config.

Rules

  1. Prefer the latest stable version when introducing a new dependency. Pin deliberately; don't inherit a stale version by copy-paste.
  2. 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.
  3. Capy search first. Before hitting external docs, search kk:lang-idioms and kk:project-conventions for previously indexed knowledge about the dependency.
  4. 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.
  5. 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.

IaC and config artifacts

The cascade rule (capy-first, context7-second, web-last) applies uniformly to all dependency categories — libraries, SDKs, frameworks, APIs, IaC API versions, CRDs, Helm charts, and container images. Per-domain lookup targets (which context7 library to query, which local command to run, which registry to consult) live in each profile's overview.md under a "Looking up dependencies" heading. When the k8s profile is active, consult ${TOOLBOX_PLUGIN_ROOT}/profiles/k8s/overview.md under the ## Looking up Kubernetes dependencies heading for Kubernetes API versions, third-party CRDs, Helm chart versions, and container image targets.

Gives 0 of the 12 instructions most containers cloud skills give in 664 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • run containers as a non-root userin 66 of 607, across 46 files
  • use multi-stage buildsin 53 of 607, across 44 files
  • use Promise.all for independent operationsin 47 of 607, across 13 files
  • import directly instead of barrel filesin 46 of 607, across 12 files
  • use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • copy dependency files before source codein 36 of 607, across 23 files
  • authenticate server actions like API routesin 35 of 607, across 7 files
  • use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • search capy knowledge base before writing calls
  • use context7 MCP to fetch matching documentation
  • fall back to web search only without context7 coverage
  • extract dependency identity before lookup
  • prefer the latest stable version for new dependencies
  • pin dependency versions deliberately

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.