Mode: Cognitive/Prompt-Driven — No standalone utility script; use via agent context.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionslack-notificationsExecute the skills CLI command in your project's root directory to begin installation:
Fetches slack-notifications from oimiragieo/agent-studio and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate slack-notifications. Access via /slack-notifications in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23
stars
Mode: Cognitive/Prompt-Driven — No standalone utility script; use via agent context.
This skill provides Slack API operations with progressive disclosure for optimal context usage.
Context Savings: ~90% reduction
chat:write - Send messageschannels:read - List channelschannels:history - Read channel historyusers:read - List usersfiles:write - Upload filesreactions:write - Add reactionsSLACK_BOT_TOKEN environment variableThe 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 |
# 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"
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"
}
}
]
}'
Reply to a message in a thread.
Parameters:
channel (required): Channel IDthread_ts (required): Parent message timestamptext (required): Reply textExample:
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 an existing message.
Parameters:
channel (required): Channel IDts (required): Message timestamptext (required): New message textExample:
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 a message.
Parameters:
channel (required): Channel IDts (required): Message timestampExample:
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"
}'
List all channels in workspace.
Parameters:
types (optional): Comma-separated channel types (default: "public_channel")
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 information.
Parameters:
channel (required): Channel IDExample:
curl -X GET "https://slack.com/api/conversations.info?channel=C1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
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.
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 profile information.
Parameters:
user (required): User IDExample:
curl -X GET "https://slack.com/api/users.info?user=U1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
Get user online status.
Parameters:
user (required): User IDExample:
curl -X GET "https://slack.com/api/users.getPresence?user=U1234567890" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
Upload a file to Slack channel.
Parameters:
channels (required): Comma-separated channel IDsfile (required): File path to uploadtitle (optional): File titleinitial_comment (optional): Message textExample:
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 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"
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 on a message.
Parameters:
channel (required): Channel IDtimestamp (required): Message timestampExample:
curl -X GET "https://slack.com/api/reactions.get?channel=C1234567890×tamp=1234567890.123456" \
-H "Authorization: Bearer $SLACK_BOT_TOKEN"
# 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"
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
slack-notifications fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
slack-notifications fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
slack-notifications is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for slack-notifications matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: slack-notifications is focused, and the summary matches what you get after install.
Registry listing for slack-notifications matched our evaluation — installs cleanly and behaves as described in the markdown.
slack-notifications reduced setup friction for our internal harness; good balance of opinion and flexibility.
slack-notifications reduced setup friction for our internal harness; good balance of opinion and flexibility.
slack-notifications has been reliable in day-to-day use. Documentation quality is above average for community skills.
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