Pilot Compliance Governance Setup

Deploy a compliance and governance system with 4 agents. Use this skill when: 1. User wants to set up automated compliance enforcement 2. User is configuring...

This skill appears to do what it says (set up four governance agents) but you should be cautious before running it. Key actions to take before installing: 1) Verify the provenance and integrity of the pilotctl and clawhub binaries (are they from a trusted, signed source?). 2) Inspect the specific pilot-* packages clawhub will install — each may request external credentials or add network connectors. 3) Plan where signing keys and any webhook/slack credentials will be stored and who can access them; the skill does not declare these needs. 4) Be careful when executing the handshake steps: automated trust between agents can expose data flows if endpoints are compromised. 5) If possible, test the setup in an isolated environment or staging cluster first. Providing the actual URLs/repositories for the pilot-* packages, a list of expected credential names for connectors, and details on where keys are stored would raise my confidence and could change this assessment to benign.

Type: OpenClaw Skill Name: pilot-compliance-governance-setup Version: 1.0.0 The skill bundle provides a legitimate orchestration setup for a four-agent compliance and governance system (policy engine, auditor, certifier, and reporter). It uses platform-specific tools like `pilotctl` and `clawhub` to manage dependencies, configure local manifests in `~/.pilot/setups/`, and establish inter-agent communication channels. The instructions in SKILL.md and README.md are consistent with the stated purpose and do not contain any indicators of malicious intent, data exfiltration, or unauthorized execution.