Help us improve
Share bugs, ideas, or general feedback.
From utils
This skill should be used when the user asks to "scan for dependencies", "find plugin dependencies", "generate extends-plugin.json", "discover plugin requirements", or invokes /utils:dependency-scanner. Scans plugin files for patterns indicating dependencies on other plugins or system tools.
npx claudepluginhub aaronbassett/agent-foundry --plugin utilsHow this skill is triggered — by the user, by Claude, or both
Slash command
/utils:dependency-scannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scan plugins for patterns that indicate dependencies on other plugins or system tools.
This skill should be used when the user asks to "scan for dependencies", "find plugin dependencies", "generate extends-plugin.json", "discover plugin requirements", "audit dependencies", "check what this plugin depends on", "list system tool dependencies", "create dependency manifest", or invokes /midnight-plugin-utils:dependency-scanner. Scans plugin files for patterns indicating dependencies on other plugins or system tools.
Guides Claude Code plugin creation, structure (plugin.json, commands/agents/skills/hooks), installation (/plugin), marketplaces, team workflows, testing, debugging, and settings. Delegates to docs-management.
Guides creation, modification, and debugging of Claude Code plugins with schemas, templates, checklists, validation workflows, and troubleshooting. Activates on .claude-plugin/, plugin.json, commands/, skills/, hooks/.
Share bugs, ideas, or general feedback.
Scan plugins for patterns that indicate dependencies on other plugins or system tools.
/utils:dependency-scanner - Scan all enabled plugins/utils:dependency-scanner --plugin <name> - Scan specific plugin/utils:dependency-scanner --marketplace <name> - Scan all plugins from marketplace/utils:dependency-scanner --plugin-dir <path> - Scan local plugin directory/utils:dependency-scanner --marketplace-dir <path> - Scan local marketplace directorySkill(skill="utils:find-claude-plugin-root")
PLUGIN_ROOT=$(python3 /tmp/cpr.py utils)
python3 "$PLUGIN_ROOT/scripts/dependency-scanner.py" [FLAGS] > /tmp/dependency-scan.json
Read /tmp/dependency-scan.json and analyze the matches. The script returns raw pattern matches - the analysis process involves:
/foo:spam, /foo:ham, /foo:eggs into one "foo" dependencyFor plugin dependencies:
/foo:bar, look for plugin named "foo"/bar (no prefix), search all available skillsFor system dependencies:
which <command> to check if installed<command> --version to get versionFor EACH dependency group, use AskUserQuestion to confirm. BATCH similar findings:
Found 3 skills (spam, ham, eggs) from foo@bar-marketplace.
Current installed version: 1.2.3
Add to dependencies?
- Yes, require ^1.2.0 (Recommended)
- Yes, require ^1.0.0
- Yes, as optional dependency
- No, skip this
For system dependencies:
Found system command: gh (used 5 times)
Currently installed: 2.45.0
Add to systemDependencies?
- Yes, require >=2.0.0 (Recommended)
- Yes, require >=2.45.0 (exact current)
- Yes, as optional system dependency
- No, skip this
After all confirmations, build the final JSON:
{
"dependencies": {
"foo": "^1.2.0"
},
"optionalDependencies": {},
"systemDependencies": {
"gh": ">=2.0.0"
},
"optionalSystemDependencies": {}
}
Show the final extends-plugin.json to the user and ask for confirmation before writing.
Write to: <plugin-path>/.claude-plugin/extends-plugin.json
$PLUGIN_ROOT/scripts/dependency-scanner.py - Pattern matching scanner