Skip to content
Get packs

Dependency Doctor

Spot common footguns in requirements.txt, pyproject.toml, and package.json before installs fail.

Source Download skill
Repository
Shubhamsaboo/awesome-llm-apps
Stars
143,726
Licence
Apache-2.0
Files
4 files

What it does

Once installed, the agent can inspect one dependency file in your project (requirements.txt, pyproject.toml, or package.json) and flag direct, surface-level problems such as standard-library names published as packages, outdated backports, unpinned dependencies, duplicate entries, and conflicting exact pins. It explains each finding in plain language and proposes a small fix, but waits for your approval before editing anything. An optional online mode can check PyPI for fully yanked Python releases, but only after you approve it.

Great for

  • Python or Node developers who want a quick sanity check of a dependency file before debugging an install
  • Maintainers cleaning up stale or duplicated pins in an old project
  • Anyone who wants a local, offline first pass before running a heavier audit

Skip it if

  • Diagnosing a failed pip or uv resolution in depth: the skill explicitly does not do this, and a clean report is not a full resolver check
  • Vulnerability (CVE) auditing: use pip-audit, npm audit, or your approved scanner instead, since this skill does not cover CVEs
  • Enforcing dependency policy across a whole repository or CI: it is designed as a user-invoked local tool and the reason to avoid CI use is that it only sees the one file you point it at

Try asking

  • “Check my requirements.txt for dependency problems and explain anything risky”
  • “Why won't my dependencies install? Run a dependency autopsy on pyproject.toml”
  • “Review package.json for unpinned or duplicate dependency entries”
  • “Check my requirements file for yanked releases (online, after I approve the PyPI lookup)”
Step-by-step guide: how to use Dependency DoctorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 4 original files, the Apache-2.0 licence and an attribution note.

    dependency-doctor.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip dependency-doctor.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip dependency-doctor.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Name the exact manifest path you want checked; the skill will not sweep the repository on its own
  • Keep the default offline run; approve --online only when you specifically want yanked-release checks, since it sends package names and exact pinned versions to pypi.org
  • Review each suggested fix before approving it, and rerun your project's existing install or test command afterward

What's inside

  • README.md
  • references/dependency-pitfalls.md
  • scripts/dep_doctor.py
  • SKILL.md

Redistributed unmodified from Shubhamsaboo/awesome-llm-apps under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.