skill-dependency-manager

Analyze skill dependency graphs, detect cycles, and assess upgrade impact across contracts.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill skill-dependency-manager-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-dependency-manager
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/skill-dependency-manager
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill skill-dependency-manager-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing dependencies between skills and artifacts becomes error-prone as a catalog grows: missing edges, circular references, and unclear upgrade blast radius can silently break compositions. This Skill parses skill contracts to build a verified dependency graph and report actionable findings. ## Core Features & Use Cases - Dependency Graph Generation: Builds directed graphs of skill-to-skill dependencies and artifact producer/consumer relationships from contract declarations. - Cycle and Conflict Detection: Identifies cycles, unreachable nodes, missing dependencies, and conflicting ownership chains with concrete node paths. - Upgrade Impact Assessment: Enumerates downstream dependents and compatibility risk points before a contract lifecycle change. - Use Case: Before introducing a new composition edge or changing a skill's lifecycle status, run this Skill to confirm the graph stays acyclic and to see exactly which downstream skills would be affected. ## Quick Start Ask the agent to generate the skill dependency graph and report any cycles or missing dependencies before adding a new composition edge.

Frequently Asked Questions about skill-dependency-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect circular dependencies between skills?

Run the dependency analysis to build a directed graph from contract-declared edges, which detects cycles automatically. Every cycle finding includes a concrete node path so you can trace and break the loop.

How to assess upgrade impact before changing a skill contract?

The upgrade impact assessment enumerates all downstream dependents of a skill and flags compatibility risk points. Impact paths are traceable from the source change to each affected dependent.

What is the difference between skill-dependency-manager and dependency-maintenance?

skill-dependency-manager handles the skill and artifact dependency graph, while dependency-maintenance covers application package dependencies. Use this Skill only for contract-level composition edges, not npm or package manager dependencies.

What inputs does the dependency graph analysis require?

It requires skill metadata and artifact ownership inventory from skill-inventory outputs, plus contract-declared composition edges and optional version constraints. The Skill fails closed if inventory artifacts are unavailable or inconsistent.

Can this Skill automatically fix dependency problems it finds?

No, it is analytical and read-only by default. Any dependency remediation that mutates contracts requires explicit approval through its approval gates before changes are made.