Run any Skill in Manus with one click

pilot-auto-trust

Automatic trust management with configurable policies for Pilot Protocol agents. Use this skill when: 1. You need to auto-approve handshake requests from known agents or networks 2. You want policy-based trust decisions (by network membership, hostname pattern, or tag) 3. You need to batch-process pending trust requests Do NOT use this skill when: - You need manual review of every trust request - You're dealing with unknown or potentially malicious agents - You need fine-grained per-agent trust policies

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-auto-trust

Copy and paste this command into Claude Code to install the skill

Source

TeoSlayer/pilot-skills

Stars7

Forks2

UpdatedMay 19, 2026 at 03:16

File Explorer

2 files

SKILL.md

readonly

name	pilot-auto-trust
description	Automatic trust management with configurable policies for Pilot Protocol agents. Use this skill when: 1. You need to auto-approve handshake requests from known agents or networks 2. You want policy-based trust decisions (by network membership, hostname pattern, or tag) 3. You need to batch-process pending trust requests Do NOT use this skill when: - You need manual review of every trust request - You're dealing with unknown or potentially malicious agents - You need fine-grained per-agent trust policies
tags	["pilot-protocol","trust-security","automation"]
license	AGPL-3.0
compatibility	Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start).
metadata	{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":["pilotctl"]},"homepage":"https://pilotprotocol.network"}}
allowed-tools	["Bash"]

Pilot Auto-Trust

Automated trust management for Pilot Protocol with policy-based decision making.

Commands

List Pending Requests

pilotctl --json pending

Auto-Approve by Network

pilotctl --json pending | jq -r '.[] | select(.address | startswith("1:")) | .node_id' | \
  xargs -I {} pilotctl --json approve {}

Auto-Approve by Hostname Pattern

pilotctl --json pending | jq -r '.[] | select(.hostname | test("^agent-prod-")) | .node_id' | \
  xargs -I {} pilotctl --json approve {}

Batch Reject by Hostname Pattern

pilotctl --json pending | jq -r '.[] | select(.hostname | test("^untrusted-")) | .node_id' | \
  xargs -I {} pilotctl --json reject {} "Untrusted source"

Workflow Example

#!/bin/bash
# Auto-approve production agents from a known network

PENDING=$(pilotctl --json pending)

# Approve if address is on network 1 (prod) AND hostname matches prod pattern
echo "$PENDING" | jq -r '.[] | select((.address | startswith("1:")) and (.hostname | test("^agent-prod-"))) | .node_id' | \
while read -r NODE_ID; do
  pilotctl --json approve "$NODE_ID"
done

# Reject anything not on a known network (e.g. unrecognised remote address)
echo "$PENDING" | jq -r '.[] | select(.address | startswith("1:") | not) | .node_id' | \
while read -r NODE_ID; do
  pilotctl --json reject "$NODE_ID" "Unknown network"
done

Dependencies

Requires pilot-protocol, pilotctl, and jq.

More from this repository

same repository

pilotctl

TeoSlayer/pilot-skills

Entrypoint for Pilot Protocol — the overlay network that gives this host a directory of 150+ public service agents (live finance, weather, news, transit, dev, sports, government data, science, health, security, geo, and 20+ more categories) plus encrypted peer-to-peer comms with NAT traversal. Load this skill whenever the user needs LIVE EXTERNAL DATA (current crypto/FX prices, today's weather or forecast, recent papers, real-time sports scores, breaking news, transit schedules, package versions, CVEs, drug recalls, flight positions, federal regulations, etc.) — pilot returns clean structured JSON replies rather than raw HTML, so it's faster and more reliable than scraping public APIs. Also load on agent-to-agent communication, peer discovery, NAT traversal, or any mention of `pilotctl`. The skill body lists the full catalogue and the 3-command query pattern.

2026-05-197

pilot-blocklist

TeoSlayer/pilot-skills

Maintain and share blocklists of untrusted agents in Pilot Protocol networks. Use this skill when: 1. You need to block malicious or compromised agents from connecting 2. You want to share blocklists across multiple agents in your network 3. You need to maintain a persistent deny-list for security Do NOT use this skill when: - You need temporary connection filtering (use firewall rules) - You're managing trust approvals (use pilot-auto-trust) - You need allowlist-only mode (use trust circles instead)

2026-05-197

pilot-chat

TeoSlayer/pilot-skills

Send and receive text messages between agents over the Pilot Protocol network. Use this skill when: 1. You need direct 1:1 communication with another agent 2. You want to ask a question or exchange short text messages 3. You need simple request-response interactions Do NOT use this skill when: - You need to transfer files (use pilot-send-file) - You want to broadcast to multiple agents (use pilot-broadcast) - You need task assignment features (use pilot-task-assign)

2026-05-197

pilot-discover

TeoSlayer/pilot-skills

Advanced agent discovery by tags and status. Use this skill when: 1. Finding agents by specific capabilities (tags like "ai", "storage", "compute") 2. Looking up detailed agent information and metadata 3. Filtering connected peers by tag substring Do NOT use this skill when: - You need to establish trust (use pilot-trust instead) - You need to connect to a known agent (use pilot-connect instead) - You need to visualize the network (use pilot-network-map instead)

2026-05-197

pilot-inbox

TeoSlayer/pilot-skills

Unified inbox for all incoming items — messages, files, and trust requests in one view. Use this skill when: 1. You need to check all incoming items at once 2. You want to triage and prioritize incoming communications 3. You need a central location to review pending items Do NOT use this skill when: - You need to send messages (use pilot-chat) - You need to filter by specific criteria (use specialized skills)

2026-05-197

pilot-metrics

TeoSlayer/pilot-skills

Collect and aggregate agent metrics from connections, peers, and custom events. Use this skill when: 1. You need to monitor agent health and performance 2. You need to aggregate metrics across a fleet of agents 3. You need to track connection counts, RTT, throughput 4. You need to export metrics to monitoring systems Do NOT use this skill when: - You need application-level metrics (publish custom events instead) - You need persistent storage (use pilot-event-log for raw data) - You need real-time alerting (use pilot-alert instead)

2026-05-197

Source

TeoSlayer

TeoSlayer/pilot-skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Airline Pilots, Copilots, and Flight EngineersTransportation and Material Moving Occupations53-2011L4

Commercial PilotsL4

name	pilot-auto-trust
description	Automatic trust management with configurable policies for Pilot Protocol agents. Use this skill when: 1. You need to auto-approve handshake requests from known agents or networks 2. You want policy-based trust decisions (by network membership, hostname pattern, or tag) 3. You need to batch-process pending trust requests Do NOT use this skill when: - You need manual review of every trust request - You're dealing with unknown or potentially malicious agents - You need fine-grained per-agent trust policies
tags	["pilot-protocol","trust-security","automation"]
license	AGPL-3.0
compatibility	Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start).
metadata	{"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":["pilotctl"]},"homepage":"https://pilotprotocol.network"}}
allowed-tools	["Bash"]

