Pilot Consensus
v1.0.0Distributed voting and agreement protocols for multi-agent decision making. Use this skill when: 1. Multiple agents need to agree on a value or decision 2. Y...
⭐ 0· 9·0 current·0 all-time
byCalin Teodor@teoslayer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name and description (distributed voting/consensus) align with the actions in SKILL.md: publishing proposals, sending votes, collecting messages via pilotctl. Requiring pilotctl and a pilot daemon is expected for this purpose. The skill does reference pilot-protocol in the compatibility text, which fits the stated purpose.
Instruction Scope
Instructions are narrowly focused on consensus flows (publish, send-message, received). They do rely on environment variables (e.g., AGENT_ID, CURRENT_TERM, TOTAL_VOTERS, PROPOSER_ADDRESS, PROPOSAL_VALUE, REGISTRY_HOST) and use jq/uuidgen, but the skill does not declare those env vars as required. The commands transmit messages to registry-hosts and peer addresses — expected for consensus, but network transmission is intrinsic and should be expected by users.
Install Mechanism
This is an instruction-only skill (no install spec, no code files), which is low risk from an install-footprint perspective. It does require the pilotctl binary on PATH; no downloads or extract steps are specified.
Credentials
The skill declares no required environment variables or credentials, yet the runtime instructions use several environment variables (agent IDs, terms, voter counts) and rely on helper binaries (jq, uuidgen) mentioned in the Dependencies section but not in the metadata's required bins. This is a documentation/integration gap: nothing requested appears excessive for the purpose, but the skill should explicitly document required env vars and runtime prerequisites.
Persistence & Privilege
always is false and the skill does not request persistent or elevated platform privileges. It does not attempt to modify other skills or global agent config. Autonomous invocation is enabled by default (normal for skills) but not combined with other red flags.
Assessment
This skill appears to do what it claims (coordinate consensus via pilotctl) and is instruction-only, so it won't write code to disk. Before installing or using it, verify you have a trusted pilotctl binary and a properly configured pilot daemon, and confirm the registry host(s) you will publish to are correct and trusted. The SKILL.md expects several environment variables (AGENT_ID, CURRENT_TERM, TOTAL_VOTERS, PROPOSER_ADDRESS, PROPOSAL_VALUE, REGISTRY_HOST) and helper tools (jq, uuidgen) but does not declare them as required — ensure you supply those at runtime. Because the skill publishes messages to network endpoints, only use it with peers and registries you trust. If you need higher assurance, ask the publisher for an explicit list of required env vars and binaries and for guidance on pilotctl authentication and access controls.Like a lobster shell, security has layers — review code before you run it.
latestvk976pf8nrf9bcmtrg7kraqtf4d84hw9h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspilotctl