# Synapse Integration Skill

> Use when global skill for BDB Synapse (3D Codebase Visualizer) integration.

- Skill: `hybridlabor-api/synapse-integration-skill` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hybridlabor-api/synapse-integration-skill`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hybridlabor-api/synapse-integration-skill/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: hybridlabor-api (https://skillmd.com/u/hybridlabor-api)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hybridlabor-api/synapse-integration-skill

---


# BDB Synapse Integration

This skill provides access to BDB Synapse tools (`mindwalk`, `judge`, `adapter`, `citymap`, `model`).
Use these tools to generate spatial 3D maps of codebases and evaluate multi-agent sessions.

- **Initialization:** When starting a new conversation in a project, trigger `synapse map <repo>` to visualize the workspace.
- **Tools:** The agent should use Synapse CLI to understand the codebase context spatially alongside memB and OpenWiki.

## 1. Overview
This skill provides domain-specific logic and rules for its respective BDB pipeline component to ensure standardization across multi-agent workflows.

## 2. When to Use
- Use when specifically requested by the user or triggered by an orchestration agent.
- Use when the current task aligns with the skill's domain.
- Exclude when standard tool execution is sufficient.

## 3. Core Process
1. Read the provided context and ensure preconditions are met.
2. Run the required script or tool and confirm the state change.
3. Verify exit codes, file modifications, or DB counts to guarantee success before reporting completion.

## 4. Common Rationalizations
| Rationalization | Reality |
|---|---|
| "The code change was small, so I skipped updating OpenWiki docs." | Every state change must be reflected in the relevant system records. |
| "The ingest script exited without an error, so the memB index must be updated." | Silent failures happen; explicit verification of the side effect is mandatory. |
| "I'll let the /startcycle proceed without a defined rollback path." | Proceeding without a rollback path corrupts the workflow integrity and safety. |
| "I trust the cached agent registry instead of rescanning after a skill change." | Caches stale out quickly; explicit rescans prevent ghost failures. |

## 5. Red Flags
- Bypassing the verification step after a script execution.
- Proceeding to the next pipeline stage without confirming the previous stage's side effects.
- Ignoring domain-specific constraints listed in this skill.

## 6. Verification
- [ ] Verified script exit codes are explicitly checked.
- [ ] Confirmed target files or database records reflect the expected change.
- [ ] Ensured no silent failures were ignored before reporting success.