Skill Detail

Bridge coding agents into chat channels with GolemBot

Runs an existing coding agent behind Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat, or HTTP so teams can invoke real agent sessions from chat without rebuilding the agent stack.

Integrations & ConnectorsMulti-Framework
Integrations & Connectors Multi-Framework Security Reviewed
⭐ 312 GitHub stars ⬇ 177/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill bridge-coding-agents-into-chat-channels-with-golembot Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
GolemBot CLI, Node.js 18+, selected coding agent engine, selected chat or HTTP gateway credentials
Install & setup
Install with npm install -g golembot, then run golembot onboard for guided setup or golembot init -e claude-code -n my-bot followed by golembot gateway.
Author
0xranx
Publisher
Independent
Last updated
Jul 26, 2026
Quick brief

## What the agent does
The agent uses GolemBot to initialize a bot workspace, connect a supported coding agent engine, start the gateway, and route chat messages or HTTP requests into real agent sessions. It can expose Claude Code, Codex, Cursor, or OpenCode-backed work through team chat while keeping the agent’s project directory and configuration inspectable.

How it works

What this skill actually does

## When to use it
Use this when users need to summon an existing coding agent from Slack, Telegram, Discord, Feishu, DingTalk, WeCom, WeChat, or a product integration rather than staying in an IDE or terminal. It fits team assistant, internal support, scheduled report, and remote agent-operation workflows.

## Scope boundary
This is not a generic chatbot framework entry. The skill is bounded to the operator workflow of deploying an already-capable coding agent behind messaging and HTTP gateways, configuring engines/providers/channels, and running or supervising those gateways. It should not expand into broad bot design, prompt engineering, or LLM framework development.

## Source evidence
The upstream README documents npm installation, golembot init/onboard/run/gateway/fleet commands, supported channels, supported engines, provider switching, dashboard/fleet operations, scheduled tasks, multimodal channel handling, and embedding through the TypeScript API.