bysirkirby· 23 skills
Activate when working on Claude plugin configuration, MCP transport behavior, or plugin release mechanics in unifi-mcp. Covers: keeping UNIFI_MCP_HTTP_FORCE at its safe default in apps/*/config/config.yaml for all three apps (network, protect, access); the stdio-primary transport pattern in transport.py and why asyncio.wait(FIRST_COMPLETED) must not be reintroduced; local development with claude --plugin-dir and its marketplace-cache blind spot; running check-prereqs.sh before plugin setup; writing Bash 3.2-compatible shell scripts for plugins/; multi-target plugin support for Claude, Codex, and OpenClaw targets; atomic version sync across plugin manifests; and issuing no-op patch releases when only plugin config or scripts change. Apply even if the user doesn't explicitly mention transport races — activate whenever plugin behavior, MCP tool availability, or plugin-scoped shell scripts are being modified.
$npx -y skills add sirkirby/unifi-mcp --skill claude-plugin-config-transportInstalls into the current project.
Run `npx skills use "https://github.com/sirkirby/unifi-mcp" --skill "sirkirby/unifi-mcp/claude-plugin-config-transport"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/sirkirby/unifi-mcp" that are relevant to the current task. Run `npx skills add "https://github.com/sirkirby/unifi-mcp"` and select the relevant skills, then follow their instructions.