slack-api

A guide and command-line workflow for discovering and calling Slack Web API methods. These methods are named operations such as sending a message or reading channel history, and each has required permissions and inputs.

In plain words
What is it for?
Use it to look up an API method, verify its contract and permissions, call it, process paginated results, and handle throttling.
Why use it?
It helps developers choose the correct method, check access requirements, handle pagination, and respond properly to API errors and rate limits.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/slackapi/slack-skills-plugin/slack-api
Any agent
npx skills add slackapi/slack-skills-plugin --skill slack-api
Clone the repo
git clone --depth 1 https://github.com/slackapi/slack-skills-plugin

Made for: Claude Code, Codex.

Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,256 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00109 $0.03256
Opus 5 $0.00055 $0.01628
Sonnet 5 $0.00022 $0.00651
Haiku 4.5 $0.00011 $0.00326

Measured 2d ago against content hash 341eb0389a7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slack-api scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

You do not need the CLI to call a method. Get a token of the type you determined above from the app's **OAuth & Permissions** page in the Slack app config (`https://api.slack.com/apps` → your app → **OAuth & Permissions*
skills/slack-api/SKILL.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slack Web API

Help the developer discover the right Web API method, read its contract, and call it correctly. Slack exposes hundreds of methods named in family.method dot notation (e.g. chat.postMessage, conversations.history) at https://slack.com/api/<method>. Every method's doc page follows a fixed URL pattern, so the contract for any method is always one fetch away.

If $0 is provided, it is either a full method.name (jump to Step 2 to read its contract) or a family name (go to Step 1 and find it in the index).

Critical rules:

  • Verify a method name and its required scopes against its doc page before calling it — never invent method names or guess scopes. Method names use family.method dot notation.
  • Every response has a top-level ok boolean. Always check ok before using the result; on ok: false, read the error string.
  • Method names, scopes, rate tiers, and arguments come from the live doc page (https://docs.slack.dev/reference/methods/<method-lowercased>.md). The docs are the source of truth — discover from the live index, read the contract from the method's own page.

DO NOT rules:

  • DO NOT assume a method is GET — many are POST. Check the doc page.
  • DO NOT hardcode bearer tokens into committed code or share them in plain text.
  • DO NOT use deprecated methods (files.upload, dialog.open, rtm.*, oauth.access, search.*, stars.*, reminders.*) without checking the replacement — a deprecated method's own doc page names what supersedes it; prefer the replacement for new apps.
  • DO NOT paginate by incrementing a page number — Slack uses opaque cursors (see Step 5).

Execution posture — run reads, confirm writes:

  • Read-only methods (*.list, *.info, *.history, conversations.members, auth.test, etc.) may be run directly to help the developer.
  • State-changing or destructive methods (chat.postMessage/update/delete, any *.delete/*.remove/*.kick/*.archive, and all admin.*) — prepare the exact command and confirm with the developer before running it.

Read the full file on GitHub · 208 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 208 lines · 109 tokens per session scan A 341eb0389a7f

Subscribe to this mod's changes

slack-api is a skill published in the GitHub repository slackapi/slack-skills-plugin (113 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 3,256 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

test-driven-development

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

addyosmani/agent-skills · 50 tokens

ci-cd-and-automation

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

addyosmani/agent-skills · 45 tokens

documentation-and-adrs

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

addyosmani/agent-skills · 43 tokens

idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…

addyosmani/agent-skills · 75 tokens

source-driven-development

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

addyosmani/agent-skills · 40 tokens

chinese-documentation

中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用,不要根据上下文自动触发。.

jnMetaCode/superpowers-zh · 62 tokens