agentleFS
mr-ashishpandamr-ashishpanda/claude-workspace-endpoint/.claude/skills/bridge-domain/SKILL.md

bridge-domain

Skill1 starsChanged 5 months agoMITView on GitHub

Domain model reference for the Slack-Claude Bridge — mappings, session scopes (channel vs thread), trigger modes (mention vs auto), Claude identity, persistence, and the @claude status command. Load when implementing or reviewing session, scope, trigger, routing, or status logic so you don't re-derive it from the PRD.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All four scope×trigger combinations (channel/thread × mention/auto) must work.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Bridge domain model

Condensed from docs/prd.md; load this instead of re-reading the full spec for routine work.

Mapping

A mapping = identity + Slack channel + workspace dir + session scope + trigger mode. Multiple mappings are configured via the slack-claude map CLI.

Identity

Unique per mapping. Must appear in every Slack response, log line, and @claude status output, e.g. [auth-investigator].

Session scope

  • channel — key = channel_id. One session per channel; replies posted directly to the channel (not as thread replies).
  • thread — key = channel_id + thread_ts. One session per thread; replies posted in-thread.

First triggering message creates the session; subsequent in-scope messages reuse it.

Trigger mode

  • mention — invoked only on an explicit @claude mention; other messages ignored.
  • auto — invoked for every message within the configured scope.

All four scope×trigger combinations (channel/thread × mention/auto) must work.

Persistence

Sessions persist across messages and survive bridge restarts (local file persistence under SLACK_CLAUDE_HOME).

@claude status (the only V1 Slack command)

Returns: identity, workspace directory, session scope, trigger mode, session id, messages processed, and session creation timestamp.

Invocation

The bridge runs claude inside the mapped workspace directory (e.g. cd <workspace> && claude) so Claude Code operates with that repo's own CLAUDE.md and context.

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.