What problem does it solve?
MCP tools can silently disappear when plugin transport configuration is wrong — a forced HTTP bind in a uvx-launched context cancels the stdio transport with no visible error. This Skill prevents that failure mode and standardizes plugin configuration, shell script portability, and release procedures across the network, protect, and access UniFi MCP apps.
Core Features & Use Cases
- Transport Stability: Enforces the stdio-primary asyncio pattern in transport.py and blocks reintroduction of the unsafe asyncio.wait(FIRST_COMPLETED) anti-pattern that caused silent tool loss (Issue #200 / PR #202).
- Config Flag Governance: Keeps UNIFI_MCP_HTTP_FORCE at its safe default across all three app config.yaml files and audits environment variable injection paths.
- Plugin Lifecycle Management: Covers local development with claude --plugin-dir, check-prereqs.sh pre-flight verification, Bash 3.2-compatible shell scripting for macOS, and atomic multi-target version sync across Claude, Codex, and OpenClaw registries.
- Use Case: When modifying a plugin's set-env.sh script, apply the change to all three plugin directories, verify with /bin/bash on macOS, run check-prereqs.sh, and issue a no-op patch release that atomically updates marketplace.json, .codex-plugin/plugin.json, and .agents/plugins/openclaw/plugin.json.
Quick Start
Ask the assistant to review a planned change to the UniFi plugin transport configuration or shell scripts and verify it follows the stdio-primary pattern and three-app parity rules.