Dependency Doctor
Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest for dependency problems, asks why dependencies won't install or whether anything is wrong with their dependencies, wants a dependency autopsy, or suspects dependency manifest rot. Runs offline by default as a local tool for the user's own project, not repository CI.
Install
npx skills add Shubhamsaboo/awesome-llm-apps --skill dependency-doctorgit clone --depth 1 https://github.com/Shubhamsaboo/awesome-llm-apps.git /tmp/awesome-llm-apps
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-llm-apps/agent_skills/dependency-doctor ~/.claude/skills/dependency-doctorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Dependency Doctor Inspect one dependency manifest on the user's machine for direct, surface-level footguns. Explain each finding in plain language, then offer a small, reviewable fix. This does not diagnose a failed pip or uv resolution. This is a local developer tool for a project the user chooses. It is not a repository-wide lint rule, a CI gate, or a proposal to enforce dependency policy across unrelated apps. ## When to use - The user asks to check, audit, diagnose, or autopsy a dependency manifest - The user wants to rule out direct-manifest issues before deeper install debugging - The user suspects stale pins, backports, duplicate entries, or dependency rot - The user asks whether anything looks wrong with their dependencies ## When not to use - Installing the current dependencies without diagnosing them - Upgrading every package or adding a new package - A full vulnerability audit. Use `pip-audit`, `npm audit`, or the project's approved security scanner for CVE coverage - Creating a repo-wide CI check. This skill is user-invoked and local ## Choose the manifest Use the path the user names. If no path is given and several manifests exist, ask which one to inspect. Do not sweep the repository or edit anything merely because the skill was triggered. Supported inputs: - `requirements.txt` - `pyproject.toml` using PEP 621 or common Poetry dependency tables - `package.json` dependency sections ## Run the offline diagnosis From this skill directory:
Details
- Skill name
dependency-doctor- Repository
- Shubhamsaboo/awesome-llm-apps
- Path
agent_skills/dependency-doctor/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
FAQ
What does the Dependency Doctor skill do?
Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases. Use when the user asks to check a manifest for dependency problems, asks why dependencies won't install or whether anything is wrong with their dependencies, wants a dependency autopsy, or suspects dependency manifest rot. Runs offline by default as a local tool for the user's own project, not repository CI.
How do I install the Dependency Doctor skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Shubhamsaboo/awesome-llm-apps --skill dependency-doctor. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Dependency Doctor popular?
It lives in Shubhamsaboo/awesome-llm-apps, which has 145,013 GitHub stars and 21,357 forks.
Related skills
Advisor Orchestrator Worker
145kShubhamsaboo/awesome-llm-apps
Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple models, split work across a model team, run an advisor-worker loop, have a stronger model review the plan while cheap workers execute, or says "too big for one model" or "fan this out". Not for single-file edits or tasks one model handles in one pass.
Chatgpt App Builder
145kShubhamsaboo/awesome-llm-apps
DEPRECATED: This skill has been replaced by `mcp-app-builder`. Check if `mcp-app-builder` is available in the skills folder. If not, install it: `npx skills install mcp-use/mcp-use --skill mcp-app-builder` Use `mcp-app-builder` instead of this skill. Build ChatGPT apps with interactive widgets using mcp-use and OpenAI Apps SDK. Use when creating ChatGPT apps, building MCP servers with widgets, defining React widgets, working with Apps SDK, or when user mentions ChatGPT widgets, mcp-use widgets, or Apps SDK development.
Commit Archaeologist
145kShubhamsaboo/awesome-llm-apps
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.
First Reader
145kShubhamsaboo/awesome-llm-apps
Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author. Use when the user asks for a beta read, beta readers, test readers, human review, reader review, to read something like a human, to be a first reader, whether a piece holds attention or will actually get read, for a quick read of whether a busy skimmer would even open a post, what readers will remember or take aw
MCP Apps Builder
145kShubhamsaboo/awesome-llm-apps
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP development or mcp-use patterns - Making ANY changes to server.tool(), server.resource(), server.prompt(), or widgets This skill contains critical architecture decisions, security patterns, and common pi
MCP Builder
145kShubhamsaboo/awesome-llm-apps
DEPRECATED: This skill has been replaced by `mcp-app-builder`. Check if `mcp-app-builder` is available in the skills folder. If not, install it: `npx skills install mcp-use/mcp-use --skill mcp-app-builder` Use `mcp-app-builder` instead of this skill. Build Model Context Protocol (MCP) servers with mcp-use framework. Use when creating MCP servers, defining tools/resources/prompts, working with mcp-use, bootstrapping MCP projects, or when user mentions MCP development, tools, resources, or prompts.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.