Pilot Trust Circle
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This instruction-only skill is coherent, but it automates persistent trust approvals between Pilot agents, so users should verify circle membership before using it.
Install only if you intend to automate Pilot agent trust circles. Before running bootstrap or add-member workflows, review the circle JSON files, confirm each agent identity, and avoid using this skill where you need per-connection manual approval.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the documented workflows can grant trust to Pilot agents, which may affect what those agents can do or exchange with each other.
The skill uses Bash and pilotctl to initiate handshakes and approve nodes. This is aligned with the trust-circle purpose, but it changes agent trust relationships.
pilotctl --json handshake "$NEW_MEMBER" "Member of $CIRCLE" NODE_ID=$(pilotctl --json find "$NEW_MEMBER" | jq -r '.[0].node_id') pilotctl --json approve "$NODE_ID"
Only run these workflows for circles and members you intend to trust, and consider reviewing each node identifier before approving it.
If an incorrect or unintended agent is included in a circle, it may become trusted by other agents in that group.
The skill intentionally creates inter-agent trust relationships. That is disclosed and purpose-aligned, but users should understand the identity and data-sharing implications of mutual trust.
Manage named trust groups where all members automatically trust each other.
Verify agent names and node identities before bootstrapping a circle, and use manual trust approval when you need fine-grained or hierarchical trust.
Stale or modified circle files could cause later workflows to trust agents the user no longer intends to trust.
The skill stores circle membership in persistent local JSON files that are later read to decide which agents to handshake with or approve.
mkdir -p ~/.pilot/circles cat > ~/.pilot/circles/team-alpha.json <<EOF
Keep ~/.pilot/circles files protected and review them before running bootstrap or approval workflows.
The skill may fail or behave unexpectedly on systems without jq installed.
The SKILL.md documents jq as a dependency, while the registry requirements list only pilotctl. This is a metadata completeness issue rather than evidence of malicious behavior.
Requires pilot-protocol skill, pilotctl, and jq.
Ensure jq is installed before use, and the publisher should declare it in the required binaries metadata.