add-slack — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited add-slack (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Adds Slack support via the Chat SDK bridge.
NanoClaw doesn't ship channels in trunk. This skill copies the Slack adapter in from the channels branch.
Skip to Credentials if all of these are already in place:
src/channels/slack.ts existssrc/channels/slack-registration.test.ts existssrc/channels/index.ts contains import './slack.js';@chat-adapter/slack is listed in package.json dependenciesOtherwise continue. Every step below is safe to re-run.
git fetch origin channelsgit show origin/channels:src/channels/slack.ts > src/channels/slack.ts
git show origin/channels:src/channels/slack-registration.test.ts > src/channels/slack-registration.test.tsAppend to src/channels/index.ts (skip if the line is already present):
import './slack.js';pnpm install @chat-adapter/[email protected]pnpm run build
pnpm exec vitest run src/channels/slack-registration.test.tsBoth must be clean before proceeding. slack-registration.test.ts is the one integration test: it imports the real channel barrel and asserts the registry contains slack. It goes red if the import './slack.js'; line is deleted or drifts, if the barrel fails to evaluate, or if @chat-adapter/slack isn't installed (the import throws) — so it also implicitly verifies the dependency from step 4. The adapter also calls core's createChatSdkBridge(...); that typed core-API consumption is guarded by pnpm run build.
End-to-end message delivery against a real Slack workspace is verified manually once the service is running — see Next Steps and the webhook setup above.
chat:write, im:write, channels:history, groups:history, im:history, channels:read, groups:read, users:read, reactions:write, files:read, files:writexoxb-...)https://your-domain/webhook/slack — Slack will send a verification challenge; it must pass before you can savemessage.channels, message.groups, message.im, app_mentionhttps://your-domain/webhook/slackAdd to .env:
SLACK_BOT_TOKEN=xoxb-your-bot-token
SLACK_SIGNING_SECRET=your-signing-secretSync to container: mkdir -p data/env && cp .env data/env/env
The Chat SDK bridge automatically starts a shared webhook server on port 3000 (configurable via WEBHOOK_PORT env var). The server handles /webhook/slack for Slack and other webhook-based adapters. This port must be publicly reachable from the internet for Slack to deliver events.
If running locally, discuss options for exposing the server — e.g. ngrok (ngrok http 3000), Cloudflare Tunnel, or a reverse proxy on a VPS. The resulting public URL becomes the base for https://your-domain/webhook/slack.
If you're in the middle of /setup, return to the setup flow now.
Otherwise, run /manage-channels to wire this channel to an agent group.
slackslack:{channelId} for channels (e.g., slack:C0123ABC), slack:{dmId} for DMs (e.g., slack:D0ARWEBLV63)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.