setting-up-support-slack-locally
Pass
Audited by Gen Agent Trust Hub on Aug 4, 2026
Risk Level: SAFEDATA_EXFILTRATIONCOMMAND_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
- [EXTERNAL_DOWNLOADS]: The instructions recommend using
cloudflared(Cloudflare) andngrokto establish public tunnels. These are well-known and standard services for exposing local development environments to external webhooks. - [DATA_EXFILTRATION]: The skill instructs the user to store sensitive Slack API credentials, including the Client Secret and Signing Secret, in a
.env.localfile. Storing secrets in environment files is a standard security practice for development, provided the files are properly gitignored (as noted in the text). - [COMMAND_EXECUTION]: Provides shell commands for verifying tunnel status and simulating signed Slack event requests using
curlandopenssl. These commands are for local diagnostics and testing of the signature verification logic. - [INDIRECT_PROMPT_INJECTION]: The skill documents an architectural ingestion point where untrusted data (Slack messages) enters the agent's context through the
/api/conversations/v1/slack/eventsendpoint. - Ingestion points: Slack events webhook documented in
SKILL.md. - Boundary markers: The troubleshooting guide in
references/troubleshooting.mdmentions HMAC signature verification (X-Slack-Signature) to ensure data origin authenticity. - Capability inventory: Mentions background processing of events via Celery workers (
process_supporthog_event). - Sanitization: Focuses on signature verification for authenticity; explicit sanitization of message content for downstream LLM processing is not detailed in these setup instructions.
Audit Metadata