Skip to main content

Remote skill

Remote From Slack Skill

Connect the current agent session to an available Slack channel bridge.

On this page

Install command

AI DevKit installs its built-in skills as one curated set. Run this once to install remote-from-slack with the rest of the built-in workflow skills.

bash
npx ai-devkit@latest skill add --built-in

What it does

Use remote-from-slack when you want to control or chat with the current session from Slack. It checks AI DevKit readiness, selects an available Slack channel, starts the bridge in daemon mode, and avoids stopping existing bridges without confirmation.

When to use it

  • Bridge the current agent session to Slack
  • Reuse an existing configured Slack channel
  • Start a background channel bridge with a clear stop command

Supported agents

  • Claude Code
  • Codex
  • opencode
  • Pi

The SKILL.md file

This is what your agent reads when the skill runs. View it on GitHub (opens in a new tab)

Use this skill when the user wants to control or chat with the current session from Slack.

Prefer the installed ai-devkit binary; if unavailable, use npx ai-devkit@latest. Run AI DevKit commands outside filesystem sandboxes because they inspect host-level agent and channel state.

Workflow#

  1. Check readiness:

    bash
    ai-devkit status --json

    If AI DevKit is not ready, use ai-devkit-setup skill first. Stop if setup leaves manual actions.

  2. Inspect channels and agents:

    bash
    ai-devkit channel list
ai-devkit agent list --json

  3. Identify the current agent by matching this session to an agent list --json entry. If unclear, ask for the agent name.

  4. Find configured Slack channels. If none exist, tell the user to run:

    bash
    ai-devkit channel connect slack

    Stop after giving that action.

  5. Choose a channel. Use the requested channel or the only available Slack channel. If multiple Slack channels are available, ask the user which one to use. Available means Slack, enabled, credentials present, and not already running.

  6. If no Slack channel is available because bridges are already running, ask before stopping one. After confirmation:

    bash
    ai-devkit channel stop <channel>

  7. Start the bridge in the background:

    bash
    ai-devkit channel start <channel> --agent <agent-name> --daemon

  8. Report the connected channel, agent name, and how to stop it: ai-devkit channel stop <channel>.

Boundaries#

  • Do not create or connect a Slack channel for the user; only point them to channel connect.
  • Do not stop a running bridge without explicit confirmation.
  • Do not guess when both agent or channel selection are ambiguous.
esc