Telegram Context

Fetches recent Telegram messages at session start to maintain conversation context across sessions, with toggle and manual fetch commands.

This skill appears to do exactly what it says: when enabled it will fetch recent messages from the current Telegram chat (via the platform's message tool), include those messages in the AI context, and store only a small local settings file (memory/telegram-context.json). Before enabling: (1) Confirm you trust the OpenClaw gateway's Telegram integration and that it enforces 'current chat only' permissions; misconfiguration there could broaden access. (2) Remember fetched messages are sent to your configured LLM provider and may appear in logs—avoid auto-fetch for very sensitive conversations or use manual fetch with a low fetchCount. (3) Check where memory/telegram-context.json is stored/backed up and who can read it. Test the skill in a non-sensitive chat first to confirm behavior matches expectations.

Type: OpenClaw Skill Name: telegram-context Version: 1.0.1 The skill is designed to fetch Telegram message history from the current chat and provide it as context to the LLM. While this involves sending potentially sensitive user data to the configured LLM provider, this behavior is explicitly and transparently documented multiple times in SKILL.md under 'Privacy & Security' and 'Limitations'. The skill declares the necessary 'message:read' permission, uses OpenClaw's built-in 'message' tool, stores state locally in 'memory/telegram-context.json', and provides user controls to manage its behavior. There is no evidence of data exfiltration to unauthorized endpoints, malicious execution, persistence mechanisms, prompt injection attempts against the agent, or obfuscation. The skill's actions are fully aligned with its stated purpose and are openly disclosed.