slack-intelligence

name	slack-intelligence
description	Use when the founder wants to configure Slack channels, extract actionable Slack intelligence, create a daily Slack digest, review Slack decisions and handoffs, or turn selected Slack context into task candidates for the daily operating workflow.
user-invocable	true

Slack Intelligence — Selected Channel Operating Digest

Purpose

Make Slack useful inside the founder operating system without turning it into a noisy transcript dump.

The skill should read only the Slack channels, threads, exports, or pasted snippets the founder chooses. It extracts operational intelligence that should affect the day: decisions, asks, customer/account mentions, blockers, handoffs, risks, product feedback, competitor mentions, useful links, and task candidates.

Setup

Use /slack-setup when Slack is first connected or when the founder wants to change which channels matter.

Capture:

• Slack connector status: connected / export-only / not connected
• selected channels to review
• channels to ignore
• what each channel is for
• review cadence
• priority keywords, accounts, competitors, products, and people
• escalation rules for urgent asks or customer risk
• posting boundary: no Slack posting without explicit approval

Write:

• data/slack/channel-map.md
• update Slack fields in data/setup-status.md
• append one line to data/ops.log

Required Paths

Read:

• data/setup-status.md
• data/connectors.md
• data/slack/channel-map.md
• data/tasks.md
• views/daily-briefing.md
• views/priority-plan.md
• data/ops.log

Write:

• data/slack/channel-map.md
• views/slack-digest.md
• data/slack/digests/{{DATE}}.md
• data/setup-status.md during setup
• append one line to data/ops.log

Tool Requirements

• Slack connector is preferred for selected channel reads.
• If the Slack connector is unavailable, use pasted threads or selected channel exports.
• Read only selected channels/sources from data/slack/channel-map.md.
• Posting to Slack requires explicit approval.
• Do not use private DMs or broad workspace history unless explicitly included.

Daily Digest

Use /slack-digest daily, or let the morning briefing include it when Slack is configured.

Read:

• data/slack/channel-map.md
• accessible Slack channel messages since the last digest, if a Slack connector is available
• pasted Slack threads or exported snippets if no connector is available
• data/tasks.md
• views/daily-briefing.md
• views/priority-plan.md
• recent data/ops.log

Extract:

• decisions made
• direct asks of the founder or team
• task candidates
• blockers and risks
• customer, prospect, account, or partner mentions
• competitor or market mentions
• product feedback or repeated complaints
• useful files or links to review
• threads that need a response

Write:

• views/slack-digest.md
• data/slack/digests/{{DATE}}.md
• append one line to data/ops.log

Output Standard

Keep the digest short enough to use in a morning briefing. Do not summarize every message.

Every item should answer:

• what happened
• why it matters
• who owns the next step, if known
• whether it should become a task
• source channel or thread reference

Boundaries

• Do not post to Slack without explicit approval.
• Do not read private channels, DMs, or broad history unless the founder explicitly includes them.
• Do not store raw Slack transcripts unless the user asks.
• Do not silently add tasks from Slack; list task candidates and ask before mutating data/tasks.md.
• Do not create hidden passive memory or full Slack indexes.
• Prefer selected-channel intelligence over broad workspace surveillance.