How do I install the Slack Channel Summarizer skill?

Run npx skillmds@latest add nvidia/slack-channel-summarizer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Slack Channel Summarizer skill do?

Read and summarize Slack channel history from inside the NemoClaw sandbox. It is listed under Research & Search on SkillMD.

Is Slack Channel Summarizer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slack Channel Summarizer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slack Channel Summarizer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Slack Channel Summarizer?

NVIDIA (@nvidia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slack Channel Summarizer by nvidia — Agent Skill

Name: Slack Channel Summarizer
Author: NVIDIA

File contents

slack-channel-summarizer

Use this skill to resolve a Slack channel and read its history.

When to use

Summarize recent activity in a channel
Review conversation history for a time range
Check what was discussed in a channel before answering a question

Instructions

The best way to access slack given the sandbox is through the provided python scripts.
Direct curl requests, or Python scripts, are unlikely to succeed
The SLACK_BOT_TOKEN contains a placeholder env var that is resolved by the sandbox on egress
Only refer to helper scripts that actually exist in this sandbox image

Procedure

1. Resolve the channel ID

If the user gives a direct Slack mention like <#C0ALN454EH4>, use that ID directly.

If the request comes from a tagged Slack channel and the runtime context already gives you the current channel ID, treat that as the resolved channel ID for phrases like "this channel".

Otherwise, use your slack channel finder skill.

2. Read channel history

Use the existing channel-description helper with the resolved channel ID. It includes recent human messages and channel metadata that are sufficient for a summary:

/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/describe_slack_channel.py \
  --channel-id CHANNEL_ID --history-limit 15

Useful variants:

/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/describe_slack_channel.py \
  --channel-id CHANNEL_ID --history-limit 30 --replies

/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/describe_slack_channel.py \
  --channel-id CHANNEL_ID --history-limit 15 --resolve-users

Interpret common failures explicitly:

not_in_channel The bot is not a member of that channel.
missing_scope with needed=channels:history The bot cannot read public-channel history.
missing_scope with needed=groups:history The bot cannot read private-channel history.
channel_not_found The ID is wrong or unavailable to the token.

3. Summarize

Summarize only what the user asked for. Good defaults are:

time range covered
main topics
active participants
decisions or action items

---name: slack-channel-summarizerdescription: Read and summarize Slack channel history from inside the NemoClaw sandbox.---# slack-channel-summarizerUse this skill to resolve a Slack channel and read its history.## When to use- Summarize recent activity in a channel- Review conversation history for a time range- Check what was discussed in a channel before answering a question## Instructions- The best way to access slack given the sandbox is through the provided python scripts.- Direct curl requests, or Python scripts, are unlikely to succeed- The SLACK_BOT_TOKEN contains a placeholder env var that is resolved by the sandbox on egress- Only refer to helper scripts that actually exist in this sandbox image## Procedure### 1. Resolve the channel IDIf the user gives a direct Slack mention like `<#C0ALN454EH4>`, use that IDdirectly.If the request comes from a tagged Slack channel and the runtime context alreadygives you the current channel ID, treat that as the resolved channel ID forphrases like "this channel".Otherwise, use your slack channel finder skill.### 2. Read channel historyUse the existing channel-description helper with the resolved channel ID. Itincludes recent human messages and channel metadata that are sufficient for asummary:```bash/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/describe_slack_channel.py \ --channel-id CHANNEL_ID --history-limit 15```Useful variants:```bash/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/describe_slack_channel.py \ --channel-id CHANNEL_ID --history-limit 30 --replies``````bash/usr/bin/python3 /sandbox/.hermes-data/skills/slack-channel-finder/scripts/describe_slack_channel.py \ --channel-id CHANNEL_ID --history-limit 15 --resolve-users```Interpret common failures explicitly:- `not_in_channel` The bot is not a member of that channel.- `missing_scope` with `needed=channels:history` The bot cannot read public-channel history.- `missing_scope` with `needed=groups:history` The bot cannot read private-channel history.- `channel_not_found` The ID is wrong or unavailable to the token.### 3. SummarizeSummarize only what the user asked for. Good defaults are:- time range covered- main topics- active participants- decisions or action items

Frequently asked questions

Slack Channel Summarizer