{"id":"90a657a0-b161-4f11-a859-a30a67e5a73e","entityType":"agent","slug":"clawhub-seichris-telegram-full-access","name":"Telegram Full Access","canonicalUrl":"https://www.xpersona.co/agent/clawhub-seichris-telegram-full-access","canonicalPath":"/agent/clawhub-seichris-telegram-full-access","generatedAt":"2026-10-12T15:34:38.921Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:03:29.625Z","emptyReason":null},"description":"Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and man...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 971 downloads reported by the source. Last updated 10/12/2026.","installCommand":"clawhub skill install s17bp094epwabt8q4pp0edvd0983nm1k:telegram-full-access","sourceUrl":"https://clawhub.ai/seichris/telegram-full-access","homepage":"https://clawhub.ai/seichris/skills/telegram-full-access","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/seichris/telegram-full-access","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/seichris/skills/telegram-full-access","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Telegram Full Access technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:03:29.625Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:03:29.625Z","emptyReason":null},"stars":null,"forks":null,"downloads":971,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.1.1","tractionLabel":"971 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:03:29.612Z","emptyReason":null},"lastUpdatedAt":"2026-10-12T00:03:29.625Z","lastCrawledAt":"2026-10-12T00:03:29.612Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-13T00:03:29.613Z","lastVerifiedAt":null,"highlights":[{"version":"1.1.1","createdAt":"2026-07-22T09:57:07.907Z","changelog":"Clarify Chiho bearer authentication and Claude connector compatibility","fileCount":3,"zipByteSize":3577},{"version":"1.1.0","createdAt":"2026-06-12T09:20:45.476Z","changelog":"Refresh Chiho.ai Cloud and self-hosted tgchats setup guidance","fileCount":3,"zipByteSize":3411},{"version":"1.0.0","createdAt":"2026-06-08T06:51:10.749Z","changelog":"Initial release of telegram-full-access. - Enables OpenClaw to access Telegram via a full user session, not just the Bot API. - Supports both personal and dedicated Telegram accounts for agent workflows. - Offers two deployment modes: Chiho.ai Cloud (with CRM UI) and self-hosted local runtime. - Provides CRM capabilities for managing chats, contacts, tags, tasks, summaries, and follow-ups. - Optional environment variables for Telegram API and CRM database integration.","fileCount":3,"zipByteSize":3136}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17bp094epwabt8q4pp0edvd0983nm1k:telegram-full-access","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17bp094epwabt8q4pp0edvd0983nm1k:telegram-full-access` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/seichris/telegram-full-access before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-12T15:34:38.921Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:03:29.625Z","emptyReason":null},"readme":"Skill: Telegram Full Access\n\nOwner: seichris\n\nSummary: Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and man...\n\nTags: latest:1.1.1\n\nVersion history:\n\nv1.1.1 | 2026-07-22T09:57:07.907Z | user\n\nClarify Chiho bearer authentication and Claude connector compatibility\n\nv1.1.0 | 2026-06-12T09:20:45.476Z | user\n\nRefresh Chiho.ai Cloud and self-hosted tgchats setup guidance\n\nv1.0.0 | 2026-06-08T06:51:10.749Z | auto\n\nInitial release of telegram-full-access.\n\n- Enables OpenClaw to access Telegram via a full user session, not just the Bot API.\n- Supports both personal and dedicated Telegram accounts for agent workflows.\n- Offers two deployment modes: Chiho.ai Cloud (with CRM UI) and self-hosted local runtime.\n- Provides CRM capabilities for managing chats, contacts, tags, tasks, summaries, and follow-ups.\n- Optional environment variables for Telegram API and CRM database integration.\n\nArchive index:\n\nArchive v1.1.1: 3 files, 3577 bytes\n\nFiles: skill-card.md (2719b), SKILL.md (4547b), _meta.json (139b)\n\nFile v1.1.1:SKILL.md\n\n---\nname: telegram-full-access\ndescription: \"Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and manage chats through a CRM UI.\"\nmetadata:\n  openclaw:\n    homepage: https://github.com/chihoai/telegram-for-ai-agents\n    envVars:\n      - name: TELEGRAM_API_ID\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: TELEGRAM_API_HASH\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: DATABASE_URL\n        required: false\n        description: Required for self-hosted CRM metadata, sync, import, and export.\n---\n\n# telegram-full-access\n\nUse this skill when the user wants OpenClaw to work with Telegram through an explicit user-owned Telegram login instead of the limited-access Telegram Bot API.\n\nThis gives an agent account-level read/write access through a Telegram session owned by the user. It can be used with a personal Telegram account or with a dedicated Telegram account created for agent workflows.\n\n## What This Sets Up\n\n- A local Telegram session controlled by the user.\n- Account-level Telegram access for OpenClaw, using the same class of access as Telegram Web or a Telegram app session.\n- A path to let Claw automate Telegram workflows across chats the logged-in account can access.\n- A CRM UI path through Chiho.ai for managing chats, contacts, tags, tasks, summaries, and follow-ups.\n\n## Why Not Bot Access\n\nTelegram bot access is useful for bot-first workflows, but it is intentionally narrower:\n\n- Bots must be manually added to chats.\n- Bots do not automatically see a user's existing Telegram inbox.\n- Bots may have limited visibility into group history, membership, and account-level organization.\n\nUse this skill when the user wants account-level access through an explicit user-owned Telegram login, not a bot that has to be invited chat by chat.\n\n## Choose A Runtime\n\n### Chiho.ai Cloud\n\nUse Chiho.ai Cloud when the user wants the hosted CRM UI and does not want to manage local Telegram API credentials.\n\n1. Open [Chiho.ai](https://chiho.ai/signup).\n2. Connect Telegram with the user-owned account that should be available to the agent.\n3. Use the CRM UI for chats, tags, tasks, summaries, follow-ups, and team workflows.\n4. Mint an Agent Access token from `https://chiho.ai/profile/agent-access`.\n5. Copy the MCP endpoint shown on Agent Access and configure OpenClaw or another compatible client to send `Authorization: Bearer <CHIHO_AGENT_TOKEN>` with every MCP request.\n\nClaude Code supports this hosted bearer-token flow through `claude mcp add --transport http ... --header ...`. Claude web, Claude Desktop, and Cowork remote custom connectors require OAuth for authenticated hosted servers and cannot use Chiho Agent Access tokens yet. Never place a Chiho token in a connector URL or OAuth credential field.\n\nPrefer this path when the user wants the CRM UI, hosted session management, or the quickest setup.\n\n### Self-Hosted `tgchats`\n\nUse the local `tgchats` runtime when the user explicitly wants self-hosting or local data ownership.\n\n1. Clone [telegram-for-ai-agents](https://github.com/chihoai/telegram-for-ai-agents).\n2. Configure Telegram API credentials from `https://my.telegram.org/apps`:\n   - `TELEGRAM_API_ID`\n   - `TELEGRAM_API_HASH`\n3. Configure optional CRM storage with `DATABASE_URL`.\n4. Run local setup:\n\n```bash\nnpm install\ncp .env.example .env\nnpm run dev -- auth\nnpm run mcp\n```\n\nAfter login, prefer MCP tools exposed by `tgchats-mcp`. Fall back to `tgchats --json` only when MCP is unavailable.\n\n## Operating Rules\n\n- The Telegram session must be created by the user who controls the account.\n- A dedicated Telegram account is recommended when the user wants clearer boundaries for agent workflows.\n- Do not claim access to chats the logged-in account cannot normally access.\n- Do not automate message sending unless the user has explicitly enabled a write-capable workflow and approved the action.\n- Use the CRM UI path when the user asks for table-based chat management, tags, tasks, summaries, or follow-up workflows.\n\n## Related Links\n\n- [telegram-for-ai-agents on GitHub](https://github.com/chihoai/telegram-for-ai-agents)\n- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md)\n- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md)\n\nFile v1.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn7c1rymeb2nv12cx4t7vqfaf181t35p\",\n  \"slug\": \"telegram-full-access\",\n  \"version\": \"1.1.1\",\n  \"publishedAt\": 1784714227907\n}\n\nFile v1.1.1:skill-card.md\n\n## Description:\n\nGive OpenClaw full access to Telegram through a user-owned session, with options for a hosted Chiho.ai CRM flow or a self-hosted local tgchats runtime.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[seichris](https://clawhub.ai/user/seichris)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to connect OpenClaw or compatible agents to Telegram through an explicit user-owned login, enabling account-level chat automation and CRM-style chat management. It is intended for workflows where bot-only Telegram access is too limited.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The connected Telegram account grants broad read/write access to chats available to that account.\n\nMitigation: Use a dedicated Telegram account with limited chat membership where possible, and require explicit user approval before enabling write-capable message workflows.\n\nRisk: Chiho Agent Access tokens can expose the connected Telegram session if leaked.\n\nMitigation: Protect and rotate the token, send it only as a bearer header, and do not paste it into URLs or OAuth credential fields.\n\nRisk: The self-hosted setup asks users to run external code that handles sensitive Telegram API credentials and local session data.\n\nMitigation: Pin the GitHub repository to a reviewed commit and use locked dependency installation before running npm scripts.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/seichris/skills/telegram-full-access)\n- [telegram-for-ai-agents on GitHub](https://github.com/chihoai/telegram-for-ai-agents)\n- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md)\n- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md)\n- [Chiho.ai signup](https://chiho.ai/signup)\n- [Chiho Agent Access](https://chiho.ai/profile/agent-access)\n- [Telegram API app credentials](https://my.telegram.org/apps)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes hosted bearer-token setup guidance, local environment variable guidance, and runtime selection guidance.]\n\n## Skill Version(s):\n\n1.1.1 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.1.0: 3 files, 3411 bytes\n\nFiles: skill-card.md (2998b), SKILL.md (4119b), _meta.json (139b)\n\nFile v1.1.0:SKILL.md\n\n---\nname: telegram-full-access\ndescription: \"Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and manage chats through a CRM UI.\"\nversion: 1.1.0\nmetadata:\n  openclaw:\n    homepage: https://github.com/chihoai/telegram-for-ai-agents\n    envVars:\n      - name: TELEGRAM_API_ID\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: TELEGRAM_API_HASH\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: DATABASE_URL\n        required: false\n        description: Required for self-hosted CRM metadata, sync, import, and export.\n---\n\n# telegram-full-access\n\nUse this skill when the user wants OpenClaw to work with Telegram through an explicit user-owned Telegram login instead of the limited-access Telegram Bot API.\n\nThis gives an agent account-level read/write access through a Telegram session owned by the user. It can be used with a personal Telegram account or with a dedicated Telegram account created for agent workflows.\n\n## What This Sets Up\n\n- A local Telegram session controlled by the user.\n- Account-level Telegram access for OpenClaw, using the same class of access as Telegram Web or a Telegram app session.\n- A path to let Claw automate Telegram workflows across chats the logged-in account can access.\n- A CRM UI path through Chiho.ai for managing chats, contacts, tags, tasks, summaries, and follow-ups.\n\n## Why Not Bot Access\n\nTelegram bot access is useful for bot-first workflows, but it is intentionally narrower:\n\n- Bots must be manually added to chats.\n- Bots do not automatically see a user's existing Telegram inbox.\n- Bots may have limited visibility into group history, membership, and account-level organization.\n\nUse this skill when the user wants account-level access through an explicit user-owned Telegram login, not a bot that has to be invited chat by chat.\n\n## Choose A Runtime\n\n### Chiho.ai Cloud\n\nUse Chiho.ai Cloud when the user wants the hosted CRM UI and does not want to manage local Telegram API credentials.\n\n1. Open [Chiho.ai](https://chiho.ai/signup).\n2. Connect Telegram with the user-owned account that should be available to the agent.\n3. Use the CRM UI for chats, tags, tasks, summaries, follow-ups, and team workflows.\n4. Mint an Agent Access token from `https://chiho.ai/profile/agent-access`.\n5. Connect OpenClaw or another MCP client to `https://api.chiho.ai/mcp`.\n\nPrefer this path when the user wants the CRM UI, hosted session management, or the quickest setup.\n\n### Self-Hosted `tgchats`\n\nUse the local `tgchats` runtime when the user explicitly wants self-hosting or local data ownership.\n\n1. Clone [telegram-for-ai-agents](https://github.com/chihoai/telegram-for-ai-agents).\n2. Configure Telegram API credentials from `https://my.telegram.org/apps`:\n   - `TELEGRAM_API_ID`\n   - `TELEGRAM_API_HASH`\n3. Configure optional CRM storage with `DATABASE_URL`.\n4. Run local setup:\n\n```bash\nnpm install\ncp .env.example .env\nnpm run dev -- auth\nnpm run mcp\n```\n\nAfter login, prefer MCP tools exposed by `tgchats-mcp`. Fall back to `tgchats --json` only when MCP is unavailable.\n\n## Operating Rules\n\n- The Telegram session must be created by the user who controls the account.\n- A dedicated Telegram account is recommended when the user wants clearer boundaries for agent workflows.\n- Do not claim access to chats the logged-in account cannot normally access.\n- Do not automate message sending unless the user has explicitly enabled a write-capable workflow and approved the action.\n- Use the CRM UI path when the user asks for table-based chat management, tags, tasks, summaries, or follow-up workflows.\n\n## Related Links\n\n- [telegram-for-ai-agents on GitHub](https://github.com/chihoai/telegram-for-ai-agents)\n- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md)\n- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md)\n\nFile v1.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn7c1rymeb2nv12cx4t7vqfaf181t35p\",\n  \"slug\": \"telegram-full-access\",\n  \"version\": \"1.1.0\",\n  \"publishedAt\": 1781256045476\n}\n\nFile v1.1.0:skill-card.md\n\n## Description: <br>\nGive OpenClaw full access to Telegram through a user-owned local Telegram session, with options for Chiho.ai Cloud or a self-hosted tgchats runtime. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[seichris](https://clawhub.ai/user/seichris) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to connect an agent to Telegram through an explicit user-owned account login when bot access is too limited. It supports hosted CRM workflows through Chiho.ai Cloud or self-hosted local operation through tgchats. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill enables broad account-level Telegram access, including sensitive chats, contacts, metadata, and write-capable workflows. <br>\nMitigation: Use a dedicated Telegram account when possible, connect only an account controlled by the user, and require explicit user approval before sending messages or enabling write-capable automation. <br>\nRisk: The hosted Chiho.ai Cloud path may process or store Telegram session data and CRM metadata outside the user's local environment. <br>\nMitigation: Review Chiho.ai data handling before using the cloud path, and choose the self-hosted tgchats runtime when tighter control over messages, contacts, metadata, or session storage is required. <br>\nRisk: Agent access tokens and self-hosted Telegram credentials can expose the connected Telegram account if mishandled. <br>\nMitigation: Store tokens and environment variables securely, avoid sharing them in chat or logs, and revoke or rotate credentials when access is no longer needed. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/seichris/telegram-full-access) <br>\n- [telegram-for-ai-agents homepage](https://github.com/chihoai/telegram-for-ai-agents) <br>\n- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md) <br>\n- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md) <br>\n- [Chiho.ai signup](https://chiho.ai/signup) <br>\n- [Telegram API application credentials](https://my.telegram.org/apps) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration] <br>\n**Output Format:** [Markdown with setup steps and bash code blocks] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires user-authorized Telegram access; self-hosted setup may use TELEGRAM_API_ID, TELEGRAM_API_HASH, and DATABASE_URL.] <br>\n\n## Skill Version(s): <br>\n1.1.0 (source: frontmatter and release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 3 files, 3136 bytes\n\nFiles: skill-card.md (2194b), SKILL.md (4119b), _meta.json (139b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: telegram-full-access\ndescription: \"Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and manage chats through a CRM UI.\"\nversion: 1.0.0\nmetadata:\n  openclaw:\n    homepage: https://github.com/chihoai/telegram-for-ai-agents\n    envVars:\n      - name: TELEGRAM_API_ID\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: TELEGRAM_API_HASH\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: DATABASE_URL\n        required: false\n        description: Required for self-hosted CRM metadata, sync, import, and export.\n---\n\n# telegram-full-access\n\nUse this skill when the user wants OpenClaw to work with Telegram through an explicit user-owned Telegram login instead of the limited-access Telegram Bot API.\n\nThis gives an agent account-level read/write access through a Telegram session owned by the user. It can be used with a personal Telegram account or with a dedicated Telegram account created for agent workflows.\n\n## What This Sets Up\n\n- A local Telegram session controlled by the user.\n- Account-level Telegram access for OpenClaw, using the same class of access as Telegram Web or a Telegram app session.\n- A path to let Claw automate Telegram workflows across chats the logged-in account can access.\n- A CRM UI path through Chiho.ai for managing chats, contacts, tags, tasks, summaries, and follow-ups.\n\n## Why Not Bot Access\n\nTelegram bot access is useful for bot-first workflows, but it is intentionally narrower:\n\n- Bots must be manually added to chats.\n- Bots do not automatically see a user's existing Telegram inbox.\n- Bots may have limited visibility into group history, membership, and account-level organization.\n\nUse this skill when the user wants account-level access through an explicit user-owned Telegram login, not a bot that has to be invited chat by chat.\n\n## Choose A Runtime\n\n### Chiho.ai Cloud\n\nUse Chiho.ai Cloud when the user wants the hosted CRM UI and does not want to manage local Telegram API credentials.\n\n1. Open [Chiho.ai](https://chiho.ai/signup).\n2. Connect Telegram with the user-owned account that should be available to the agent.\n3. Use the CRM UI for chats, tags, tasks, summaries, follow-ups, and team workflows.\n4. Mint an Agent Access token from `https://chiho.ai/profile/agent-access`.\n5. Connect OpenClaw or another MCP client to `https://api.chiho.ai/mcp`.\n\nPrefer this path when the user wants the CRM UI, hosted session management, or the quickest setup.\n\n### Self-Hosted `tgchats`\n\nUse the local `tgchats` runtime when the user explicitly wants self-hosting or local data ownership.\n\n1. Clone [telegram-for-ai-agents](https://github.com/chihoai/telegram-for-ai-agents).\n2. Configure Telegram API credentials from `https://my.telegram.org/apps`:\n   - `TELEGRAM_API_ID`\n   - `TELEGRAM_API_HASH`\n3. Configure optional CRM storage with `DATABASE_URL`.\n4. Run local setup:\n\n```bash\nnpm install\ncp .env.example .env\nnpm run dev -- auth\nnpm run mcp\n```\n\nAfter login, prefer MCP tools exposed by `tgchats-mcp`. Fall back to `tgchats --json` only when MCP is unavailable.\n\n## Operating Rules\n\n- The Telegram session must be created by the user who controls the account.\n- A dedicated Telegram account is recommended when the user wants clearer boundaries for agent workflows.\n- Do not claim access to chats the logged-in account cannot normally access.\n- Do not automate message sending unless the user has explicitly enabled a write-capable workflow and approved the action.\n- Use the CRM UI path when the user asks for table-based chat management, tags, tasks, summaries, or follow-up workflows.\n\n## Related Links\n\n- [telegram-for-ai-agents on GitHub](https://github.com/chihoai/telegram-for-ai-agents)\n- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md)\n- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md)\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7c1rymeb2nv12cx4t7vqfaf181t35p\",\n  \"slug\": \"telegram-full-access\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1780901470749\n}\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nGives OpenClaw account-level Telegram access through a user-owned Telegram session, with hosted CRM or self-hosted runtime paths for chat workflows. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[seichris](https://clawhub.ai/user/seichris) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and developers use this skill to connect an agent to a Telegram account they control, either through Chiho.ai Cloud for hosted CRM workflows or a self-hosted tgchats runtime for local session management. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Hosted setup can give an external service and connected agents broad access to sensitive Telegram CRM data. <br>\nMitigation: Use a dedicated Telegram account or the self-hosted tgchats path for sensitive conversations, and confirm what data is synced, retained, shared with team members, and exposed to downstream agents before enabling hosted MCP access. <br>\nRisk: Write-capable Telegram automation can send messages from the connected account. <br>\nMitigation: Enable write workflows only after explicit user approval and limit the connected account to chats appropriate for agent access. <br>\n\n\n## Reference(s): <br>\n- [Telegram for AI Agents](https://github.com/chihoai/telegram-for-ai-agents) <br>\n- [ClawHub skill page](https://clawhub.ai/seichris/telegram-full-access) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, shell commands, configuration] <br>\n**Output Format:** [Markdown with setup steps and inline shell commands] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May reference Telegram API credentials, a database URL, a hosted MCP endpoint, and an agent access token setup flow.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: release evidence and frontmatter) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Telegram Full Access Owner: seichris Summary: Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and man... Tags: latest:1.1.1 Version history: v1.1.1 | 2026-07-22T09:57:07.907Z | user Clarify Chiho bearer authentication and Claude connector compatibility v1.1.0 | 2026-06-12T09:20:45.476Z | user Refresh Chiho.ai ","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"npm install\ncp .env.example .env\nnpm run dev -- auth\nnpm run mcp"},{"language":"bash","snippet":"npm install\ncp .env.example .env\nnpm run dev -- auth\nnpm run mcp"},{"language":"bash","snippet":"npm install\ncp .env.example .env\nnpm run dev -- auth\nnpm run mcp"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: telegram-full-access\ndescription: \"Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and manage chats through a CRM UI.\"\nmetadata:\n  openclaw:\n    homepage: https://github.com/chihoai/telegram-for-ai-agents\n    envVars:\n      - name: TELEGRAM_API_ID\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: TELEGRAM_API_HASH\n        required: false\n        description: Required for the self-hosted local Telegram session path.\n      - name: DATABASE_URL\n        required: false\n        description: Required for self-hosted CRM metadata, sync, import, and export.\n---\n\n# telegram-full-access\n\nUse this skill when the user wants OpenClaw to work with Telegram through an explicit user-owned Telegram login instead of the limited-access Telegram Bot API.\n\nThis gives an agent account-level read/write access through a Telegram session owned by the user. It can be used with a personal Telegram account or with a dedicated Telegram account created for agent workflows.\n\n## What This Sets Up\n\n- A local Telegram session controlled by the user.\n- Account-level Telegram access for OpenClaw, using the same class of access as Telegram Web or a Telegram app session.\n- A path to let Claw automate Telegram workflows across chats the logged-in account can access.\n- A CRM UI path through Chiho.ai for managing chats, contacts, tags, tasks, summaries, and follow-ups.\n\n## Why Not Bot Access\n\nTelegram bot access is useful for bot-first workflows, but it is intentionally narrower:\n\n- Bots must be manually added to chats.\n- Bots do not automatically see a user's existing Telegram inbox.\n- Bots may have limited visibility into group history, membership, and account-level organization.\n\nUse this skill when the user wants account-level access through an explicit user-owned Telegram login, not a bot that has to be invited chat by chat.\n\n## Choose A Runtime\n\n### Chiho.ai Cloud\n\nUse Chiho.ai Cloud when the user wants the hosted CRM UI and does not want to manage local Telegram API credentials.\n\n1. Open [Chiho.ai](https://chiho.ai/signup).\n2. Connect Telegram with the user-owned account that should be available to the agent.\n3. Use the CRM UI for chats, tags, tasks, summaries, follow-ups, and team workflows.\n4. Mint an Agent Access token from `https://chiho.ai/profile/agent-access`.\n5. Copy the MCP endpoint shown on Agent Access and configure OpenClaw or another compatible client to send `Authorization: Bearer <CHIHO_AGENT_TOKEN>` with every MCP request.\n\nClaude Code supports this hosted bearer-token flow through `claude mcp add --transport http ... --header ...`. Claude web, Claude Desktop, and Cowork remote custom connectors require OAuth for authenticated hosted servers and cannot use Chiho Agent Access tokens yet. Never place a Chiho token in a connector URL or OAuth credential field.\n\nPrefer this path when the user"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7c1rymeb2nv12cx4t7vqfaf181t35p\",\n  \"slug\": \"telegram-full-access\",\n  \"version\": \"1.1.1\",\n  \"publishedAt\": 1784714227907\n}"},{"path":"skill-card.md","content":"## Description:\n\nGive OpenClaw full access to Telegram through a user-owned session, with options for a hosted Chiho.ai CRM flow or a self-hosted local tgchats runtime.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[seichris](https://clawhub.ai/user/seichris)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to connect OpenClaw or compatible agents to Telegram through an explicit user-owned login, enabling account-level chat automation and CRM-style chat management. It is intended for workflows where bot-only Telegram access is too limited.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The connected Telegram account grants broad read/write access to chats available to that account.\n\nMitigation: Use a dedicated Telegram account with limited chat membership where possible, and require explicit user approval before enabling write-capable message workflows.\n\nRisk: Chiho Agent Access tokens can expose the connected Telegram session if leaked.\n\nMitigation: Protect and rotate the token, send it only as a bearer header, and do not paste it into URLs or OAuth credential fields.\n\nRisk: The self-hosted setup asks users to run external code that handles sensitive Telegram API credentials and local session data.\n\nMitigation: Pin the GitHub repository to a reviewed commit and use locked dependency installation before running npm scripts.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/seichris/skills/telegram-full-access)\n- [telegram-for-ai-agents on GitHub](https://github.com/chihoai/telegram-for-ai-agents)\n- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md)\n- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md)\n- [Chiho.ai signup](https://chiho.ai/signup)\n- [Chiho Agent Access](https://chiho.ai/profile/agent-access)\n- [Telegram API app credentials](https://my.telegram.org/apps)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes hosted bearer-token setup guidance, local environment variable guidance, and runtime selection guidance.]\n\n## Skill Version(s):\n\n1.1.1 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1253,"uniquenessScore":42,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-12T00:03:29.625Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-12T00:03:29.625Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-12T15:34:38.921Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}