Menu

Individual skill

grok-bot-gateway

0upvotes

An official-webhook-only gateway to all your Grok Bots. Use this when a coding agent or script needs to list a Grok Bot team, read a Bot's transcript or message a Bot, or when a Grok Bot user wants to host that gateway; it detects which side you're on and guides you. Callers (Claude Code, Codex, scripts) use the grokgw client; hosts create the gateway Bot, its webhook routine and a host config. Getting results back is optional and goes over a return path you choose (none by default).

SKILL.md

Read pinned source

Source commit 94b7894bf2802c0fcebeb23035dc1ad6b1286e48

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
25
Repository last updated
Nov 5, 2026
License
Apache-2.0

Observed agent integration: claude-code

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Grok Bot gateway

An official-webhook-only gateway to all your Grok Bots: list them, read their transcripts and message them from outside Grok Bot. One dedicated **gateway Bot** has a routine with an official webhook trigger. An outside tool POSTs a small JSON request to that webhook, the gateway Bot wakes up, does one of four things (`ping`, list the Bots, read a Bot's transcript, send a Bot a message) and hands the result back over a **return path** the caller chose. Every request is a full Bot run, so it is asynchronous (tens of seconds to minutes) and spends the account's Grok Bot usage.

How results come back is optional and up to the caller. The default is `none` (fire-and-forget): `ping` and `send` work, but nothing is read back. Setting a return path (`tailnet`, `tunnel`, `github` or `callback`) enables `list`, `read`, `ask` and `fetch`. No mode is "better"; see [references/return-paths.md](references/return-paths.md) for a neutral comparison.

There are two roles, and this one file serves both:

- **Caller:** the outside side. Claude Code, Codex or a script on a laptop or in CI, using the `grokgw` client.
- **Host:** the Grok Bot side. A Grok Bot account that runs the gateway Bot on its cloud computer.

Read **Step 0**, then only your role's section. The reference material at the end is shared.

Files in this skill (paths are relative to this folder):