{
  "schemaVersion": "1.0",
  "item": {
    "slug": "telegram-context",
    "name": "Telegram Context",
    "source": "tencent",
    "type": "skill",
    "category": "通讯协作",
    "sourceUrl": "https://clawhub.ai/fourthdensity/telegram-context",
    "canonicalUrl": "https://clawhub.ai/fourthdensity/telegram-context",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/telegram-context",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=telegram-context",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/telegram-context"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/telegram-context",
    "agentPageUrl": "https://openagent3.xyz/skills/telegram-context/agent",
    "manifestUrl": "https://openagent3.xyz/skills/telegram-context/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/telegram-context/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Telegram Context",
        "body": "Provides conversational continuity by fetching recent Telegram messages at session start. When enabled, the agent automatically retrieves message history to maintain context across disconnected sessions."
      },
      {
        "title": "Credits",
        "body": "Created by @fourthdensity"
      },
      {
        "title": "Commands",
        "body": "/telegram-context on — Enable automatic history fetching\n/telegram-context off — Disable automatic fetching\n/telegram-context status — Show current settings\n/telegram-context fetch [n] — Manually fetch last n messages (default: 20)"
      },
      {
        "title": "Setup",
        "body": "The skill auto-detects Telegram channels — no configuration needed\nState is stored in memory/telegram-context.json\nOnly activates when the current channel is Telegram"
      },
      {
        "title": "How It Works",
        "body": "When a session starts in Telegram:\n\nCheck memory/telegram-context.json for enabled state\nIf enabled, fetch recent messages via message tool\nProvide history as context for the conversation\nUpdate lastFetch timestamp"
      },
      {
        "title": "State File",
        "body": "memory/telegram-context.json:\n\n{\n  \"enabled\": true,\n  \"fetchCount\": 20,\n  \"lastFetch\": \"2025-01-15T10:30:00Z\"\n}"
      },
      {
        "title": "Command Handlers",
        "body": "Enable/disable:\n\n// Read current state\nread: memory/telegram-context.json\n\n// Update state\nwrite: memory/telegram-context.json\n{\n  \"enabled\": true/false,\n  \"fetchCount\": 20,\n  \"lastFetch\": \"2025-01-15T10:30:00Z\"\n}\n\nManual fetch:\n\nmessage: {\n  action: \"list\",\n  limit: 20  // or user-specified count\n}\n// Provide results as context summary"
      },
      {
        "title": "Session Start Behavior",
        "body": "At the start of each Telegram session:\n\nCheck if memory/telegram-context.json exists\nIf enabled, call message tool with action: \"list\"\nSummarize recent messages for context window\nAcknowledge continuity to user (optional)"
      },
      {
        "title": "Implementation Scope",
        "body": "The skill uses OpenClaw's built-in message tool with:\n\naction: \"list\" — limited to the current Telegram chat only\nNo access to other chats, channels, or external Telegram accounts\nRequires the OpenClaw gateway to have Telegram channel permissions already configured"
      },
      {
        "title": "Privacy & Security",
        "body": "Data Handling:\n\nOnly fetches from the current chat (never cross-chats or other Telegram conversations)\nMessage content is included in the agent's context window and sent to the configured LLM provider\nNo message content is stored in telegram-context.json — only settings and timestamps\nMessage content may appear in OpenClaw session logs (depends on your logging configuration)\n\nRecommendations for Sensitive Conversations:\n\nUse manual fetch (/telegram-context fetch) instead of auto-fetch\nSet low fetchCount (5-10) to minimize context exposure\nDisable the skill entirely when discussing sensitive topics: /telegram-context off\nBe aware that fetched messages become part of the conversation history sent to AI models\n\nUser Control:\n\nFull toggle on/off anytime — no persistence beyond your control\nNo external credentials or API keys required\nNo binaries installed — pure instruction-based skill"
      },
      {
        "title": "Limitations",
        "body": "Telegram-only (other channels not supported)\nRequires appropriate message permissions via OpenClaw gateway\nLarge history may need summarization to fit context window\nFetched messages are sent to your configured LLM provider — review your threat model for sensitive conversations"
      },
      {
        "title": "Tips",
        "body": "Set fetchCount to 10-30 for most use cases (balance context vs. tokens)\nUse /telegram-context fetch 50 when you need deep context for a specific task\nWorks best alongside MEMORY.md for long-term persistence"
      }
    ],
    "body": "Telegram Context\n\nProvides conversational continuity by fetching recent Telegram messages at session start. When enabled, the agent automatically retrieves message history to maintain context across disconnected sessions.\n\nCredits\n\nCreated by @fourthdensity\n\nCommands\n/telegram-context on — Enable automatic history fetching\n/telegram-context off — Disable automatic fetching\n/telegram-context status — Show current settings\n/telegram-context fetch [n] — Manually fetch last n messages (default: 20)\nSetup\nThe skill auto-detects Telegram channels — no configuration needed\nState is stored in memory/telegram-context.json\nOnly activates when the current channel is Telegram\nHow It Works\n\nWhen a session starts in Telegram:\n\nCheck memory/telegram-context.json for enabled state\nIf enabled, fetch recent messages via message tool\nProvide history as context for the conversation\nUpdate lastFetch timestamp\nState File\n\nmemory/telegram-context.json:\n\n{\n  \"enabled\": true,\n  \"fetchCount\": 20,\n  \"lastFetch\": \"2025-01-15T10:30:00Z\"\n}\n\nImplementation Notes\nCommand Handlers\n\nEnable/disable:\n\n// Read current state\nread: memory/telegram-context.json\n\n// Update state\nwrite: memory/telegram-context.json\n{\n  \"enabled\": true/false,\n  \"fetchCount\": 20,\n  \"lastFetch\": \"2025-01-15T10:30:00Z\"\n}\n\n\nManual fetch:\n\nmessage: {\n  action: \"list\",\n  limit: 20  // or user-specified count\n}\n// Provide results as context summary\n\nSession Start Behavior\n\nAt the start of each Telegram session:\n\nCheck if memory/telegram-context.json exists\nIf enabled, call message tool with action: \"list\"\nSummarize recent messages for context window\nAcknowledge continuity to user (optional)\nImplementation Scope\n\nThe skill uses OpenClaw's built-in message tool with:\n\naction: \"list\" — limited to the current Telegram chat only\nNo access to other chats, channels, or external Telegram accounts\nRequires the OpenClaw gateway to have Telegram channel permissions already configured\nPrivacy & Security\n\nData Handling:\n\nOnly fetches from the current chat (never cross-chats or other Telegram conversations)\nMessage content is included in the agent's context window and sent to the configured LLM provider\nNo message content is stored in telegram-context.json — only settings and timestamps\nMessage content may appear in OpenClaw session logs (depends on your logging configuration)\n\nRecommendations for Sensitive Conversations:\n\nUse manual fetch (/telegram-context fetch) instead of auto-fetch\nSet low fetchCount (5-10) to minimize context exposure\nDisable the skill entirely when discussing sensitive topics: /telegram-context off\nBe aware that fetched messages become part of the conversation history sent to AI models\n\nUser Control:\n\nFull toggle on/off anytime — no persistence beyond your control\nNo external credentials or API keys required\nNo binaries installed — pure instruction-based skill\nLimitations\nTelegram-only (other channels not supported)\nRequires appropriate message permissions via OpenClaw gateway\nLarge history may need summarization to fit context window\nFetched messages are sent to your configured LLM provider — review your threat model for sensitive conversations\nTips\nSet fetchCount to 10-30 for most use cases (balance context vs. tokens)\nUse /telegram-context fetch 50 when you need deep context for a specific task\nWorks best alongside MEMORY.md for long-term persistence"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/fourthdensity/telegram-context",
    "publisherUrl": "https://clawhub.ai/fourthdensity/telegram-context",
    "owner": "fourthdensity",
    "version": "1.0.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/telegram-context",
    "downloadUrl": "https://openagent3.xyz/downloads/telegram-context",
    "agentUrl": "https://openagent3.xyz/skills/telegram-context/agent",
    "manifestUrl": "https://openagent3.xyz/skills/telegram-context/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/telegram-context/agent.md"
  }
}