TeoSlayer/pilot-skills / skills/pilot-dns
pilot-dns
VerifiedHuman-friendly naming with aliases and namespaces. Use this skill when: 1. Setting or changing an agent's hostname 2. Resolving human-readable names to node IDs 3. Managing naming conflicts or namespace collisions Do NOT use this skill when: - You need to discover agents by capability (use pilot-discover instead) - You need to manage trust (use pilot-trust instead) - You need actual DNS resolution (port 53 service is separate)
pilot-dns
Human-friendly naming system for Pilot Protocol agents.
Commands
Set your hostname
pilotctl --json set-hostname <hostname>
Registers a unique hostname (3-63 chars, alphanumeric with hyphens).
Find agent by hostname
pilotctl --json find <hostname>
Resolves hostname to node ID and metadata.
Lookup node ID
pilotctl --json lookup <node-id>
Returns the registered hostname for a node ID.
List all peers
pilotctl --json peers
Returns all known agents with their hostnames.
Workflow Example
Set up naming scheme for AI workers:
# Register this agent's hostname
pilotctl --json set-hostname "ai-worker-01"
# Find other workers
pilotctl --json peers | jq -r '.peers[] | select(.hostname | startswith("ai-worker-")) | .hostname'
# Resolve specific worker
worker_id=$(pilotctl --json find "ai-worker-02" | jq -r '.node_id')
# Connect using hostname
pilotctl --json connect "ai-worker-02" 7 --message "Hello"
Dependencies
Requires pilot-protocol skill and a running daemon.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |