slack-notifications▌
oimiragieo/agent-studio · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Mode: Cognitive/Prompt-Driven — No standalone utility script; use via agent context.
Mode: Cognitive/Prompt-Driven — No standalone utility script; use via agent context.
Slack Notifications Skill
Overview
This skill provides Slack API operations with progressive disclosure for optimal context usage.
Context Savings: ~90% reduction
- MCP Mode: ~15,000 tokens always loaded (30+ tools)
- Skill Mode: ~500 tokens metadata + on-demand loading
Requirements
- SLACK_BOT_TOKEN environment variable (required)
- SLACK_SIGNING_SECRET environment variable (optional, for event verification)
- SLACK_APP_TOKEN environment variable (optional, for Socket Mode)
Setting up Slack Bot Token
- Create a Slack App at https://api.slack.com/apps
- Navigate to "OAuth & Permissions"
- Add required bot token scopes:
chat:write- Send messageschannels:read- List channelschannels:history- Read channel historyusers:read- List usersfiles:write- Upload filesreactions:write- Add reactions
- Install app to workspace
- Copy "Bot User OAuth Token" to
SLACK_BOT_TOKENenvironment variable
Tools
The skill provides 14 tools across 5 categories:
| Category | Tools | Confirmation Required |
|---|---|---|
| Messaging | post-message, post-thread, update-message, delete-message | Yes (all) |
| Channels | list-channels, get-channel, channel-history | No |
| Users | list-users, get-user, user-presence | No |
| Files | upload-file, list-files | Yes (upload only) |
| Reactions | add-reaction, get-reactions | No |
Quick Reference
# Post message to channel
curl -X POST https://slack.com/api/chat.postMessage \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{"channel": "C1234567890", "text": "Hello from Claude!"}'
# List channels
curl -X GET "https://slack.com/api/conversations.list" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
# Upload file
curl -X POST https://slack.com/api/files.upload \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-F "channels=C1234567890" \
-F "[email protected]" \
-F "title=Weekly Report"
Tool Details
Messaging Tools (Confirmation Required)
post-message
Send a message to a Slack channel.
Parameters:
channel(required): Channel ID or name (e.g., "C1234567890" or "#general")text(required): Message text (supports Slack markdown)thread_ts(optional): Parent message timestamp for threadingblocks(optional): Rich message blocks (JSON array)
Example:
curl -X POST https://slack.com/api/chat.postMessage \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channel": "C1234567890",
"text": "Deployment successful!",
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*Deployment Status*\n:white_check_mark: Production deployed successfully"
}
}
]
}'
post-thread
Reply to a message in a thread.
Parameters:
channel(required): Channel IDthread_ts(required): Parent message timestamptext(required): Reply text
Example:
curl -X POST https://slack.com/api/chat.postMessage \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channel": "C1234567890",
"thread_ts": "1234567890.123456",
"text": "Thread reply here"
}'
update-message
Update an existing message.
Parameters:
channel(required): Channel IDts(required): Message timestamptext(required): New message text
Example:
curl -X POST https://slack.com/api/chat.update \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channel": "C1234567890",
"ts": "1234567890.123456",
"text": "Updated message"
}'
delete-message
Delete a message.
Parameters:
channel(required): Channel IDts(required): Message timestamp
Example:
curl -X POST https://slack.com/api/chat.delete \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channel": "C1234567890",
"ts": "1234567890.123456"
}'
Channel Tools
list-channels
List all channels in workspace.
Parameters:
types(optional): Comma-separated channel types (default: "public_channel")- Options: "public_channel", "private_channel", "mpim", "im"
limit(optional): Max channels to return (default: 100)
Example:
curl -X GET "https://slack.com/api/conversations.list?types=public_channel,private_channel" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
get-channel
Get channel information.
Parameters:
channel(required): Channel ID
Example:
curl -X GET "https://slack.com/api/conversations.info?channel=C1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
channel-history
Get channel message history.
Parameters:
channel(required): Channel IDlimit(optional): Max messages to return (default: 100)oldest(optional): Start of time range (Unix timestamp)latest(optional): End of time range (Unix timestamp)
Example:
curl -X GET "https://slack.com/api/conversations.history?channel=C1234567890&limit=50" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
Security Note: Channel history may contain sensitive information. Use with caution.
User Tools
list-users
List all users in workspace.
Parameters:
limit(optional): Max users to return (default: 100)
Example:
curl -X GET "https://slack.com/api/users.list" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
get-user
Get user profile information.
Parameters:
user(required): User ID
Example:
curl -X GET "https://slack.com/api/users.info?user=U1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
user-presence
Get user online status.
Parameters:
user(required): User ID
Example:
curl -X GET "https://slack.com/api/users.getPresence?user=U1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
File Tools
upload-file (Confirmation Required)
Upload a file to Slack channel.
Parameters:
channels(required): Comma-separated channel IDsfile(required): File path to uploadtitle(optional): File titleinitial_comment(optional): Message text
Example:
curl -X POST https://slack.com/api/files.upload \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-F "channels=C1234567890" \
-F "file=@C:\reports\weekly.pdf" \
-F "title=Weekly Report" \
-F "initial_comment=Here is this week's report"
list-files
List files in channel.
Parameters:
channel(optional): Channel ID to filter byuser(optional): User ID to filter bycount(optional): Max files to return (default: 100)
Example:
curl -X GET "https://slack.com/api/files.list?channel=C1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
Reaction Tools
add-reaction
Add emoji reaction to a message.
Parameters:
channel(required): Channel IDtimestamp(required): Message timestampname(required): Emoji name (without colons, e.g., "thumbsup")
Example:
curl -X POST https://slack.com/api/reactions.add \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channel": "C1234567890",
"timestamp": "1234567890.123456",
"name": "thumbsup"
}'
get-reactions
Get reactions on a message.
Parameters:
channel(required): Channel IDtimestamp(required): Message timestamp
Example:
curl -X GET "https://slack.com/api/reactions.get?channel=C1234567890×tamp=1234567890.123456" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
Agent Integration
Primary Agents
- devops: Infrastructure alerts, deployment notifications, monitoring
- incident-responder: Incident alerts, status updates, escalations
Secondary Agents
- pm: Sprint notifications, milestone updates, team announcements
- developer: Build notifications, PR alerts, test results
- qa: Test failure alerts, quality reports
- security-architect: Security alerts, vulnerability notifications
Common Use Cases
Deployment Notifications
# Notify channel of successful deployment
curl -X POST https://slack.com/api/chat.postMessage \
-H "Authorization: Bearer $SLACK_BOT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"channel": "#deployments",
"text": ":rocket: Production deployment completed",
"blocks": [
{
"type": "section",
"text": {
"type": "mrkdwn",
"text": "*Production Deployment*\n:white_check_mark: v1.2.3 deployed successfully\n*Duration:* 5m 23s"
How to use slack-notifications on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add slack-notifications
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches slack-notifications from GitHub repository oimiragieo/agent-studio and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate slack-notifications. Access the skill through slash commands (e.g., /slack-notifications) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★31 reviews- ★★★★★Shikha Mishra· Dec 12, 2024
slack-notifications fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Michael Johnson· Dec 8, 2024
slack-notifications fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mia Verma· Dec 4, 2024
slack-notifications is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Benjamin Mensah· Nov 27, 2024
Registry listing for slack-notifications matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Neel Srinivasan· Nov 23, 2024
Solid pick for teams standardizing on skills: slack-notifications is focused, and the summary matches what you get after install.
- ★★★★★Rahul Santra· Nov 3, 2024
Registry listing for slack-notifications matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Pratham Ware· Oct 22, 2024
slack-notifications reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Evelyn Rao· Oct 18, 2024
slack-notifications reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Haddad· Oct 14, 2024
slack-notifications has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Isabella Sethi· Jul 19, 2024
Useful defaults in slack-notifications — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 31