Agent skill · data analytics · aiskillstore
debug-connection
Debug WebSocket connection issues between CLI and FigJam plugin. Use when diagrams aren't syncing, connection fails, plugin shows "Connecting..." indefinitely, or patches aren't being applied to canvas.
Why this skill is useful
Provides specific troubleshooting steps and commands for debugging WebSocket connections in a FigJam plugin context that the AI wouldn't reliably generate on its own.
What it needs
Requires bun, wscat installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
WebSocket Connection Debugging Architecture Common Issues Issue Symptom Solution ------- --------- ---------- CLI not running "Connecting..." indefinitely Start bun run packages/cli/src/index.ts serve diagram.yaml Port in use Connection refused Check lsof -i :3456, use different port Secret mismatch Connects then immediately closes Match --secret value in CLI and plugin YAML errors Connected but no updates Fix validation errors in CLI output docId mismatch No response after hello Ensure plugin docId matches YAML docId Patches not applied Connected, canvas unchanged Check Plugin Main console for render errors Debugging Steps 1. CLI side: Check terminal for errors, verify YAML with bun run packages/cli/src/index.ts build diagram.yaml 2. Plugin UI: Right-click plugin → Inspect → Console for WebSocket events 3. Plugin Main: Figma Desktop → Plugins → Development → Open console Message Flow JSON Import Errors JSON must be an object with version, docId, nodes DSL format: nodes as array IR format: nodes as object (Record) Validation errors shown in alert with path + message Quick Test
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/debug-connection