Agent skill

Debug Transport

Debug and troubleshoot the NetMQ transport layer, port allocation, and device communication.

MITAuto-check passedDevelopment

Install Debug Transport

skills CLI

$ npx skills add lge-ros2/cloisim --skill debug-transport -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install lge-ros2/cloisim debug-transport --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/lge-ros2/cloisim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/debug-transport .claude/skills/debug-transport && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "debug-transport" agent skill from https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport into .claude/skills/debug-transport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-transport", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add lge-ros2/cloisim --skill debug-transport -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install lge-ros2/cloisim debug-transport --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lge-ros2/cloisim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/debug-transport .agents/skills/debug-transport && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "debug-transport" agent skill from https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport into .agents/skills/debug-transport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-transport", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lge-ros2/cloisim --skill debug-transport -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install lge-ros2/cloisim debug-transport --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lge-ros2/cloisim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/debug-transport .cursor/skills/debug-transport && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "debug-transport" agent skill from https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport into .cursor/skills/debug-transport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-transport", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/lge-ros2/cloisim.git --path .github/skills/debug-transport

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add lge-ros2/cloisim --skill debug-transport -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install lge-ros2/cloisim debug-transport --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lge-ros2/cloisim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/debug-transport .gemini/skills/debug-transport && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "debug-transport" agent skill from https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport into .gemini/skills/debug-transport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-transport", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install lge-ros2/cloisim debug-transport

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add lge-ros2/cloisim --skill debug-transport -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/lge-ros2/cloisim.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/debug-transport .github/skills/debug-transport && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "debug-transport" agent skill from https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport into .github/skills/debug-transport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-transport", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add lge-ros2/cloisim --skill debug-transport -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install lge-ros2/cloisim debug-transport --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/lge-ros2/cloisim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/debug-transport .opencode/skills/debug-transport && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "debug-transport" agent skill from https://github.com/lge-ros2/cloisim/tree/main/.github/skills/debug-transport into .opencode/skills/debug-transport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-transport", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: debug-transport
GitHub stars: 176
Token cost: ~1.4k tokens
SKILL.md length: 363 words
Files: 1
Skills in repo: 18
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Debug and troubleshoot the NetMQ transport layer, port allocation, and device communication.

Works in 8 steps: Check Port Allocation → Check Plugin Startup → Verify Thread Health → …
: diagnosing connection failures
SKILL.md covers When to Use, Transport Architecture, Diagnostic Steps and Network Debugging Commands, plus 1 more section
Calls curl

What it does

Debug Transport is an agent skill from lge-ros2/cloisim. Debug and troubleshoot the NetMQ transport layer, port allocation, and device communication. Use when: diagnosing connection failures, debugging message flow, troubleshooting port conflicts, verifying device registration.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. The repository describes itself as: Unity 6 based multi-robot simulator for ROS 2, SDFormat/SDF, LiDAR, camera, depth, IMU, GPS, and large-scale robotics simulation. The licence is MIT.

When your agent uses it

: diagnosing connection failures
Debugging message flow
Troubleshooting port conflicts
Verifying device registration

Example prompts

“/debug-transport”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Check Port Allocation
Check Plugin Startup
Verify Thread Health
Common Failure Modes
Message Flow Debugging
Port Range
Hash-Based Message Tagging
Cleanup Verification

What it can do on your machine

Read from SKILL.md and the folder at commit f4c1f0b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug Transport loads about 1.4k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 363 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from lge-ros2/cloisim at commit f4c1f0b, republished under its MIT licence (© lge-ros2). 363 words, ~1,417 tokens.

