utils:dependency-scanner

Scan plugin code to identify dependencies and output a JSON report.

4|1|Updated Jan 23, 2026

Search Tags:#dependencies #tooling #plugins #marketplace #scan #pattern-matching

Ready to run

npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill utils-dependency-scanner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: utils:dependency-scanner
Source: https://github.com/aaronbassett/aaronbassett-marketplace/tree/main/plugins/utils/skills/dependency-scanner
Command: npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill utils-dependency-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Identify plugin dependencies and required system tools across plugin code, helping teams understand coupling and risk.

Core Features & Use Cases

Dependency detection: scan all enabled plugins to identify required dependencies, skills, and tool references.
Marketplace analysis: compare dependencies across marketplace plugins to surface duplicates or conflicts.
Use Case: When updating a core plugin, reveal all dependent plugins and their version requirements to guide safe changes.

Quick Start

Use the dependency-scanner to analyze plugins and produce a JSON summary. Example command: /usr/bin/python3 plugins/utils/skills/dependency-scanner/scripts/dependency-scanner.py --plugin-dir ./plugins --output dependency-scan.json

Frequently Asked Questions about utils:dependency-scanner

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

FAQPage Schema

How do I scan plugins to identify required dependencies?▼

To scan plugins for required dependencies, run the scanner against your plugin directory to read plugin files, resolve references, and group dependencies by source. It outputs a JSON report detailing all required dependencies and tool references.

What is the best way to check plugin dependencies for a marketplace audit?▼

Checking plugin dependencies for a marketplace audit involves scanning all enabled marketplace plugins to surface duplicate dependencies or conflicts. The scanner compares dependencies across plugins and produces a JSON summary to guide safe updates.

Can I use dependency scanning for CI validation of plugin code?▼

Yes, you can use dependency scanning for CI validation of plugin code. The scanner reads plugin files and resolves references to identify required system tools and skills, outputting a JSON report that can be evaluated in your continuous integration pipeline.

How does pattern matching resolve references in plugin files?▼

Pattern matching resolves references in plugin files by reading the code, identifying required dependencies and tool references, and grouping them by source. This mechanism detects coupling and risk across all enabled plugins or a specific targeted plugin.

Do I need Python to run a plugin dependency scan?▼

Yes, you need Python to run a plugin dependency scan. The scanner is executed as a Python script, reading your plugin directory and generating a JSON summary of required dependencies, skills, and system tools.

What limitations exist when scanning a specific plugin for dependencies?▼

A limitation when scanning a specific plugin for dependencies is that the scanner strictly reads plugin files and resolves references to output a JSON report. It identifies system-tool and plugin dependencies but does not modify the code or automatically resolve version conflicts.