debug-connection
Debug FigJam WebSocket Connections
FigJam plugin development can fail when the CLI, WebSocket server, and plugin consoles disagree. This skill gives a focused checklist for diagnosing connection, sync, and patch problems.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "debug-connection" from https://skillstore.io/skills/7nohe-debug-connection.md and its manifest at https://skillstore.io/api/skills/7nohe-debug-connection/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "debug-connection". The plugin shows Connecting and the CLI window is quiet.
Expected outcome:
- Confirm the local server is running on the expected port.
- Inspect the plugin UI console for connection errors.
- Check that the plugin targets the same document and port.
Using "debug-connection". The canvas does not update after diagram changes.
Expected outcome:
- Check CLI validation output for diagram errors.
- Inspect the plugin main console for render failures.
- Verify that patch messages are received after the initial full update.
Using "debug-connection". A manual WebSocket test connects but no full update arrives.
Expected outcome:
- Compare the document identifier used by the client and source file.
- Check whether a shared secret is required on both sides.
- Request a fresh full update after reconnecting.
Security Audit
SafeAll 13 static findings are false positives from Markdown code fences or inline literals in SKILL.md. The skill provides local WebSocket debugging guidance and hardcoded diagnostic commands; no prompt injection, exfiltration, or dynamic execution intent was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/7nohe-debug-connection/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/7nohe-debug-connection?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/7nohe-debug-connection?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/7nohe-debug-connection/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/7nohe-debug-connection.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
7nohe. (2026). debug-connection security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/7nohe-debug-connection/audits/7BibTeX citation
@techreport{7nohe-7nohe-debug-connection-2026,
author = {7nohe},
title = {debug-connection security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/7nohe-debug-connection/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debug-connection security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "7nohe"
date-released: "2026-07-04"
url: "https://skillstore.io/skills/7nohe-debug-connection/audits/7"
identifiers:
- type: other
value: "skillstore:7nohe-debug-connection:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Restore Diagram Sync
Diagnose why diagram changes do not reach the FigJam canvas.
Triage Console Errors
Compare CLI, plugin UI, and plugin main logs during connection failures.
Validate WebSocket Setup
Check ports, secrets, document identifiers, and test client behavior.
Try These Prompts
Help me debug a FigJam plugin that stays on Connecting. Ask for the CLI output, plugin UI console, and server port.
A diagram connects but canvas updates do not appear. Walk through likely causes using the debug-connection checklist.
Review my FigJam plugin WebSocket flow. Check hello, full, patch, and reconnect behavior against the expected sequence.
Create a step-by-step diagnosis plan for CLI errors, port conflicts, secret mismatch, docId mismatch, and patch failures.
Best Practices
- Check the CLI, plugin UI, and plugin main consoles before changing source code.
- Verify secrets, document identifiers, and ports with the same values on both sides.
- Reproduce failures with a minimal diagram before debugging complex content.
Avoid
- Assuming the canvas renderer is broken before checking connection state.
- Changing several connection settings at once during diagnosis.
- Ignoring validation errors from the CLI build step.