mcpField
C
claude-code-in-slack

claude-code-in-slack

github.com/dearestAgent workflows045 installsUpdated 30w ago
Repository

About claude-code-in-slack

A skill for managing the Claude Code in Slack client daemon, with commands for setup, start, stop, status, and logs. It checks configuration before operations and prevents starting the daemon without a valid config.

Key features

  1. 01Run the setup wizard
  2. 02Start or stop the daemon
  3. 03Check daemon status
  4. 04View a chosen number of log lines
  5. 05Mask tokens in output

Use cases

  1. 01Configure the Slack client for the first time
  2. 02Connect or disconnect the background daemon
  3. 03Troubleshoot daemon operation
  4. 04Inspect recent daemon logs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dearest/claude-code-in-slack --skill claude-code-in-slack

After installing, type/claude-code-in-slackin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
references/
setup.md
scripts/
setup.sh
daemon.sh
daemon-bundle.js

Details

From the project README

Claude Code in Slack — Client Skill

You are managing the Claude Code in Slack client daemon. User data and config are stored at ~/.claude-code-in-slack/.

First, locate the skill directory by finding this SKILL.md file:

  • Use Glob with pattern **/skills/**/claude-code-in-slack/SKILL.md to find its path, then derive the skill root directory from it.
  • Store that path mentally as SKILL_DIR for all subsequent file references.

Command parsing

Parse the user's intent from $ARGUMENTS into one of these subcommands:

User says (examples)Subcommand
setup, configure, initsetup
start, start daemon, connectstart
stop, stop daemon, disconnectstop
status, daemon statusstatus
logs, logs 100, show logslogs

Extract optional numeric argument for logs (default 50).

Config check (applies to start, stop, status, logs)

Before running any subcommand other than setup, check if ~/.claude-code-in-slack/config.env exists:

  • If it does NOT exist:
    • In Claude Code: tell the user "No configuration found" and automatically start the setup wizard using AskUserQuestion.
    • In other environments: tell the user "No configuration found. Please run /claude-code-in-slack setup first." and stop.
  • If it exists: proceed with the requested subcommand.

Subcommands

setup

Read the setup guide from SKILL_DIR/references/setup.md and follow its instructions exactly.

start

Pre-check: Verify ~/.claude-code-in-slack/config.env exists (see "Config check" above). Do NOT proceed without it.

Run: bash "SKILL_DIR/scripts/daemon.sh" start

Show the output to the user. If it fails, tell the user:

  • Check recent logs: /claude-code-in-slack logs
  • Re-run setup if config is invalid: /claude-code-in-slack setup
stop

Run: bash "SKILL_DIR/scripts/daemon.sh" stop

Show the output to the user.

status

Run: bash "SKILL_DIR/scripts/daemon.sh" status

Show the output to the user.

logs

Extract optional line count N from arguments (default 50). Run: bash "SKILL_DIR/scripts/daemon.sh" logs N

Notes

  • Always mask the TOKEN value in output (show only first 4 and last 4 characters if you must display it)
  • Never start the daemon without a valid config.env — always check first, redirect to setup
  • The daemon runs as a background process (node or bun); its PID is stored at ~/.claude-code-in-slack/runtime/daemon.pid
  • Logs are at ~/.claude-code-in-slack/logs/daemon.log
  • Config persists at ~/.claude-code-in-slack/config.env — survives across sessions

Comments

Markdown supported