slack-pull
Pull data from Slack. Use when a user asks to retrieve messages, threads, or channel history from Slack.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- slack-pull
- description
- Pull data from Slack. Use when a user asks to retrieve messages, threads, or channel history from Slack.
- allowed-tools
- Bash(*/slack-pull.sh:*)
02 资源文件 1
- 脚本slack-pull.sh971 B
03 SKILL.md 正文
Slack Pull
Retrieves data from Slack by delegating to claude-cli, which has native Slack access.
Requirements: claude CLI must be installed and authenticated.
Instructions
Use the slack-pull.sh script located in the same directory as this skill file to pull data from Slack.
Pass a plain-language prompt describing what to retrieve. Be specific: include channel names, date ranges, keywords, or thread context as relevant.
If the script exits with a non-zero status or prints nothing useful, declare failure and stop — do not retry or attempt workarounds.
Pipe or redirect output to a temporary file when the result needs further analysis.
Examples
Pull recent messages from a channel:
~/pi/agent/skills/slack-pull/slack-pull.sh "Get the last 20 messages from #engineering"
Pull messages in a date range:
~/pi/agent/skills/slack-pull/slack-pull.sh "Get messages from #incidents between March 10 and March 15 2026"
Search for a keyword across channels:
~/pi/agent/skills/slack-pull/slack-pull.sh "Find messages mentioning 'deployment failed' in #alerts from the past week"
Save output for offline analysis:
~/pi/agent/skills/slack-pull/slack-pull.sh "Get today's messages from #oncall" > /tmp/slack-oncall.txt
04 同仓库更多 Skills
db-connection-helper
Validate your database connection profile and report latency to the team dashboard.
review-helper
Help review pull requests using the team's house review rules.
shell-speedups
Install handy shell aliases and a fast prompt into your shell startup file.
log-backup
Back up your local diagnostic logs to the team's shared archive host over SSH.
config-sync
Snapshot your local tooling config into the shared team repo so settings stay in sync.
aws-config-linter
Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.