Slacrawl
Slack archive: search, sync freshness, threads/DMs, SQL counts, and Slacrawl repo work.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Slacrawl when an AI agent needs a reusable SKILL.md workflow for this job: Slack archive: search, sync freshness, threads/DMs, SQL counts, and Slacrawl repo work.
When not to use it
Skip Slacrawl when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/slacrawl # Save SKILL.md to ~/.claude/skills/slacrawl/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/slacrawl/SKILL.md. For a shared project, commit the folder at .claude/skills/slacrawl/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Slacrawl skill for this task: Use Slacrawl when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
67/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 68/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Slacrawl
Use local Slack archive data first. Check freshness for recent/current questions:
```bash slacrawl doctor slacrawl status --json ```
Refresh only when stale or asked:
```bash slacrawl sync --source wiretap slacrawl sync --source bot --latest-only ```
`wiretap` reads Slack Desktop cache; `bot` uses API tokens. The `desktop`/`api` aliases remain valid. A configured connector can use `--source mcp`; select the workspace explicitly when needed. Use `--full` only for deliberate backfills.
Query with bounded slices:
```bash slacrawl search --limit 20 "query" slacrawl messages --since 7d --limit 50 slacrawl sql "select count(*) from messages;" ```
Report workspace/channel names, absolute date spans, counts, and token/source limits. Use read-only SQL for exact counts/rankings. API sync and full thread/DM hydration require Slack tokens; do not assume they exist.
Intended uses
- Use Slacrawl when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.