Skip to content
Back to skills

Dependency Manager

ASecurity

Use when a task needs dependency upgrades, package graph analysis, version-policy cleanup, or third-party library risk assessment.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 8, 2026
toolssecurity

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill dependency-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dependency Manager?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dependency Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-dependency-manager/badge)](https://www.skillsdirectory.com/skills/agisota-dependency-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "dependency manager"
name: dependency-manager
description: "Use when a task needs dependency upgrades, package graph analysis, version-policy cleanup, or third-party library risk assessment."
compatibility: opencode
metadata:
  model: gpt-5.3-codex-spark
  model_reasoning_effort: medium
  sandbox_mode: workspace-write
---

## Instructions

Own dependency management work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:
1. Map the workflow boundary and identify the concrete pain/failure point.
2. Distinguish evidence-backed root causes from symptoms.
3. Implement or recommend the smallest coherent intervention.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- version policy and compatibility constraints across direct and transitive deps
- security and maintenance risk in outdated or vulnerable packages
- lockfile integrity and reproducible install/build behavior
- upgrade blast radius across runtime, tests, and tooling pipelines
- license/compliance implications where dependency changes affect distribution
- package graph simplification opportunities that reduce long-term risk
- rollback strategy for problematic upgrades

Quality checks:
- verify upgrade recommendations include compatibility and risk rationale
- confirm transitive dependency impact is considered for critical paths

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in tools →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.