Pilot Slack Bridge

Bidirectional bridge between Pilot Protocol and Slack channels. Use this skill when: 1. You need to send Slack notifications from Pilot agents 2. You want to...

This skill appears to do what it says (bridge Pilot and Slack), but its instructions leave gaps you should clear before installing: 1) Confirm where and how the Slack webhook secret is provided — SKILL.md uses $SLACK_WEBHOOK but the skill doesn't declare it; avoid pasting workspace webhooks into untrusted contexts. 2) The inbound flow requires a separate HTTP relay (slack_relay.py) that is not supplied — inspect or implement that relay yourself; don't run unknown code. 3) Examples use jq and python3; ensure those binaries are available and from trusted sources. 4) Check what pilotctl --json set-webhook does and where it stores the webhook (config file, daemon memory) so you know where the secret will reside. 5) If you want to proceed, run this in an isolated environment or with least privilege, and consider restricting the Slack webhook to a workspace/channel you control. If the publisher can provide the missing relay code and a clear list of required env vars/binaries, that would raise confidence.

Type: OpenClaw Skill Name: pilot-slack-bridge Version: 1.0.0 The skill implements a bidirectional Slack bridge using an external binary (`pilotctl`) and references an unprovided Python script (`slack_relay.py`). It contains a workflow that starts a daemon with a `--public` flag and enters a loop to execute local commands (e.g., `pilotctl peers`) based on incoming Slack messages, effectively creating a remote control interface. While these features support the stated purpose, the combination of a public listener, remote command execution, and missing dependencies poses a significant security risk.