How do I install the Org Slack Dm skill?

Run npx skillmds@latest add pooriaarab/org-slack-dm 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.

Is Org Slack Dm 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 Org Slack Dm?

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 Org Slack Dm free to use?

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

Who published Org Slack Dm?

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

Org Slack Dm by pooriaarab — Agent Skill

Name: Org Slack Dm
Author: pooriaarab

Org Slack Dm

Use when the user wants to organize Slack DMs and saved items — archiving stale DM threads, processing the Saved Items queue, identifying conversations to convert into reference notes, and reducing notification clutter. Triggers: 'clean up Slack', 'process my Slack saved items'.

pooriaarab 0c46482 2.6 KB Updated Sep 17, 2026

File contents

Slack DM Organizer

Triage Slack DMs and the Saved Items queue.

Requirements

Slack workspace with admin or user-level token (xoxp-...) — see Slack API docs.
slackclaw CLI — pooriaarab/slackclaw (scaffold; needs implementation). Goal: parallel to steipete's discrawl (Discord) but for Slack — local SQLite archive of DMs and saved items, claw-able for agents.
Per-workspace scope (Slack tokens are per-workspace, not global).
Until slackclaw is built: use the Slack Web API directly (conversations.list, conversations.history, etc.) with a user-token from https://api.slack.com/apps.

Step 1 — Ask the User First

1. Workspaces in scope — pick which to touch (likely one at a time).
2. Saved Items strategy — convert to Notes / Notion reference, archive, or just review and clear?
3. Stale DM threads — archive after N days of inactivity?
4. Notification preferences — also re-tune notification settings per channel?
5. Bot DMs — separate treatment for bot-driven DMs (deploys, alerts, integrations)?

Steps (TBD)

Inventory — list DMs (1:1 + multi-person), list saved items, list active channels with notification noise.
Classify — DMs by recency, saved items by category (reference / actionable / stale).
Plan — proposed archive list + saved-items export plan.
Approve — batch.
Apply — conversations.archive, save-items processing, notification tuning.
Verify — final state + saved items count.

Surface-specific notes

Slack DMs aren't "deletable" by users — only archivable from view (still searchable).
Saved Items is a personal queue; processing it = converting to Notes/Notion or unsaving.
Per-workspace token: get from https://api.slack.com/apps. Required scopes: users.profile:read, conversations.read, conversations.history, conversations.write, bookmarks.read.
Free workspaces have message-history retention limits — plan around that.

---name: org-slack-dmdescription: Use when the user wants to organize Slack DMs and saved items — archiving stale DM threads, processing the Saved Items queue, identifying conversations to convert into reference notes, and reducing notification clutter. Triggers: 'clean up Slack', 'process my Slack saved items'.---# Slack DM OrganizerTriage Slack DMs and the Saved Items queue.## Requirements- Slack workspace with admin or user-level token (`xoxp-...`) — see Slack API docs.- **`slackclaw` CLI** — [pooriaarab/slackclaw](https://github.com/pooriaarab/slackclaw) (scaffold; needs implementation). Goal: parallel to steipete's `discrawl` (Discord) but for Slack — local SQLite archive of DMs and saved items, claw-able for agents.- Per-workspace scope (Slack tokens are per-workspace, not global).- Until `slackclaw` is built: use the Slack Web API directly (`conversations.list`, `conversations.history`, etc.) with a user-token from https://api.slack.com/apps.## Step 1 — Ask the User First```1. Workspaces in scope — pick which to touch (likely one at a time).2. Saved Items strategy — convert to Notes / Notion reference, archive, or just review and clear?3. Stale DM threads — archive after N days of inactivity?4. Notification preferences — also re-tune notification settings per channel?5. Bot DMs — separate treatment for bot-driven DMs (deploys, alerts, integrations)?```## Steps (TBD)1. **Inventory** — list DMs (1:1 + multi-person), list saved items, list active channels with notification noise.2. **Classify** — DMs by recency, saved items by category (reference / actionable / stale).3. **Plan** — proposed archive list + saved-items export plan.4. **Approve** — batch.5. **Apply** — `conversations.archive`, save-items processing, notification tuning.6. **Verify** — final state + saved items count.## Surface-specific notes- Slack DMs aren't "deletable" by users — only archivable from view (still searchable).- Saved Items is a personal queue; processing it = converting to Notes/Notion or unsaving.- Per-workspace token: get from https://api.slack.com/apps. Required scopes: `users.profile:read`, `conversations.read`, `conversations.history`, `conversations.write`, `bookmarks.read`.- Free workspaces have message-history retention limits — plan around that.## See also- [`../org-life-organizer/_lib/taxonomy.md`](../org-life-organizer/_lib/taxonomy.md)- [`../org-life-organizer/_lib/patterns.md`](../org-life-organizer/_lib/patterns.md)- [`../notion-organizer/SKILL.md`](../notion-organizer/SKILL.md) — destination for saved items worth keeping

Frequently asked questions