muchiny

This skill should be used when the user asks to "run a security scan", "check for vulnerabilities", "audit compliance", "check certificate expiry", "scan open ports", or mentions security reviews, CIS benchmarks, or compliance assessments on remote servers.

This skill should be used when the user asks to "show me the available tools", "what Docker tools exist", "search for kubernetes tools", "explore the tool catalog", or wants to browse the 476 bridge-mcp tools by group or keyword.

This skill should be used when the user asks to "run a command on a server", "check Docker containers", "restart a service", "read a remote file", "check disk usage", or mentions managing remote infrastructure via SSH. Teaches CLI-first workflow with progressive tool discovery.

Use when the user wants to run a command on or manage a remote host over SSH — a server, Raspberry Pi, VM, NAS, network switch, or air-gapped machine. Triggers: "check/manage my server", "run X on host Y", "ssh into / exec on host", "restart nginx on prod", "docker ps / containers on", "kubectl / k8s pods / helm on the cluster", "tail the logs on", "disk usage / cpu / memory / processes on host", "what's listening on port", "is host reachable", "service status", "configure / validate the bridge". Drives the bridge-mcp CLI (476 SSH tools) — guided setup, status checks, and tool execution.

Use when the user wants to explore, search, or learn what bridge-mcp can do: "what tools are available", "list bridge tools", "find a tool for X", "show docker / kubernetes / systemd / network tools", "search tools for logs / firewall / packages / databases", "which tool groups exist", "what can the bridge do". Progressive discovery across the 476 tools and 77 groups, with token-efficient describe-tool output.

Use when the user says "bridge", "remote", "ssh tool", "run on host", "check host", "configure host", "setup bridge", or wants to manage remote servers or bridge config via CLI.

This skill should be used when the user asks to "deploy to production", "restart a service", "do a rolling update", "canary deploy", "helm upgrade", or "rollout to K8s". Manual-only for safety — requires explicit /ssh-deploy invocation.

This skill should be used when the user asks to "debug my server", "why is prod slow", "check why a service is down", "diagnose disk full", "server is unresponsive", or mentions troubleshooting remote server issues like CPU, memory, disk, or network problems.

Run the `airbnb` CLI binary through a short demonstration sequence — help, search, listing details in JSON, and a multi-fetch analytical command — to verify that the CLI wires through to the shared AirbnbClient and renders output correctly. Use after changing anything under src/cli/, src/application/, or the Display impls on domain types.

List and describe the HTML/JSON test fixtures in tests/fixtures/, and walk through how to capture a fresh fixture from a live Airbnb URL when a parser regression appears. Use when a scraper or GraphQL parser test fails unexpectedly, or when adding coverage for a new Airbnb response shape.

Smoke-test the mcp-airbnb MCP server by building it, sending an `initialize` + `tools/list` JSON-RPC request via stdin, and verifying the response contains the expected 18 tools. Use when you've changed anything in src/mcp/, src/application/, or the AirbnbClient trait and want a quick end-to-end sanity check before running the full test suite.