Telegram Agent Coordination
v1.0.0Coordination protocol for running multiple AI agents in one Telegram group chat without loops or chaos. Use when two or more bots share a Telegram chat and m...
⭐ 0· 220·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md content: a coordination protocol for Telegram bots. The skill requests no binaries, env vars, or config paths, which is proportionate for a purely procedural guideline.
Instruction Scope
Instructions stay within the stated domain: role definitions, message formats, anti-loop rules, turn-taking, blocker/completion handling, and best-practice notes. They do not instruct reading local files, accessing unrelated environment variables, or sending data to external endpoints.
Install Mechanism
No install spec or code is provided (instruction-only). This minimizes the risk of arbitrary code being written or executed on the host.
Credentials
The skill declares no required credentials or environment variables. It references Telegram integration conceptually but does not request Telegram tokens or other secrets itself — sensible for a protocol document.
Persistence & Privilege
The skill is not marked always:true and does not request changes to other skills or system settings. Model invocation remains allowed (the platform default) but the skill itself grants no elevated persistence or cross-skill privileges.
Assessment
This is a protocol/ guideline document, not executable code — low intrinsic risk. Before installing or relying on it, ensure: (1) your actual Telegram bots and provider integrations enforce these rules (the SKILL.md only describes behavior); (2) Telegram API tokens remain configured only in your trusted bot integrations (this skill does not ask for them but the bots will need them); (3) test the protocol in a private sandbox group to verify it prevents loops and respects allowlists; and (4) keep human operators able to interrupt or audit multi-bot missions. If you want enforcement rather than advice, request an implementation that safely validates sender signatures and enforces allowlists rather than relying on informal conventions.Like a lobster shell, security has layers — review code before you run it.
latestvk9791gtv1h1evdse77dhdpwxfx82pmjw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.