Skip to content

hyperlane-xyz/hyperlane-monorepo / .agents/skills/stop-http-registry

stop-http-registry

Verified

Stop the background HTTP registry server started by /start-http-registry — TaskStop / KillShell by the recorded task ID, plus a /proc cmdline-scan fallback for minimal-tool sandboxes with no ps/lsof/pkill/fuser. Referenced by every warp deploy/update skill that starts the registry.

FileKindSize
SKILL.mdskill md1.5 KB
---
name: stop-http-registry
description:
  Stop the background HTTP registry server started by /start-http-registry
  — TaskStop / KillShell by the recorded task ID, plus a /proc cmdline-scan fallback
  for minimal-tool sandboxes with no ps/lsof/pkill/fuser. Referenced by every warp
  deploy/update skill that starts the registry.
---

# Stop HTTP Registry Server

Stop the background HTTP registry started via `/start-http-registry`. Always stop it at the end of the skill — even on failure paths — so no background process is left running.

1. **Primary:** `TaskStop` (or `KillShell`) with the task/shell ID recorded when the registry was started.
2. **Fallback (minimal-tool sandboxes):** if `TaskStop` doesn't clean up the underlying process and `ps` / `lsof` / `pkill` / `fuser` aren't available, scan `/proc` for the registry's cmdline and kill it:

   ```bash
   # Find PIDs matching the registry process — exclude the scanning shell itself
   SELF_PID=$$
   for pid in $(ls /proc | grep -E '^[0-9]+$'); do
     [ "$pid" = "$SELF_PID" ] && continue
     if grep -aql 'http-registry-server\|start:http-registry' /proc/$pid/cmdline 2>/dev/null; then
       echo "killing http-registry pid=$pid"
       kill "$pid" 2>/dev/null || true
     fi
   done
   ```

   Always run the fallback after `TaskStop` regardless — it is idempotent if the process is already gone.

## Consumers

`/warp-deploy-init-route`, `/warp-deploy-update-owners`, `/warp-update`, `/warp-update-extend`, `/warp-update-resolve-artifacts` — every skill that starts the HTTP registry.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall