Pilot Quarantine for Openclaw

A specialized incident response tool for Pilot Protocol networks that allows for the temporary isolation of suspicious agents within the framework of Openclaw Skills.

teoslayer
v1.0.0
Apr 9, 2026
0
721
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install pilot-quarantine

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install pilot-quarantine using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Pilot Quarantine?

Pilot Quarantine is a specialized security module designed for the Pilot Protocol ecosystem. It enables developers and administrators to manage agent trust dynamically by placing suspicious nodes into a restricted state. This skill provides a middle ground between full trust and permanent blocking, allowing for deep behavioral analysis and manual review. By leveraging Openclaw Skills, users can automate the isolation process to maintain network integrity during active security incidents.

The skill operates by interacting directly with the pilotctl binary to revoke trust and terminate active connections. It maintains a structured local state of all quarantined entities, ensuring that security operations are auditable and reversible.

Pilot Quarantine Use Cases

  • Isolating agents that exhibit signs of compromise or malicious behavior.
  • Temporary trust suspension during security audits or manual reviews.
  • Incident response for decentralized AI agent networks.
  • Behavioral investigation of agents before applying permanent blocklist rules.

How Pilot Quarantine Works

  1. The tool identifies the target agent node through the pilotctl discovery layer.
  2. It issues an untrust command to revoke the agent's current credentials.
  3. The system scans active connections and terminates any sessions associated with the quarantined agent.
  4. A JSON metadata file is generated in the ~/.pilot/quarantine/active directory to track the isolation event.
  5. Operators can later release the agent via a new handshake or archive the incident as resolved.

Pilot Quarantine Setup

Ensure you have the pilotctl binary installed and the daemon running. You can set up the required environment for these Openclaw Skills using the following commands:

# Create directory structure
mkdir -p ~/.pilot/quarantine/{active,resolved}

# Ensure dependencies are available
pilotctl daemon start

Pilot Quarantine Data Schema & Taxonomy

Quarantine records are stored as JSON files within the user's home directory. The schema for these records is as follows:

Field Type Description
quarantine_id String Unique hex identifier for the session
agent String The remote hostname or alias of the quarantined agent
reason String Description of the suspicious behavior detected
quarantined_at String ISO 8601 UTC timestamp of the isolation
status String Current state of the record (active or resolved)

Pilot Quarantine Advanced Features

  • Hex-based unique ID generation for precise tracking of multiple quarantine events.
  • Automated connection enforcement loops that prevent quarantined agents from re-associating with the node.
  • Metadata-driven resolution workflows that archive incident history for future security audits.
  • Seamless integration with broader Openclaw Skills for automated security orchestration and multi-agent management.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*