Maintain JSON blocklists of untrusted Pilot Protocol peers.
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-blocklist
Please help me install this Agent Skill. Skill: pilot-blocklist Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-blocklist Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-blocklist
Blocklists untrusted Pilot Protocol peers to prevent unwanted connections and enable secure, shared denial data across agents.
Install the Pilot Protocol daemon and enable blocklist enforcement on your agents.
High-intent search queries and answers about installing and using this skill.
To block untrusted peers in a Pilot Protocol network, you use pilot-blocklist commands to untrust, reject, and deny connections by hostname and node_id. The system maintains a persistent JSON blocklist at ~/.pilot/blocklists/default.json.
Yes, you can synchronize blocklists across multiple Pilot Protocol agents to enforce shared denial data. This cross-agent security workflow ensures all nodes reject pending handshakes from blocked agents in real time.
Yes, you need the pilotctl daemon running to enforce a peer blocklist and reject pending handshakes. The enforcement relies on this background service alongside the pilot-blocklist commands.
Real-time blocklist enforcement rejects pending handshakes from blocked agents by checking connections against the active deny list. It prevents unwanted connections immediately as untrusted peers attempt to join the network.
The best way to manage shared denial data across agents is maintaining a persistent JSON blocklist that synchronizes across the network. This approach ensures consistent trust management and prevents unwanted connections globally.
TeoSlayerExpose Pilot Protocol daemon operations as MCP tools.
thatrebeccaraeAudit code pushes for secrets and PII before pushing to remotes.
chunkydotdevDiagnose email sender reputation issues and create recovery plans.
dreadnodeBypass 403 and 401 access control errors from WAFs, proxies, and CDNs.