Download SKILL.mdSave it as .claude/skills/debug-transport/SKILL.md (or your agent's skills folder).

name: debug-transport
description: Debug and troubleshoot the NetMQ transport layer, port allocation, and device communication. Use when: diagnosing connection failures, debugging message flow, troubleshooting port conflicts, verifying device registration.

Debug Transport Issues

Reference guide for diagnosing and fixing issues in CLOiSim's NetMQ transport layer.

When to Use

Plugin fails to start or register its transport ports
External ROS 2 bridge cannot connect to a device
Messages are not being received or published
Port allocation conflicts
Device appears in device_list but data doesn't flow

Transport Architecture

CLOiSimPlugin                    External Bridge (cloisim_ros)
    ↓                                      ↓
 Transporter                          connects to
    ├── Publisher  (PUB, bind)  ←─── Subscriber (SUB, connect)
    ├── Subscriber (SUB, bind) ←─── Publisher  (PUB, connect)
    ├── Responsor  (REP, bind) ←─── Requestor  (REQ, connect)
    └── Requestor  (REQ, bind) ←─── Responsor  (REP, connect)

All CLOiSim sockets bind on tcp://*:{port}. The bridge connects.

Diagnostic Steps

1. Check Port Allocation

Via WebSocket API:

bash

# Get all registered devices and ports
echo '{"command":"port_list"}' | websocat ws://localhost:8080/control

# Get device map (grouped by model/plugin/parts)
echo '{"command":"device_list"}' | websocat ws://localhost:8080/control

Via code (Unity Console):

csharp

// BridgeManager logs all allocations after world load:
BridgeManager.PrintAllocatedHistory();

// Check if a specific port is allocated:
var port = BridgeManager.SearchSensorPort(hashKey);

Port hash key format: {modelName}{partsName}{subPartsName}{controlKey}

2. Check Plugin Startup

Every plugin fires a Started event. If a plugin doesn't start:

Check PluginStartTracker — it logs which plugins haven't started
Verify SDF <plugin filename="ClassName"> matches the actual C# class name exactly
Check Unity Console for "[Plugin] No plugin(xxx) exist" warnings
Verify OnStart() coroutine completes (must yield return null at the end)

3. Verify Thread Health

csharp

// In a plugin, check if threads are running:
// CLOiSimPluginThread manages background threads
// Each thread has a 50ms timeout join during cleanup

// Thread naming convention:
// Threads are added via AddThread(port, threadFunction, device)
// Thread functions: SenderThread, ReceiverThread, ServiceThread

4. Common Failure Modes

Symptom	Cause	Fix
`"Failed to Bind"` in Console	Port already in use	Kill previous CLOiSim instance; check `ss -tlnp \| grep 49152`
Plugin not in `device_list`	`filename` doesn't match class name	Fix SDF `<plugin filename="">` to match C# class name exactly
TX data not flowing	Device `Mode` mismatch	Ensure device `Mode` matches plugin thread type (TX_THREAD for SenderThread)
RX data not received	Hash mismatch	Verify subscriber hash matches publisher hash
Service timeout	`HandleCustomRequestMessage` not handling request	Add case for the request type in the plugin
`NullReferenceException` in thread	Device component not found	Check `GetComponent<>()` in `OnAwake()`, ensure device is on same GameObject

Show full SKILL.md (113 more words)Show less

5. Message Flow Debugging

TX (publishing) flow:

Device.GenerateMessage() or Device.EnqueueMessage()
  → DeviceMessageQueue.Enqueue()
  → SenderThread: DeviceMessageQueue.Dequeue()
  → Publisher.Publish(data, hash)
  → NetMQ PUB socket send

RX (receiving) flow:

NetMQ SUB socket recv
  → ReceiverThread: Subscriber.Subscribe()
  → Device.ProcessReceivedDeviceMessage()

Service (request/reply) flow:

NetMQ REP socket recv
  → ServiceThread: Responsor receives request
  → CLOiSimPlugin.HandleCustomRequestMessage()
  → Responsor sends response

6. Port Range

Range: 49152–65535 (ephemeral ports)
Allocation: sequential scan from 49152, checks IPGlobalProperties.GetActiveTcpConnections()
Each device port is unique per CLOiSim instance

7. Hash-Based Message Tagging

Each transport connection uses a ulong hash for message routing:

csharp

// Hash is computed from the device path:
// StdHash.Hash64(modelName + partsName + subPartsName + controlKey)

// Publisher tags each message with hash
// Subscriber filters by matching hash
// If hashes don't match, messages are silently dropped

8. Cleanup Verification

On OnDestroy(), plugins automatically:

Join all threads (50ms timeout per step, up to 500ms total)
Dispose Transporter (closes all NetMQ sockets)
Deallocate ports from BridgeManager

If ports aren't freed, check:

_thread.Dispose() is being called
DeregisterDevice() runs (logs removed hash keys)
No orphaned CLOiSimPlugin instances (destroyed GameObjects should trigger OnDestroy)

Network Debugging Commands

bash

# Check which ports CLOiSim is binding:
ss -tlnp | grep -E '4915[2-9]|49[2-9][0-9]{2}|[5-6][0-9]{4}'

# Check WebSocket service:
curl -s http://localhost:8080/

# Test WebSocket commands:
echo '{"command":"fps"}' | websocat ws://localhost:8080/control
echo '{"command":"reset"}' | websocat ws://localhost:8080/control

Adding Debug Logging to a Plugin

csharp

protected override IEnumerator OnStart()
{
	if (RegisterTxDevice(out var portTx, "Data"))
	{
		Debug.Log($"[{name}] TX registered on port {portTx}");
		AddThread(portTx, SenderThread, _sensor);
	}
	else
	{
		Debug.LogError($"[{name}] Failed to register TX device");
	}

	yield return null;
}

Files

Just SKILL.md in .github/skills/debug-transport of lge-ros2/cloisim.

Open the folder on GitHubat commit f4c1f0b

Compare with similar skills

Debug Transport next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug Transport compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Debug Transport this skilllge-ros2/cloisim	176	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Trellis Session Insightmindfold-ai/Trellis	15k	4 repos	~1.7k	Automated safety check: Pass	AGPL-3.0	9 days ago
Native Data FetchingCherryHQ/cherry-studio-app	4k	6 repos	~2.9k	Automated safety check: Notes	MIT	yesterday
Debugging Executionsn8n-io/n8n	207k	—	~2.6k	Automated safety check: Pass	Custom licence	yesterday
Aoti Debugpytorch/pytorch	104k	1 repos	~1.7k	Automated safety check: Pass	Custom licence	yesterday
Herdr Throwaway Reproductionherdrdev/herdr	43k	—	~2.4k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
15k GitHub starsUsed in 4 repos~1.7k tokens
DevelopmentAuto-check passed
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
4k GitHub starsUsed in 6 repos~2.9k tokens
DevelopmentAuto-check: notes
Debugging Executions
n8n-io/n8n
Official
Debug failed or wrong-output workflow executions using executions tools.
207k GitHub stars~2.6k tokensUpdated yesterday
DevelopmentAuto-check passed
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
104k GitHub starsUsed in 1 repo~1.7k tokens
DevelopmentAuto-check passed
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
43k GitHub stars~2.4k tokensUpdated yesterday
DevelopmentAuto-check passed
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
258 GitHub starsUsed in 51 repos~2.4k tokens
DevelopmentAuto-check passed

Questions about Debug Transport

What does Debug Transport do?

Debug and troubleshoot the NetMQ transport layer, port allocation, and device communication. Debug Transport is an agent skill from lge-ros2/cloisim. Debug and troubleshoot the NetMQ transport layer, port allocation, and device communication.

When should I use Debug Transport?

Debug Transport fits situations like: : diagnosing connection failures; debugging message flow; troubleshooting port conflicts; verifying device registration.

How do I install Debug Transport in Claude Code?

Run `npx skills add lge-ros2/cloisim --skill debug-transport -a claude-code`. Or copy the skill folder (.github/skills/debug-transport in lge-ros2/cloisim) into .claude/skills/debug-transport in your project. Claude Code loads it when a task matches its description.

How do I install Debug Transport in Codex?

Run `npx skills add lge-ros2/cloisim --skill debug-transport -a codex`. Or copy the skill folder (.github/skills/debug-transport in lge-ros2/cloisim) into .agents/skills/debug-transport in your project. Codex loads it when a task matches its description.

Can I use Debug Transport in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lge-ros2/cloisim --skill debug-transport -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-transport, .gemini/skills/debug-transport, .github/skills/debug-transport and .opencode/skills/debug-transport in your project.

What does Debug Transport need to run?

Going by SKILL.md and its folder, Debug Transport needs the command-line tools its instructions call (curl).

Does Debug Transport access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Debug Transport safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debug Transport use?

Debug Transport is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug Transport use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debug Transport?

Skills that share tags, products or a category with Debug Transport: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Transport?

lge-ros2 (a GitHub organization) maintains it in lge-ros2/cloisim, which has 176 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 6, 2026.

Source: lge-ros2/cloisim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Debug Transport

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Debug Transport Issues

When to Use

Transport Architecture

Diagnostic Steps

1. Check Port Allocation

2. Check Plugin Startup

3. Verify Thread Health

4. Common Failure Modes

5. Message Flow Debugging

6. Port Range

7. Hash-Based Message Tagging

8. Cleanup Verification

Network Debugging Commands

Adding Debug Logging to a Plugin

Files

Compare with similar skills

Similar skills

More from lge-ros2/cloisim

Related

Questions about Debug Transport