Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

cross-ecosystem-synergy-detection

Automatically discovers useful combinations (synergy pairs) across multiple installed plugins and skills, and presents them as a ranked table. Proactively suggests undiscovered synergies when new projects or skills are registered in the registry. Activates on phrases like "do my installed tools work well together?", "they seem to work in isolation", "find synergies".

chrono-meta · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add chrono-meta/forge-harness --skill cross-ecosystem-synergy-detection

About this skill


name: cross-ecosystem-synergy-detection description: Automatically discovers useful combinations (synergy pairs) across multiple installed plugins and skills, and presents them as a ranked table. Proactively suggests undiscovered synergies when new projects or skills are registered in the registry. Activates on phrases like "do my installed tools work well together?", "they seem to work in isolation", "find synergies". user-invocable: true allowed-tools: ["Read", "Grep", "Glob", "Bash"] model: sonnet complexity_routing: base: sonnet high: opus escalate_when: - cross_project - cold_start

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 reports [NOT-CONFIGURED] and skips its body (see Step 7-1 outcome table).

Exception: Single-component environments (1 or fewer installed → no meaningful activation)

Natural Language Triggers (General user phrasing — activates without internal vocabulary)

Example phrasingIntent
"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
"I just installed something new — check for conflicts with existing setup"Check after adding new component
"I have multiple installs but not sure if I'm using them right"Diagnose installation ecosystem utilization
"Wouldn't this and that work better together?"Explore cross-invocation possibilities
"My tools feel disconnected and inconvenient"Detect namespace/cwd fragmentation
"Wouldn't combining these plugins be more powerful?"Explore component combination synergies
"I feel like there's synergy here — find it"Automatic cross-invocation pair discovery
"Do my harnesses have synergy with each other?"Step 3-b standalone — harness-level scan
"Can I transplant a governance pattern from another project?"Step 3-b standalone
"Could I bring that project's gate over here?"Step 3-b standalone
"하네스끼리 시너지" · "거버넌스 패턴 이식" · "다른 프로젝트 게이트 가져올 수 있나"Step 3-b standalone
"이 하네스에 시너지 몰아줘" · "focus the synergy on this one" · "이거 하나 집중해서 강화"focus mode — Step 3-b + Step 3-c by default
"밖에도 이런 거 있나" · "더 강화할 방법 있어?" · "is there prior art that would make this stronger?"Step 3-c

Step 3-b fires standalone. The last four rows call that step alone; they do not require the full door-④ pass. A request about harnesses is not a request about installed plugins.

Processing Steps (7-step)

Step 1. Installation Inventory Direct Inspection

cat ~/.claude/plugins/installed_plugins.json

Schema (measured 2026-08-11, version: 2) — read this before writing any parser:

{"version": 2,
 "plugins": {                       # DICT, not a list
   "<plugin>@<marketplace>": [      # value is a LIST of entries
     {"gitCommitSha": …, "installPath": …, "installedAt": …,
      "lastUpdated": …, "scope": …, "version": …}
   ]}}

The plugin name is the dict key, not an entry field — entry.get('name') is always None, and iterating for pl in data['plugins'] yields key strings, not entry dicts. gitCommitSha is optional (measured: present on 5 of 11 installs) — see Step 5 drift.

Additional checks:

  • ~/.claude/settings.json enabledPlugins (actually active assets)
  • Check installed_plugins.json ↔ enabledPlugins consistency (catch drift)

Step 2. Asset Matrix Extraction per Component

for T in skills agents commands .mcp.json hooks; do
  if [ -e "$IP/$T" ]; then echo "PRESENT $T"; ls "$IP/$T"; else echo "ABSENT  $T"; fi
done

Extract each asset's frontmatter description + allowed-tools + model. Merge plugin.json keywords.

ABSENT is a state, not a zero. Most plugins ship only a subset (measured on fh-meta: skills/agents present, commands/.mcp.json/hooks absent). Carry ABSENT through to the matrix — an absent asset class must not be counted as "0 assets found", which would read as an inspected-and-empty component.

Step 3. Cross-Invocation Possible Pair Matrix Derivation

Call mechanism compatibility:

  • Skill: Can be called directly as {component-name}:{skill-name}
  • Agent: Can be called directly as {component-name}:{agent-name} via subagent_type
  • Hook: Auto-triggered (no direct cross-component calls)
  • MCP: Per-tool calls (namespace separated)

Step 3-b. Harness-level pattern-transplant scan (conditional default)

Condition: 2+ mapped field-harness tracks exist. 🟥 Establish the count by running bash scripts/mapped_tracks.sh — never by listing tracks/ from the session's cwd. The mapping signal is the presence of tracks/<name>/, and that signal cannot reach a worktree: tracks/** is gitignored, and at least one mapped track is an empty directory git could not carry even if it were not. Measured 2026-08-22, one run: main checkout 11 · worktree 1 — a c

Read the complete source ↗