ClawHub

Pilot Dns

v1.0.0

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

⭐ 0· 0·0 current·0 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk97be56t8wwc465ce32hg5yrfh84hrns

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

Binspilotctl

Comments