بنقرة واحدة
find-ssh-host
Find an SSH host on the local network and update ~/.ssh/config with its current IP address
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Find an SSH host on the local network and update ~/.ssh/config with its current IP address
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Integration for interacting with Google Docs and Google Workspace using the 'gws' CLI.
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service: "plan this issue", "let's design X", "spec this out", "write a plan for #N", "start an MBO / a design doc", or when they're working in a gss draft PR and want to scope the work — even if they don't say "mbo". Routes the task to the right skill workflow (skill-creator, brainstorming→writing-plans, the go/web teams) per docs/mbo/AGENTS.md. Also anchors the objective to a GitHub design issue + a gss draft PR, and — when the plan is ready and it's time to BUILD — asks whether to "break out the work / parallelize / divide it across the teams": a dependency graph of leaf tasks, each a gss feature worker with its own worktree, draft PR, and linked GitHub sub-issue, fanned out via a Workflow, blocking task
Start, restart, or attach to a persistent Claude --remote-control session on any remote SSH host inside a specified git repository. Use this skill whenever the user asks to "start a remote Claude session", "spin up Claude on [host]", "set up remote control on [host]", "launch Claude remotely in [repo]", "start an AI session on [machine]", "restart the remote Claude session", or any variation of establishing or checking a remote Claude Code instance. Also triggers when the user asks to check whether a remote session is running or to get the attach command for an existing one.
Synchronize AI agent skills and build binaries from the dotfiles repository.
Route a task to the right AI team + member (two-level team→member selection)
Query and configure the gsl (Go Status Line) that renders a powerline-style status bar in Claude Code and Antigravity CLI.
| name | find_ssh_host |
| description | Find an SSH host on the local network and update ~/.ssh/config with its current IP address |
This skill uses the ssh-find script to scan the local network for an SSH host
defined in ~/.ssh/config, identify it by hostname, and update the config file
with the host's current IP address.
nmap must be installed (brew install nmap on macOS, sudo apt-get install nmap on Linux)~/opt/bin/ssh-find script must be available (installed via dotfiles)~/.ssh/configAsk the user which SSH host alias they want to find. The alias must match a
Host entry in ~/.ssh/config.
If the user has already provided a host alias in their request, use that value directly without prompting.
Run the following command to confirm the alias exists in the SSH config:
ssh -G <HOST_ALIAS> 2>/dev/null | head -5
hostname and user from the output for the user's reference.~/.ssh/config and stop.Execute the ssh-find script via the terminal. This script is interactive — it
will scan the network and prompt for confirmation before updating the config.
~/opt/scripts/network/ssh-find <HOST_ALIAS>
Important: This command is interactive. It will:
nmap (may require sudo)Is this the correct host for '<HOST_ALIAS>'? (y/n):You must monitor the terminal output and:
(y/n), ask the user whether the displayed hostname matches
the host they are looking for.y or n based on the user's answer.After the script completes, report the outcome to the user:
~/.ssh/config.bak.<HOST_ALIAS> exists in ~/.ssh/wol_map.json, the
ssh-find script will automatically offer to send a Wake-on-LAN magic
packet.wol <MAC_ADDRESS> manually.If the config was updated, verify by running:
ssh -G <HOST_ALIAS> 2>/dev/null | grep "^hostname "
Display the updated hostname value to confirm the change took effect.