Skills connector-slack
📦

connector-slack

v0.0.3 Content revision r1 High Risk ⚙️ External commands🌐 Network access

Connect Caffeine Canisters to Slack

Caffeine canisters need secure Slack messaging without custom HTTP and authentication code. This skill provides an experimental client setup, token guidance, and Motoko examples.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "connector-slack" from https://skillstore.io/skills/caffeinelabs-connector-slack.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-connector-slack/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/caffeinelabs-connector-slack.md Signed manifest GET /api/skills/caffeinelabs-connector-slack/manifest Signed lockfile GET /api/skills/caffeinelabs-connector-slack/lockfile

Test it

Using "connector-slack". Post deployment alerts to the engineering channel as the application.

Expected outcome:

  • Selected a bot token because messages should represent the application.
  • Required scope: chat:write.
  • Invite the Slack app to the engineering channel before testing.

Using "connector-slack". Allow support leads to send approved incident updates to two Slack channels.

Expected outcome:

  • Store the token through the administrator-only setter.
  • Require the support-lead permission before each post.
  • Allow only the two approved channel identifiers and apply rate limits.

Using "connector-slack". Assess whether this connector is ready for production.

Expected outcome:

The connector remains experimental. Verify response decoding, add sender authorization, test Slack error handling, rotate secrets, and monitor rate limits before production use.

Security Audit

High Risk
v1 • 8/19/2026 Open versioned report

All 65 external-command alerts are false positives caused by Markdown backticks and code fences; no Ruby or shell backtick execution exists. The three hardcoded URLs point to official Slack properties and match the connector's declared purpose. The example exposes posting to every authenticated caller, enabling unauthorized Slack messages under the configured workspace credential.

1
Files scanned
259
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

High
SKILL.md:209-215
Slack Posting Lacks Role Authorization
The example rejects anonymous callers but lets every authenticated caller post arbitrary text through the shared bot or user credential.
Lines 209-215 check only caller anonymity before using the shared Slack token; no role, channel, or message authorization is enforced.

Risk Factors

⚙️ External commands (50)
SKILL.md:5 SKILL.md:8 SKILL.md:11 SKILL.md:26 SKILL.md:27 SKILL.md:29 SKILL.md:30 SKILL.md:31 SKILL.md:37 SKILL.md:38 SKILL.md:45 SKILL.md:46 SKILL.md:53 SKILL.md:54 SKILL.md:57 SKILL.md:67 SKILL.md:68 SKILL.md:70 SKILL.md:71 SKILL.md:74 SKILL.md:78 SKILL.md:79 SKILL.md:81 SKILL.md:82 SKILL.md:83 SKILL.md:85 SKILL.md:88 SKILL.md:91 SKILL.md:93 SKILL.md:94 SKILL.md:103 SKILL.md:109 SKILL.md:110 SKILL.md:113 SKILL.md:114 SKILL.md:117 SKILL.md:119 SKILL.md:122 SKILL.md:126 SKILL.md:136-139 SKILL.md:139-142 SKILL.md:144 SKILL.md:146-149 SKILL.md:149-159 SKILL.md:159 SKILL.md:164-166 SKILL.md:166-178 SKILL.md:178-188 SKILL.md:188-190 SKILL.md:190-207
🌐 Network access (3)
SKILL.md:38 SKILL.md:76 SKILL.md:249
Audited by: codex
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/caffeinelabs-connector-slack/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/caffeinelabs-connector-slack/security.svg)](https://skillstore.io/skills/caffeinelabs-connector-slack?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/caffeinelabs-connector-slack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-connector-slack/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/caffeinelabs-connector-slack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

caffeinelabs. (2026). connector-slack security audit report (audit version 1) [Author version 0.0.3]. Skillstore. https://skillstore.io/skills/caffeinelabs-connector-slack/audits/1

BibTeX citation

@techreport{caffeinelabs-caffeinelabs-connector-slack-2026, author = {caffeinelabs}, title = {connector-slack security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/caffeinelabs-connector-slack/audits/1}, note = {Author version 0.0.3} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "connector-slack security audit report (audit version 1)" version: "0.0.3" type: report authors: - name: "caffeinelabs" date-released: "2026-08-19" url: "https://skillstore.io/skills/caffeinelabs-connector-slack/audits/1" identifiers: - type: other value: "skillstore:caffeinelabs-connector-slack:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
100
Maintainability
87
Content
65
Community
91
Spec Compliance

What You Can Build

Add Application Alerts

Send operational notifications from a Caffeine application to a designated Slack channel.

Secure Workspace Setup

Configure a workspace token, minimal scopes, channel membership, and administrator-only secret updates.

Prototype Slack Workflows

Test bot or user message identity before committing to a production integration.

Try These Prompts

Post a Basic Notification 
Add Slack notifications to my Caffeine canister. Use a bot token and post [message] to [channel]. Explain the required setup.
Choose the Token Model 
Compare bot and user tokens for [workflow]. Recommend one, list required Slack scopes, and explain identity and channel access consequences.
Secure Slack Configuration 
Implement administrator-only Slack token configuration and authenticated posting. Restrict senders to [role], allow [channels], and avoid exposing the token.
Design a Resilient Integration 
Design a production hardening plan for this experimental connector. Cover authorization, rate limits, retries, response decoding, observability, secret rotation, and tests.

Best Practices

  • Prefer bot tokens unless a workflow explicitly requires a person's Slack identity.
  • Grant only required Slack scopes and limit posting to approved channels.
  • Protect token updates and message posting with separate role permissions.

Avoid

  • Do not expose Slack tokens to the frontend, logs, URLs, or generated output.
  • Do not permit every authenticated caller to post with a shared workspace credential.
  • Do not present the pre-release connector as production-ready without runtime tests.

Frequently Asked Questions

Which Slack token should I use?
Use a bot token for application messages. Use a user token only when the message must represent a specific person.
Which Slack scope is required for posting?
The basic posting flow requires chat:write. Add other scopes only when the selected API method requires them.
Must the Slack app join the channel?
A bot must usually be invited to each target channel. User tokens inherit the authorized person's channel access.
Does the skill support per-user OAuth?
No. It supports one administrator-supplied bot or user token and does not implement OAuth redirects, exchanges, or refreshes.
Is this connector production-ready?
No. Version 0.0.3 is experimental, and success and error response decoding still need complete runtime verification.
How should posting access be protected?
Require an explicit application role, restrict allowed channels, validate message size, and apply rate controls before using the shared credential.

Developer Details

License

MIT

Author version

v0.0.3

Skillstore revision

r1

Repository

https://github.com/caffeinelabs/skills/tree/4e4462a8296d6300944d55b17feb67bc34ea9508/skills/connector-slack

Ref

7fd79e91da5a0cc369dfba10b3e8ca2534c9aff8

Maintenance freshness

8/19/2026

Usage

0 downloads · 0 views

File structure

📄 SKILL.md