Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Telegram Routing
v1.0.0Manage how OpenClaw routes Telegram messages to different Claude model backends. Switch between CLI and API providers with simple config changes.
⭐ 0· 208·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to manage routing via OpenClaw config, which legitimately requires reading and writing ~/.openclaw/openclaw.json and reading gateway logs. However, the registry metadata lists no required config paths or credentials even though the SKILL.md explicitly instructs access and modification of ~/.openclaw/openclaw.json and gateway logs; that mismatch is incoherent and should be justified.
Instruction Scope
Runtime instructions tell the agent to read and update ~/.openclaw/openclaw.json, restart the OpenClaw gateway service, and inspect gateway logs. Those actions are within the skill's domain but are high-impact (persistent config change + service restart). The SKILL.md is vague about how to perform the restart and about where credentials for API backends would come from, giving the agent broad discretion.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. That lowers installation risk.
Credentials
The skill declares no environment variables or primary credentials, which is consistent with an editor for local config. However, the model shorthand can resolve to API providers (e.g., 'anthropic/claude-haiku-4-5') that normally require API keys; the skill does not declare or explain where such credentials are stored or how they should be supplied. That omission is notable.
Persistence & Privilege
The skill modifies a persistent user config file and instructs a service restart; even though it is not 'always: true', these persistent changes can affect runtime behavior across agent runs. Because the skill can be invoked autonomously by default, its ability to change configuration increases the potential impact and deserves caution.
What to consider before installing
This skill appears to do what it says (edit routing config and switch backends), but be cautious: it comes from an unknown source and the metadata omits the config paths the instructions require. Before installing or allowing autonomous use, verify the skill's origin, back up ~/.openclaw/openclaw.json, and test actions manually: try making the config change yourself and restarting the gateway via known commands so you control what actually runs. Ask the author to (1) declare required config paths, (2) explain how service restart is performed, and (3) document where API credentials must be stored if switching to API providers. If you don't trust it, decline installation or restrict the skill from making persistent changes/autonomous invocations.Like a lobster shell, security has layers — review code before you run it.
latestvk971q9c8wtqgtkqcsvte5y46gh82mb24
License
MIT-0
Free to use, modify, and redistribute. No attribution required.