system-bridging

Generates idempotent bridge scripts that inject entities and edges between two knowledge systems.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill system-bridging-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-bridging
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/research-tools/research/intelligence-monitoring/system-bridging
Command: npx skills add https://github.com/yakeworld/Synthos --skill system-bridging-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Connecting two separate knowledge systems (e.g., a research repository and a knowledge graph) usually requires ad-hoc scripts that duplicate nodes, create runaway edges, and break on reruns. This Skill produces a structured, idempotent bridge: it surveys both systems first, then generates bridge, query, index, and sync scripts plus protocol documentation. ## Core Features & Use Cases - Structure Survey Before Bridging: Inspects both system roots, counts entities, and detects same-name or same-domain overlaps before creating anything. - Idempotent Incremental Sync: Generates scripts that skip existing nodes and edges, enforce a minimum edge weight (0.3) and adjacency caps to prevent graph explosion, and log every run to bridge-log.jsonl. - One-Way Injection Design: Enforces A-to-B unidirectional injection to avoid bidirectional sync loops, with reverse-query scripts for cross-system lookup. - Use Case: Inject a research system's papers and skills into a knowledge graph, create domain-keyword-based cross-system edges, generate a wiki project entry and bridge protocol document, then rerun the sync safely without duplicates. ## Quick Start Bridge the Synthos repository into the AKNE knowledge graph by generating the bridge, query, index, and sync scripts, then run the first one-way sync and report node and edge changes.

Frequently Asked Questions about system-bridging

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

FAQPage Schema
How do I sync entities between two knowledge systems without duplicates?

Use incremental idempotent sync: check node and edge existence before creation so reruns add nothing. This Skill generates bridge scripts with _exists_node and _exists_edge checks, plus a bridge-log.jsonl record showing new_nodes and new_edges per run.

How to connect a research repository to a knowledge graph?

Survey both systems first, then inject papers and skills as typed nodes and create edges via domain-keyword matching and name overlap. The Skill produces a main bridge script, a reverse query script, an index generator, and a sync daemon script.

Why does keyword-based edge creation cause graph explosion?

Broad keyword matching creates excessive low-value edges that drown the graph. Enforce a minimum edge weight (0.3) and a per-node adjacency cap so weak or over-connected matches are rejected instead of added.

Should system synchronization be bidirectional or one-way?

Use one-way A-to-B injection. Bidirectional sync risks infinite loops where each system re-triggers the other; let system B manage its own changes and use a reverse query script for B-to-A lookups instead.

What happens when the source system root path is missing?

The bridge exits with a non-zero error that includes context and a recovery suggestion rather than silently running empty. No output files are written when required inputs like system_a_root are absent.