OpenKnowledgeBank
Bundle catalog

tools bundle

Slack

A free, open-source set of 10 Markdown files for planning, reviewing, and carrying out evidence-based work with Slack.

Use the Slack bundle to review workspace, channel, message, membership, app, workflow, permission, retention, export, and communication evidence before drafting a governance brief.

Project-reviewed beta
Preview contents Download bundle Inspect source

10 Markdown files · 1,194 words · no signup · CC-BY-4.0

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Tool guide

Slack

Defines source-aware team communication and collaboration, evidence handling, and action boundaries.

Read the file

Overview

Slack overview

Use this bundle to structure team communication and collaboration while keeping official-source context separate from account, organization, project, document, or environment evidence.

Read the file

Workflow

Slack source-aware triage

1. State the requested decision or deliverable. 2. Inventory evidence: workspace, organization, channel, and thread scope, message content, timestamp, author, and edit state, membership.

Read the file

Template

Slack communication and governance brief

Review-ready brief for team communication and collaboration, evidence quality, verification, and controlled next actions.

Read the file

Is this bundle right for your task?

Who it is for

  • Slack administrators, operations and collaboration teams, communication owners, security and compliance reviewers, and app integration maintainers

When to use it

  • A workspace, channel, thread, membership, role, or permission question needs current identifiers and administrator evidence reconciled.
  • An app, workflow, integration, token-scope, retention, legal-hold, export, or audit decision needs policy and local state separated.
  • A sensitive or consequential Slack communication needs message provenance, source-of-record context, notification impact, and approval boundaries reviewed.

What you need to provide

  • Workspace and organization identifiers, channel and thread scope, relevant message content and timestamps, author and edit state, membership, roles, permissions, and source-of-record rules.
  • App and integration configuration, scopes without exposed tokens, workflows, retention and legal-hold policy, export availability, administrator policy, audit evidence, communication plan, and approvals.

Tasks and expected outputs

Questions it helps answer

  • Prepare a slack communication and governance brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce review-ready decisions with explicit verification and approval boundaries.

What it helps produce

  • Slack communication and governance brief

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Load the Slack bundle and provide the workspace and channel scope, relevant message or thread evidence, membership and permission context, app scopes, workflow configuration, retention and export policy, audit source of record, proposed communication, and approval owner. Ask the agent to separate observed state from missing evidence and draft a Slack communication and governance brief without sending or changing anything.

Context path: bundles/tools/slack

What the bundle includes

Tools

  • Slack

Frameworks

  • source-evidence matrix
  • team-communication-and-collaboration evidence matrix
  • qualified-review gate

Evaluations

  • Slack source-awareness check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

docs.slack.dev Product, platform, or operating reference for Slack scope and source checks.

Limitations and safe use

Do not use this for

  • Guessing workspace state, channel membership, message content, permissions, app scopes, retention, export availability, or approval; sending or editing messages, inviting users, or changing channels, permissions, retention, apps, workflows, tokens, or exports without explicit confirmation.

Known limitations

  • Use official Slack sources for general context; local team communication and collaboration, configuration, records, values, states, and permissions require inspected evidence.
  • Task-specific work requires current evidence for workspace, organization, channel, and thread scope, message content, timestamp, author, and edit state, membership, roles, and permissions, apps, scopes, tokens, workflows, and integrations, retention, legal hold, export, and administrator policy, notification and communication approvals, and audit and source-of-record evidence.
  • Do not infer workspace state, channel membership, message content, permissions, app scopes, retention, export availability, approval.

Safety notes

  • Minimize personal, customer, employee, financial, credential, and other sensitive data.
  • Require explicit confirmation before sending or editing messages, inviting users, changing channels, permissions, retention, apps, workflows, tokens, or exports.
  • Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.

Download Review source Agent guidance Star on GitHub