Pilot Http Proxy

Route HTTP requests through Pilot Protocol tunnels. Use this skill when: 1. You need to access HTTP services behind NATs or firewalls 2. You want to proxy HT...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (routing HTTP via Pilot Protocol tunnels), but it can expose local HTTP services to remote networks so you should verify the Pilot tooling and be careful what you map.

Purpose & Capability

Name/description ask for routing HTTP through Pilot Protocol; the only required binary is pilotctl and the SKILL.md only uses pilotctl gateway/daemon commands and curl. The declared requirements align with the stated purpose.

Instruction Scope

Instructions are narrowly focused on running pilotctl commands (daemon start, gateway start/map/list/unmap/stop) and then accessing services via HTTP. This stays within purpose, but these steps explicitly expose local IPs/services to the Pilot overlay — a security-sensitive action that users should understand before mapping hosts.

Install Mechanism

No install spec or code files are present (instruction-only). No binaries are downloaded or written by the skill itself, which minimizes installation risk.

Credentials

The skill requests no environment variables or credentials and only needs the pilotctl binary. That is proportionate to the described functionality.

Persistence & Privilege

Skill is not always-enabled and uses normal autonomous invocation. It notes that root/sudo may be required for ports <1024 — this is expected for binding privileged ports but implies elevated local privileges when used.

Assessment

This skill is internally consistent for exposing and routing HTTP services over the Pilot network, but you should only install it if you trust the pilotctl binary and the Pilot Protocol network operator. Before using: (1) verify pilotctl came from a trusted source and check signatures/hashes, (2) avoid mapping sensitive internal hosts or admin endpoints (you will be making them reachable over the overlay), (3) be aware sudo/root may be needed for low-numbered ports, and (4) review Pilot Protocol documentation and the pilot-protocol skill provenance. If you are unsure about the source (the registry shows 'unknown'), treat the skill as higher risk and prefer running pilotctl manually in a controlled environment rather than granting an agent automated access.

Route HTTP requests through Pilot Protocol tunnels using the gateway subsystem.

Commands

Start Gateway

pilotctl --json gateway start

Map Remote HTTP Service

pilotctl --json gateway map <hostname> <local-ip>

List Mappings

pilotctl --json gateway list

Remove Mapping

pilotctl --json gateway unmap <local-ip>

Stop Gateway

pilotctl --json gateway stop

Workflow Example

#!/bin/bash
# Access remote HTTP API

pilotctl --json daemon start
pilotctl --json find api-server
pilotctl --json gateway start
pilotctl --json gateway map api-server 192.168.100.50

# Access remote service
curl http://192.168.100.50/api/v1/status
curl http://192.168.100.50:8080/metrics

Port Mapping

Gateway forwards common HTTP ports:

• Port 80 (HTTP)
• Port 443 (HTTPS)
• Port 8080 (alternative HTTP)

Dependencies

Requires pilot-protocol skill with running daemon. Root/sudo on Linux for port <1024.