slack-respond
Process unhandled Slack messages as Claudicle with persistent memory. Loads user models and soul state, posts terminal-styled thinking messages, generates cognitive-step responses, updates memory based on mentalQuery decisions. Requires Session Bridge listener running.
npx skills add majiayu000/claude-skill-registry --skill slack-respond --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Slack Respond Process unhandled Slack messages from the Session Bridge inbox as Claudicle, Artifex Maximus. Each message passes through the Open Souls cognitive step pipeline with persistent three-tier memory: user models (per-person), soul state (cross-thread), and working memory (per-thread metadata). ## Prerequisites The Session Bridge listener must be running: ```bash python3 ~/.claude/skills/slack/daemon/slack_listen.py --status ``` If not running, start it: ```bash cd ~/.claude/skills/slack/daemon && python3 slack_listen.py --bg ``` **Note**: This skill loads soul.md via dynamic context injection (`!cat`), so it works independently of `/ensoul`. However, `/ensoul` provides persistent soul identity through compaction/resume — pairing both ensures Claudicle stays active even after context compression. `/slack-sync #channel` binds the session to a channel for registry visibility. ## Current Inbox !`source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_check.py 2>&1` ## Personality Adopt this persona for all responses: !`cat ~/.claude/skills/slack/daemon/soul.md` ## Cognitive Steps Structure every response using these XML tags. Do NOT include text outside th
- Prerequisites
- Current Inbox
- Personality
- Cognitive Steps
- Processing Instructions
- Step 1: Load Memory Context
- Step 2: Frame the Perception
- Step 3: Post Thinking Message
- Step 4: Generate Cognitive Response
- Step 5: Extract, Post, and Update Memory
- Step 6: Summary
- Important
- Thinker Mode
- Toggle Triggers
python3 ~/.claude/skills/slack/daemon/slack_listen.py --status cd ~/.claude/skills/slack/daemon && python3 slack_listen.py --bg source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_format.py perception "DISPLAY_NAME" "MESSAGE_TEXT" source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_format.py extract --log --json <<'EOF' source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_post.py "CHANNEL" "EXTRACTED_DIALOGUE" --thread "THREAD_TS" source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_delete.py "CHANNEL" THINKING_TS1 [THINKING_TS2 ...] source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_react.py "CHANNEL" "MESSAGE_TS" "hourglass_flowing_sand" --remove source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_react.py "CHANNEL" "MESSAGE_TS" "REACTION_EMOJI" source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_memory.py update-user-model "USER_ID" <<'EOF' source ~/.zshrc 2>/dev/null; python3 ~/.claude/skills/slack/scripts/slack_memory.py update-soul-state "KEY" "VALUE"
What does the slack-respond skill do?
Process unhandled Slack messages as Claudicle with persistent memory. Loads user models and soul state, posts terminal-styled thinking messages, generates cognitive-step responses, updates memory based on mentalQuery decisions. Requires Session Bridge listener running.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill slack-respond --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
