Pilot Dns

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

Security Scan

The skill is internally consistent with a Pilot Protocol naming helper: it only calls the pilotctl CLI, requests no credentials, and has no install steps or unusual system access.

Purpose & Capability

The skill's name/description (human-friendly naming for Pilot Protocol agents) aligns with the runtime instructions, which only invoke pilotctl commands (set-hostname, find, lookup, peers, connect). Requiring the pilotctl binary is reasonable for this purpose.

Instruction Scope

Instructions stay within the naming/lookup scope and do not request unrelated files, credentials, or system paths. One minor inconsistency: example commands use jq for JSON processing but jq is not listed as a required binary; the connect example sends a message to another node (expected for a connect operation) so users should understand that the skill triggers network operations via pilotctl.

Install Mechanism

No install spec is present (instruction-only), so nothing is written to disk by the skill itself. This minimizes install-time risk.

Credentials

The skill declares no environment variables, no credentials, and no config paths. That is proportionate to a CLI-driven naming helper.

Persistence & Privilege

always is false and the skill does not request permanent presence or access to other skills' configs. Model invocation is allowed (platform default) but this is normal and not excessive here.

Assessment

This skill is coherent and low-risk in isolation: it only provides instructions to run the pilotctl CLI and does not request secrets or install code. Before installing, verify you trust the pilotctl binary and the Pilot Protocol daemon (install source, checksum, and homepage), since the skill expects a running daemon and will cause network actions (e.g., connect/send messages). Also note the examples assume jq is available for JSON parsing even though jq is not declared as a required binary; if you don't have jq installed, those example pipelines will fail. If you need stronger assurance, inspect your pilotctl installation and review pilot-protocol's documentation or source before use.

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.