agentleFS
Sign inStart free
hyperlane-xyzhyperlane-xyz/hyperlane-monorepo/.agents/skills/stop-http-registry/SKILL.md

stop-http-registry

Skill76 starsChanged 20 days agoApache-2.0View on GitHub

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. Always run the fallback after TaskStop regardless — it is idempotent if the process is already gone. /warp-deploy-init-route, /warp-deploy-update-owners, /warp-update, /warp-update-extend, /warp-update-resolve-artifacts — every skill that starts the HTTP registry.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Stop the background HTTP registry started via /start-http-registry.

    line 12
  2. Very specific:

    Fallback (minimal-tool sandboxes): if TaskStop doesn't clean up the underlying process and ps / lsof / pkill / fuser aren't available, scan …

    line 15
  3. Very specific:

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

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

    # 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free