Interact with Slack workspaces for channel management, message reading, and content analysis. All operations are read-only unless creating channels.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionslack-automationExecute the skills CLI command in your project's root directory to begin installation:
Fetches slack-automation from casper-studios/casper-marketplace 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-automation. Access via /slack-automation 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
10
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10
stars
Interact with Slack workspaces for channel management, message reading, and content analysis. All operations are read-only unless creating channels.
What do you need?
│
├── Search for channels by name
│ └── references/search.md
│ └── Script: scripts/slack_search.py search
│
├── Read messages from a channel
│ └── references/fetch-news.md
│ └── Script: scripts/fetch_slack_news.py
│
├── Create a new channel
│ └── references/create-channel.md
│ └── Script: scripts/create_slack_channel.py
│
└── Categorize/analyze messages
└── references/categorize.md
└── Script: scripts/categorize_slack_messages.py
# Required in .env
SLACK_BOT_TOKEN=xoxb-your-bot-token
| Scope | Purpose |
|---|---|
channels:read |
List public channels |
channels:history |
Read public channel messages |
groups:read |
List private channels |
groups:history |
Read private channel messages |
channels:manage |
Create channels |
python scripts/slack_search.py search "internal" --limit 10
python scripts/slack_search.py read "internal-client" --days 7
python scripts/create_slack_channel.py "project-alpha" --private
For client channels: internal-{client-name}
internal-microsoft, internal-acme-corpFree - Slack API has no per-request cost. Rate limited to ~50 requests/minute.
SLACK_BOT_TOKEN in .env file (never commit to git)xoxb- - never expose in logs or outputchannels:read - List public channels (read-only)channels:history - Read public channel messages (read-only)groups:read - List private channels bot is in (read-only)groups:history - Read private channel messages (read-only)channels:manage - Create channels (write access)Symptoms: "channel_not_found" error when reading or posting Cause: Invalid channel ID, bot not in channel, or private channel Solution:
slack_search.py search)/invite @botname)Symptoms: "missing_scope" or "not_allowed_token_type" error Cause: Bot token missing required OAuth scopes Solution:
channels:read, channels:history, etc.xoxb-)Symptoms: "invalid_auth" or "token_revoked" error Cause: OAuth token expired, revoked, or incorrectly configured Solution:
.env for correct SLACK_BOT_TOKEN valueSymptoms: "ratelimited" error or 429 status code Cause: Too many API requests in short period Solution:
Symptoms: Can't read private channel despite having scopes Cause: Bot not added to the private channel Solution:
/invite @botnamegroups:read and groups:history scopes are addedSkills: slack-automation → content-generation Use case: Summarize internal news for weekly newsletter Flow:
Skills: slack-automation → transcript-search Use case: Find related meetings when researching Slack discussions Flow:
Skills: slack-automation → google-workspace Use case: Archive categorized Slack summaries to Google Drive Flow:
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
Solid pick for teams standardizing on skills: slack-automation is focused, and the summary matches what you get after install.
We added slack-automation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
slack-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
slack-automation has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: slack-automation is focused, and the summary matches what you get after install.
slack-automation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
slack-automation has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in slack-automation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added slack-automation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
slack-automation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 30