slack-channel-finder
Skill142 starsChanged 3 months agoApache-2.0View on GitHub
Discover Slack channels by topic, team, or domain and determine the channel ID.
In this repository62 other files it gives its agents.
- examples/recipes/partners/hpe/retail-assistant/docker-compose/scripts/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/hpe/retail-assistant/helm/files/identity/AGENTS.mdAGENTS.md
- examples/recipes/partners/tavily/watchtower/prompts/AGENTS.mdAGENTS.md
- nemoclaw-community-contributor-examplesSkill
- nemoclaw-community-maintainer-policiesSkill
- coach-nemoclaw-hermesSkill
- coordinate-nemoclaw-blenderSkill
- blender-host-sandbox-boundarySkill
- blender-python-api-verificationSkill
- ovphysx-host-runtime-boundarySkill
- axe-a11ySkill
- deep-researchSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- module-1Skill
- module-2Skill
- module-3Skill
- module-4Skill
- module-5Skill
- module-6Skill
- module-7Skill
- setup-workshop-nemoclaw-operatorSkill
- setup-workshop-nemoclawSkill
- workshopSkill
- cross-source-gap-analysisSkill
- github-readonly-liveSkill
- gitlab-readonly-liveSkill
- nemoclaw-autohealSkill
- nemoclaw-nvteamSkill
- outlook-email-searchSkill
- public-web-searchSkill
- slack-channel-finderSkill
- slack-channel-summarizerSkill
- source-etl-querySkill
- kubernetes-sreSkill
- openshift-llm-deploySkill
- inbound-judgingSkill
- memory-consolidationSkill
- memory-repairSkill
- memory-writingSkill
- obligation-reviewSkill
- preference-updateSkill
- nv-tech-assistantSkill
- payment-ops-playbookSkill
- payment-screeningSkill
- rail-boundary-testSkill
- release-packetSkill
- pr-reviewSkill
- pr-test-case-assistantSkill
- vss-videoSkill
- nemoclaw-hermes-swarmSkill
- blackwall-payment-gateSkill
- retail-apiSkill
- retail-apiSkill
- watchtowerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to discover Slack channels ID by name or topic
- Distinctive: line 12
Do NOT use this skill when the user has already provided a slack channel ID
- Distinctive: line 17
Avoid writing custom curl or python commands
- Distinctive: line 18
Only customize if the existing scrips fail, and in that case follow their authorization patterns closely
- Distinctive: line 26
Check for scripts at:
- Distinctive: line 49
If the user is asking to summarize or inspect a specific Slack channel, and they likely know the channel already but did not provide the …
- Distinctive: line 52
If the user is asking you to help find which Slack channel is relevant to a topic, team, or project, use the discovery flow below instead …
- Very specific: line 142
When you need to understand a specific channel — what it's for, who's active, what they're discussing — use describe_slack_channel.py:
- Very specific: line 226
When a message has a high reply_count and you need the actual discussion content, use --replies on describe_slack_channel.py or directly …
- Very specific: line 238
If the user's goal goes beyond discovery ("tell me what the X team is working on"), once channels are identified, hand off to …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
slack-channel-finder
Use this skill to discover Slack channels ID by name or topic
When to use
Do NOT use this skill when the user has already provided a slack channel ID
Instructions
- Because of the sandbox, the best path is to use the provided helper scripts
- Avoid writing custom curl or python commands
- Only customize if the existing scrips fail, and in that case follow their authorization patterns closely
- Be aware that slack access is through a Slack bot, whose token might have certain scopes or might be missing scopes
Scripts
Check for scripts at:
/sandbox/.hermes-data/skills/slack-channel-finder/scripts/or at
/sandbox/.hermes/skills/slack-channel-finder/scripts| Script | Purpose |
find_channel.py | Search and rank channels by query across the workspace |
list_accessible_channels.py | List channels (bot-member or workspace-wide) |
describe_slack_channel.py | Deep-describe a single channel with layered signals |
Procedure
1. Distinguish summary requests from discovery requests
- If the user is asking to summarize or inspect a specific Slack channel, and they likely know the channel already but did not provide the exact name or ID, ask them for the channel name.
- If the user is asking you to help find which Slack channel is relevant to a topic, team, or project, use the discovery flow below instead of asking for a channel name first.
2. If you are given a channel name, start with list_accessible_channels.py and try to match channel name to ID
/usr/bin/python3 .../list_accessible_channels.py
3. If you are unclear on what channel the user is talking about, ask them for the channel name
4. If the user wants help finding a channel, attempt to find one based on the user's topic or query
For topic or team queries, use find_channel.py — it searches all discoverable
public channels (not just bot-member channels) and returns scored matches:
/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/find_channel.py \
--query "nemoclaw inference" --top 5Output:
{
"ok": true,
"query": "nemoclaw inference",
"query_tokens": ["nemoclaw", "inference"],
"total_searched": 78,
"count": 2,
"discovery_mode": "workspace",
"results": [
{
"channel_id": "C0ASZUN3L5D",
"name": "lopp-nemoclaw-staging",
"is_member": true,
"num_members": 8,
"topic": "",
"purpose": "This is a channel to discuss NemoClaw technical updates...",
"score": 9,
"match_reasons": ["name:nemoclaw", "purpose:nemoclaw"]
}
]
}Scoring weights: name token match = 3 pts, purpose match = 2 pts, topic match = 1 pt.
The is_member flag tells you whether the bot is in the channel — full history
and thread signals are available only for member channels.
Options:
| Flag | Description |
--query TEXT | Required. Matched against name, topic, purpose. |
--top N | Max results (default 5) |
--member-only | Restrict to bot-member channels only |
--min-score N | Minimum score to include (default 1) |
Information on other scripts
List all channels (when you need the full inventory)
For cases where you need the complete channel list rather than a scored search:
# Bot-member channels only (fast)
/usr/bin/python3 .../list_accessible_channels.py
# All public channels in the workspace
/usr/bin/python3 .../list_accessible_channels.py --all-publicOutput: { "ok": true, "count": N, "channels": [...], "discovery_mode": "workspace" }
Each channel: {id, name, is_archived, is_private, is_member, num_members, topic, purpose, created}
For --all-public, is_member=false channels exist in the workspace but the bot
hasn't been added — you can see name/topic/purpose but NOT read their history.
Options:
| Flag | Description |
--all-public | Use conversations.list for workspace-wide discovery |
--include-archived | Include archived channels |
--types TYPES | Comma-separated types (default public_channel) |
Describe a channel in depth
When you need to understand a specific channel — what it's for, who's active, what
they're discussing — use describe_slack_channel.py:
# Full mode (name + topic + purpose + pins + bookmarks + recent history)
/usr/bin/python3 .../describe_slack_channel.py --channel-id C0ASZUN3L5D
# Fast mode (skips conversations.history — useful for breadth scans)
/usr/bin/python3 .../describe_slack_channel.py --channel-id C0ASZUN3L5D --no-history
# With thread content (expands reply threads for high-activity messages)
/usr/bin/python3 .../describe_slack_channel.py --channel-id C0ASZUN3L5D --replies
# With resolved user display names on top contributors
/usr/bin/python3 .../describe_slack_channel.py --channel-id C0ASZUN3L5D --resolve-usersOptions:
| Flag | Description |
--channel-id ID | Required. Slack channel ID (e.g. C0ASZUN3L5D) |
--history-limit N | Max messages to fetch (default 50) |
--no-history | Skip conversations.history (faster, cheaper) |
--no-pins | Skip pins.list |
--no-bookmarks | Skip bookmarks.list |
--replies | Fetch first few replies for threaded messages (reply_count > 0) |
--replies-limit N | Max replies per thread when --replies is set (default 5) |
--resolve-users | Resolve contributor user IDs to display names via users.info |
Output structure:
{
"ok": true,
"channel_id": "C0ASZUN3L5D",
"name": "lopp-nemoclaw-staging",
"is_archived": false,
"is_private": false,
"num_members": 8,
"signals": {
"name_tokens": ["lopp", "nemoclaw", "staging"],
"topic": "",
"topic_stale": true,
"purpose": "This is a channel to discuss NemoClaw...",
"pinned_messages": [],
"bookmarks": [],
"recent_human_messages": [
{
"user": "UR0A4QL5N",
"text": "<@U0AUN68FSNT> tell me a joke",
"ts": "1777589708.784719",
"thread_ts": "1777589708.784719",
"reply_count": 2,
"thread_messages": [...]
}
],
"top_contributors": [
{"user_id": "U0887Q5UVV4", "message_count": 13, "display_name": "Scott Lopp"}
],
"human_message_count": 22
},
"confidence": "medium"
}The script does NOT produce a natural-language description. Synthesize one from
the signals dict, weighting in this order:
- Pinned messages (often a charter or intro)
- Channel name tokens
- Topic and purpose (if not stale)
- Bookmarks
- Recent human message themes
- Top contributors
The confidence field (high, medium, low) reflects how many independent
signals were available. For low-confidence channels, hedge ("appears to be
about ...") or ask the user to confirm.
Other
Read thread content
When a message has a high reply_count and you need the actual discussion
content, use --replies on describe_slack_channel.py or directly call
conversations.replies:
# Via describe (expands all threads in the sampled history)
/usr/bin/python3 .../describe_slack_channel.py --channel-id [channel-id] --replies --replies-limit [n]Chain into summarization if requested
If the user's goal goes beyond discovery ("tell me what the X team is working
on"), once channels are identified, hand off to slack-channel-summarizer
for each top channel. Cap at 5 channels per query; surface the ranking so the
user can ask for more.
Common patterns
Find channels matching a topic:
/usr/bin/python3 .../find_channel.py --query "nemoclaw deployments"See all public channels in the workspace:
/usr/bin/python3 .../list_accessible_channels.py --all-publicUnderstand a specific channel (fast, no history):
/usr/bin/python3 .../describe_slack_channel.py --channel-id C0ASZUN3L5D --no-historyUnderstand a channel with thread context and user names:
/usr/bin/python3 .../describe_slack_channel.py --channel-id C0ASZUN3L5D --replies --resolve-usersDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

