Discord Cross-Gateway Delegation
v2.1.1Set up and operate full cross-gateway task delegation between two OpenClaw Discord bots across different PCs/gateways. Use when: another OpenClaw bot lives o...
⭐ 0· 129·0 current·0 all-time
by@jini92
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the content: all files are documentation and runbooks about creating a cross-gateway delegation lane between two Discord bots. There are no unexpected binaries, env vars, or installs required.
Instruction Scope
The SKILL.md and referenced docs focus narrowly on creating channels, sending structured envelopes, and diagnosing guild/channel policies. They reference internal config keys (e.g., channels.discord.*) and example placeholders like $WORKSPACE_ROOT, but do not instruct the agent to read arbitrary system files or exfiltrate secrets. The documentation repeatedly recommends constraints such as 'No credential disclosure.'
Install Mechanism
No install spec or code files are present (instruction-only), so nothing will be downloaded or written during install. This minimizes installation risk.
Credentials
The skill does not request environment variables, credentials, or config paths in metadata. Example envelopes mention repo or workspace placeholders, but those are examples and not required by the skill.
Persistence & Privilege
always is false and the skill is user-invocable. Model invocation is allowed (the platform default), which is appropriate for an operational how-to. The skill does not request permanent presence or system-wide changes.
Assessment
This skill is a documentation/runbook for wiring two OpenClaw Discord bots together; it does not contain code or request credentials. Before using it: (1) ensure you only use it with bots/accounts you control and trust (bot tokens remain sensitive and should never be pasted into task envelopes), (2) follow the checklist and test with non-sensitive, read-only tasks first (the examples explicitly forbid credential disclosure), (3) be aware the docs reference gateway config keys — you'll need access to the worker gateway's configuration to fix guild/channel policies, and (4) if you plan to automate any steps via your bot, ensure your automation code enforces the documented 'no credential disclosure' and 'no destructive actions' constraints. If you need a higher-assurance review, ask for the actual bot integration code that will perform the delegation so that it can be audited.Like a lobster shell, security has layers — review code before you run it.
latestvk9734n5am5ac1han4dtmh74d4h8375z0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.