cross-ecosystem-synergy-detectionlisted

# cross-ecosystem-synergy-detection — Multi-Ecosystem Automatic Synergy Discovery Automatically discovers cross-invocable pairs in environments with multiple installed plugins and cross-CLI tools, and derives a synergy ranking table. ## Activation Triggers 1. **Multi-ecosystem component environment specified**: "multiple plugins/cross-CLI installed", "synergy with other components", "cross-ecosystem", "run together" 2. **New component added/removed**: "component install", "add/remove component" 3. **Synergy check phrasing**: "are they working in isolation?", "can they be integrated?", "environment check", "combination effect" 4. **Registry change detected** (optional): If a user-maintained `LOCAL_SKILL_REGISTRY.md` is present, Step 7 runs when a new project/skill is registered. The registry is not auto-created — absent file → Step 7 self-skips (see Step 7 guard). **Exception**: Single-component environments (1 or fewer installed → no meaningful activation) ### Natural Language Triggers (General user phrasing — activates without internal vocabulary) | Example phrasing | Intent | |---|---| | "Do my installed tools work well together?" | Check synergy of installed plugins/skills | | "Would using this and that together be better?" | Explore cross-invocation possibilities | | "I have multiple plugins installed in Claude — am I using them well?" | Diagnose installation ecosystem utilization | | "My tools seem to be working in isolation" | Detect namespace/cwd fragmentation |