メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
SOC 職業分類に基づく
| name | ssh-audit |
| description | 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. |
| argument-hint | <host> [quick|full|network|compliance] |
| compatibility | 2.1+ |
Run security audits on a remote server via bridge-mcp CLI.
Delegation: Use a general-purpose agent (via the Agent tool) to run these commands in isolation, so verbose scan output does not pollute the main conversation.
Parse $ARGUMENTS: first word = host, second word (optional) = scope (default: quick).
Fast security overview — run this first:
# Open ports
bridge-mcp tool ssh_port_scan host=HOST --json
# Certificate expiry
bridge-mcp tool ssh_cert_expiry host=HOST --json
# Fail2ban status
bridge-mcp tool ssh_fail2ban_status host=HOST --json
# Firewall rules
bridge-mcp tool ssh_firewall_list host=HOST --json
# Listening services
bridge-mcp tool ssh_exec host=HOST command="ss -tlnp" --json
Network-focused security assessment:
# SSL/TLS audit
bridge-mcp tool ssh_ssl_audit host=HOST --json
# Port scan
bridge-mcp tool ssh_port_scan host=HOST --json
# Active connections
bridge-mcp tool ssh_net_connections host=HOST --json
# DNS configuration
bridge-mcp tool ssh_net_dns host=HOST --json
Standards-based compliance check:
# CIS Benchmark
bridge-mcp tool ssh_cis_benchmark host=HOST --json
# STIG check
bridge-mcp tool ssh_stig_check host=HOST --json
# Compliance score
bridge-mcp tool ssh_compliance_score host=HOST --json
# Full compliance report
bridge-mcp tool ssh_compliance_report host=HOST --json
Comprehensive audit — combines all scopes plus vulnerability scanning:
Run all commands from quick, network, and compliance scopes, then add:
# SBOM generation
bridge-mcp tool ssh_sbom_generate host=HOST --json
# Vulnerability scan
bridge-mcp tool ssh_vuln_scan host=HOST --json
# SELinux / AppArmor status
bridge-mcp tool ssh_selinux_status host=HOST --json
bridge-mcp tool ssh_apparmor_status host=HOST --json
# Security audit log
bridge-mcp tool ssh_security_audit host=HOST --json
# User accounts review
bridge-mcp tool ssh_user_list host=HOST --json
Produce a structured report: