agentleFS
Sign inStart free
pierreraiipierreraii/claude-slack-bridge/skills/configure/SKILL.md

configure

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Set up the Slack channel — save the bot and app tokens and review access policy. Use when the user pastes Slack tokens, asks to configure Slack, asks "how do I set this up" or "who can reach me," or wants to check channel status.

  • Reads credentials

43 other projects use a version of this, 13 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use calendar, setup and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 7 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read both state files and give the user a complete picture:

    line 26
  2. Distinctive:

    No tokens → show the Slack App setup guide below

    line 35
  3. Very specific:

    Read existing .env, update/add both lines, preserve other keys.

    line 48
  4. Distinctive:

    Delete both token lines (or the file if that's all it contains).

    line 55

“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/slack-bridge:configure — Slack Channel Setup

Writes the bot and app tokens to ~/.claude/channels/slack/.env and orients the user on access policy. The server reads this file at boot.

Arguments passed: $ARGUMENTS

Dispatch on arguments

No args — status and guidance

Read both state files and give the user a complete picture:

  1. Tokens — check ~/.claude/channels/slack/.env for SLACK_BOT_TOKEN and SLACK_APP_TOKEN. Show set/not-set; if set, show first 10 chars masked.
  2. Access — read ~/.claude/channels/slack/access.json (missing = defaults). Show: dmPolicy, allowed senders count and list, pending pairings.
  3. What next — concrete next step:
    • No tokens → show the Slack App setup guide below
    • Tokens set, nobody allowed → "DM your bot on Slack. Approve with /slack-bridge:access pair <code>."
    • Tokens set, someone allowed → "Ready. DM your bot to reach the assistant."

Push toward lockdown. Once the allowlist is set, offer to flip to allowlist policy.

<bot-token> <app-token> — save tokens

  1. Split $ARGUMENTS — first is SLACK_BOT_TOKEN, second is SLACK_APP_TOKEN.
  2. Warn if prefixes don't match xoxb- / xapp-.
  3. mkdir -p ~/.claude/channels/slack
  4. Read existing .env, update/add both lines, preserve other keys. Write back.
  5. chmod 600 ~/.claude/channels/slack/.env
  6. Show no-args status after saving.
  7. Note: restart required for token changes (/reload-plugins).

clear — remove tokens

Delete both token lines (or the file if that's all it contains).

Slack App Setup Guide

Show this when tokens are not set:

To create a Slack bot:

1. Go to https://api.slack.com/apps → "Create New App" → "From scratch"

2. Left sidebar → "Socket Mode" → Enable Socket Mode
   Generate an App-Level Token with scope: connections:write
   Copy it — this is your SLACK_APP_TOKEN (starts with xapp-)

3. Left sidebar → "OAuth & Permissions" → "Bot Token Scopes" → Add:
     chat:write, reactions:write, im:history, im:write,
     channels:history, groups:history, files:read, files:write, users:read

4. Left sidebar → "Event Subscriptions" → Enable Events → Subscribe to:
     message.im, message.channels, message.groups, app_mention

5. Left sidebar → "Install App" → "Install to Workspace" → Allow
   Copy the Bot User OAuth Token — this is your SLACK_BOT_TOKEN (starts with xoxb-)

6. Run: /slack-bridge:configure xoxb-... xapp-...

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free