CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, tool-wrapping skill body: executable commands, a documented output schema, an approval-gated fix workflow with explicit re-verification, and a clean two-file bundle used at the right moments. The only cost is mild repetition of the local-tool scope boundary across three sections, which slightly inflates token use without adding guidance.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains what a manifest or package manager is, and every section instructs rather than describes. It falls at the 4 anchor ("efficient; minor instances of over-explanation") because the local-tool/not-a-CI-gate boundary is repeated three times (intro paragraph, "When not to use", "Do not introduce a new CI gate" in the fixes section) and could be trimmed to one statement. It is not a 5 ("every token earns its place") given that repetition, and clearly not a 2 ("noticeably verbose").

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands for both modes ("python3 scripts/dep_doctor.py /path/to/requirements.txt --json" and the --online variant), a concrete JSON report shape showing the exact fields to present, and a specific fix recipe per finding kind. This matches the 5 anchor ("copy-paste ready code or commands; specific examples cover the common cases"); the same command covers all three manifest types, so the 4 anchor's "minor gaps" fit is worse.

5 / 5

Workflow Clarity

The sequence is explicit with checkpoints: choose the named manifest (ask when ambiguous), run the offline diagnosis, read the reference, present findings ordered by severity, ask permission before the online check, wait for approval before edits, then "rerun the offline diagnosis and the project's existing install or test command" — a genuine validate-fix-retry feedback loop for the semi-destructive manifest edits. Error handling is also specified ("Network failures become low-severity findings instead of hiding the offline diagnosis"), matching the 5 anchor rather than the 4 anchor's "minor validation gaps".

5 / 5

Progressive Disclosure

The bundle structure matches the body's claims: scripts/dep_doctor.py exists as the self-contained engine (493 lines) and references/dependency-pitfalls.md exists as a one-level-deep reasoning guide, both listed in a "Files" section with accurate one-line descriptions. The detailed reasoning content (why each footgun matters, pin-hygiene steps) is correctly pushed to the reference and surfaced exactly when needed ("Read references/dependency-pitfalls.md before presenting findings"), matching the 5 anchor ("clear overview with well-signaled one-level-deep references").

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, information-dense description: concrete capabilities, explicit 'Use when' triggers with natural synonyms, and clear scope boundaries in third person. Its only weakness is claiming an install-failure trigger that the skill body explicitly disclaims, creating minor overlap risk with resolver-debugging and security-audit skills.

DimensionReasoningScore

Specificity

The description names the three concrete input types ("requirements.txt, pyproject.toml, and package.json dependency manifests") and enumerates the full set of concrete check categories ("standard-library shadowing pins, abandoned backports, unpinned dependencies, and obvious intra-manifest conflicts, plus opt-in PyPI yanked releases"). Coverage is comprehensive with no vague filler, matching the 5 anchor; the 4 anchor ("minor gaps in coverage") fits worse since every capability category is explicitly listed.

5 / 5

Completeness

Both halves are explicit: the "what" is the enumerated set of manifest checks, and a literal "Use when..." clause gives concrete trigger phrases. This matches the 5 anchor ("clearly and explicitly answers both what AND when with concrete trigger phrases"); the 4 anchor requires a 'when' that could be more explicit, which is not the case here.

5 / 5

Trigger Term Quality

It includes multiple natural phrasings users would actually say ("check a manifest for dependency problems", "why dependencies won't install", "whether anything is wrong with their dependencies") plus distinctive synonyms ("dependency autopsy", "dependency manifest rot") and the literal file names of all three supported manifests, matching the 5 anchor's comprehensive coverage including synonyms and file extensions. The 4 anchor ("a few natural terms missing") fits worse; even stale-pin intent is covered via "dependency manifest rot".

5 / 5

Distinctiveness Conflict Risk

The niche is well-drawn (named manifest files, enumerated footgun categories, "surface-level direct-dependency", "not repository CI"), but the trigger "asks why dependencies won't install" invites resolver/install-debugging requests that the skill body explicitly disclaims ("This does not diagnose a failed pip or uv resolution"), and "check a manifest for dependency problems" has minor overlap with vulnerability-audit skills. This places it at the 4 anchor ("mostly distinct; minor overlap risk with closely related skills") rather than the 5 anchor's minimal conflict risk.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Shubhamsaboo/awesome-llm-apps

Path

agent_skills/dependency-doctor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.