Signal Hardened

Bridge THIS Claude Code session to Telegram, Discord, Feishu/Lark, or QQ so the user can chat with Claude from their phone. Use for: setting up, starting, st...

This skill appears to do what it claims: guide setup and manage a bridge by collecting platform tokens and writing a local config at ~/.claude-to-im/config.env. Before installing or using it: 1) Inspect SKILL_DIR/references/setup-guides.md and config.env.example so you know exactly which tokens/IDs will be stored. 2) Ensure the skill (or your agent) will set restrictive permissions on the config file (chmod 600) and avoid storing secrets in additional files. 3) Confirm what exact commands it will run to start/stop the daemon (so you can audit them). 4) Never paste your tokens into unknown external endpoints — validate tokens only against official platform APIs or via local validation routines. 5) If you do not trust the author or environment, run the setup in an isolated machine or container. If you want, ask the skill author to add explicit secure-write steps (atomic write + chmod 600) and a signed start/stop script so you can audit actions before they run.

Type: OpenClaw Skill Name: signal-hardened Version: 1.0.0 The 'signal-hardened' skill is a bridge for connecting Claude Code to messaging platforms like Telegram and Discord. It demonstrates a high level of security awareness, incorporating explicit instructions in SKILL.md to mask credentials, enforce restrictive file permissions (chmod 600), and restrict token transmission to official API endpoints. The inclusion of a detailed SAFETY.md report further outlines the hardening process and guardrails implemented to prevent common agent-based vulnerabilities like credential exfiltration or scope creep.