Menu
Best practices for extracting signal from Slack channel history — decisions, action items, blockers, and FYIs — and formatting them into structured reports.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Complete guide to all Gmail tools — inbox management, search, sending, drafts, and attachments.
Understand the @matimo/composio governance wrapper — how composio_* tools proxy Composio's 250+ integrations, what risk levels mean for approval, and how to handle missing connected accounts.
Complete guide to all Microsoft Graph tools — search, OneDrive/SharePoint files, Outlook mail, Teams, calendar, and SharePoint publishing.
Generates a smart daily briefing by analyzing Gmail and Google Calendar.
Complete guide for DBA agents managing PostgreSQL databases — query execution, performance tuning, connection monitoring, index health, and VACUUM management. USE THIS SKILL whenever the user asks to inspect, diagnose, optimize, or manage a PostgreSQL database. Triggers include: 'show me slow queries', 'check table bloat', 'what connections are active', 'find unused indexes', 'why is my DB slow', 'run this SQL', or any Postgres health/diagnostic task.
A test skill to verify skill creation works
| name | slack-intelligence |
| description | Best practices for extracting signal from Slack channel history — decisions, action items, blockers, and FYIs — and formatting them into structured reports. |
Extract meaningful signal from raw Slack message history and produce structured, actionable reports.
Messages indicating something is stuck, broken, or preventing progress. Signals: "blocked", "can't", "waiting on", "broken", "issue", "problem", "stuck", "need help", "urgent"
Messages where a conclusion, agreement, or direction was settled. Signals: "we decided", "going with", "confirmed", "agreed", "approved", "final", "will do", "let's go with"
Messages assigning tasks or committing to next steps. Signals: "@mention + verb", "will", "I'll", "you should", "please", "need to", "by [date/time]", "take care of"
Informational messages with no required action. Signals: "FYI", "heads up", "just so you know", "for your awareness", "update:", "reminder"
## 📊 Channel Intelligence Report
**Channel:** #channel-name
**Period:** Last N hours
**Messages Analyzed:** X
---
### 🔴 Blockers (N)
- [URGENT?] @user: <summary> — <timestamp>
### ✅ Decisions Made (N)
- <decision summary> — agreed by @user1, @user2
### 📋 Action Items (N)
- [ ] @assignee: <task> — due <deadline or "unspecified">
### 📢 FYIs (N)
- <summary> — from @user
---
**Signal Score:** X/10 (ratio of meaningful to total messages)