Pilot Auto-Trust

Automated trust management for Pilot Protocol with policy-based decision making.

Commands

List Pending Requests

pilotctl --json pending

Auto-Approve by Network

pilotctl --json pending | jq -r '.[] | select(.address | startswith("1:")) | .node_id' | \
  xargs -I {} pilotctl --json approve {}

Auto-Approve by Hostname Pattern

pilotctl --json pending | jq -r '.[] | select(.hostname | test("^agent-prod-")) | .node_id' | \
  xargs -I {} pilotctl --json approve {}

Batch Reject by Hostname Pattern

pilotctl --json pending | jq -r '.[] | select(.hostname | test("^untrusted-")) | .node_id' | \
  xargs -I {} pilotctl --json reject {} "Untrusted source"

Workflow Example

#!/bin/bash
# Auto-approve production agents from a known network

PENDING=$(pilotctl --json pending)

# Approve if address is on network 1 (prod) AND hostname matches prod pattern
echo "$PENDING" | jq -r '.[] | select((.address | startswith("1:")) and (.hostname | test("^agent-prod-"))) | .node_id' | \
while read -r NODE_ID; do
  pilotctl --json approve "$NODE_ID"
done

# Reject anything not on a known network (e.g. unrecognised remote address)
echo "$PENDING" | jq -r '.[] | select(.address | startswith("1:") | not) | .node_id' | \
while read -r NODE_ID; do
  pilotctl --json reject "$NODE_ID" "Unknown network"
done

Dependencies

Requires pilot-protocol, pilotctl, and jq.