utils:dependency-scanner
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.
What this skill does
# Dependency Scanner
Scan plugins for patterns that indicate dependencies on other plugins or system tools.
## Usage
- `/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 directory
## Workflow
### Step 1: Generate CPR Resolver
```bash
Skill(skill="utils:find-claude-plugin-root")
```
### Step 2: Run the Scanner Script
```bash
PLUGIN_ROOT=$(python3 /tmp/cpr.py utils)
python3 "$PLUGIN_ROOT/scripts/dependency-scanner.py" [FLAGS] > /tmp/dependency-scan.json
```
### Step 3: Read and Interpret Matches
Read `/tmp/dependency-scan.json` and analyze the matches. The script returns raw pattern matches - the analysis process involves:
1. **Filter internal references**: If Skill A in plugin X references Skill B also in plugin X, that's NOT a dependency
2. **Group by source**: Combine `/foo:spam`, `/foo:ham`, `/foo:eggs` into one "foo" dependency
3. **Identify source**: For each group, determine which plugin/marketplace provides it
4. **Classify**: Determine if it's a plugin dependency or system dependency
### Step 4: Determine Dependency Sources
**For plugin dependencies:**
- Search installed plugins for matching skill/command names
- Check marketplace plugins if not found in installed
- If skill is `/foo:bar`, look for plugin named "foo"
- If skill is `/bar` (no prefix), search all available skills
**For system dependencies:**
- Run `which <command>` to check if installed
- Run `<command> --version` to get version
- Do web search for installation instructions if needed
### Step 5: Batch Confirmations with User
For 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
```
### Step 6: Build extends-plugin.json
After all confirmations, build the final JSON:
```json
{
"dependencies": {
"foo": "^1.2.0"
},
"optionalDependencies": {},
"systemDependencies": {
"gh": ">=2.0.0"
},
"optionalSystemDependencies": {}
}
```
### Step 7: Confirm and Write
Show the final `extends-plugin.json` to the user and ask for confirmation before writing.
Write to: `<plugin-path>/.claude-plugin/extends-plugin.json`
## Key Principles
- **Script does pattern matching only** - returns potential matches
- **LLM interprets** - groups, filters, identifies sources
- **User confirms everything** - never auto-write
- **Batch similar findings** - don't ask 3 times for same plugin
- **False positives are OK** - better than missing dependencies
## Additional Resources
### Scripts
- `$PLUGIN_ROOT/scripts/dependency-scanner.py` - Pattern matching scanner
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.