faucetsdn/udmi/gateway-fieldbus-triage

Claude Code and agent skill by faucetsdn/udmi

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Methodological playbook for triaging gateway proxies, sub-device metadata bindings, and attach/communication status.

Install

npx vskill@latest install faucetsdn/udmi/gateway-fieldbus-triage

SKILL.md

Gateway & Proxy Triage Playbook

1. Principle: Check Gateway Specification & Site Model Bindings

Gateway proxies aggregate multiple physical or virtual sub-devices (e.g., over BACnet or Modbus). Authoritative specs are at:

  • docs/specs/gateway.md
  • docs/specs/proxy.md
  • docs/specs/bacnet.md
  • docs/specs/modbus.md

2. Gateway-Proxy Architecture

  • Gateway Device: Connects directly to the MQTT broker, authenticates with its own credentials, and proxies telemetry and state on behalf of sub-devices.
  • Proxy Sub-Device: Does not connect to MQTT directly. In sites/<site>/devices/<proxy_device>/metadata.json, it binds to its gateway:

``json "gateway": { "gateway_id": "<GATEWAY_DEVICE_ID>" } ``

  • Message Routing & Status Reporting (docs/specs/gateway.md):
  • On startup or config update, the gateway attaches to each configured proxy device.
  • Attach Failures: If the gateway cannot attach to a proxy device, the failure is reported in the state.gateway block of the gateway device's own state message.
  • Local Communication Errors: If the gateway attaches successfully but fails to communicate with the proxy device, the failure is indicated in the proxy device's state.status block or logged in events_system logentries.
  • Config to the proxy device is forwarded by the gateway; state/events for the proxy device are published under the proxy device's ID.

3. Investigation Procedure

  1. Validate Site Model Binding: Call inspect_site_model(site_model="...", device_id="<proxy_device>"). Verify that gateway.gateway_id points to a valid, existing gateway device in the site model.
  2. Inspect Gateway State: Run inspect_message_trace(run_dir="<run_dir>", message_type="state") for the gateway device to check if its state.gateway block reports any attach errors.
  3. Inspect Sub-Device State & Status: Check the proxy sub-device's state.status block and events_system logs for communication or timeout errors.
  4. Inspect Test Execution Logs: Run get_test_logs(test_id="...") to examine driver and orchestrator messages during proxy execution.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
69
Repository forks
61
7-day trend score
26

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/faucetsdn/udmi/gateway-fieldbus-triage/badge)](https://verified-skill.com/skills/faucetsdn/udmi/gateway-fieldbus-triage)

Something wrong with this skill or its page? Tell us.