{"id":"e499a0f2-5529-4245-b479-a063d1de4ffb","entityType":"agent","slug":"clawhub-oomol-oo-telegram","name":"Telegram Bot","canonicalUrl":"https://www.xpersona.co/agent/clawhub-oomol-oo-telegram","canonicalPath":"/agent/clawhub-oomol-oo-telegram","generatedAt":"2026-10-11T20:56:58.418Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:50:25.685Z","emptyReason":null},"description":"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-telegram","sourceUrl":"https://clawhub.ai/oomol/oo-telegram","homepage":"https://clawhub.ai/oomol/skills/oo-telegram","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/oomol/oo-telegram","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/oomol/skills/oo-telegram","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Telegram Bot 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-11T16:50:25.685Z","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-11T16:50:25.685Z","emptyReason":null},"stars":null,"forks":null,"downloads":1024,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:50:25.678Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T16:50:25.685Z","lastCrawledAt":"2026-10-11T16:50:25.678Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T16:50:25.678Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-09-20T03:32:10.467Z","changelog":"- Operates Telegram Bot accounts through the OOMOL `telegram` connector and `oo` CLI, with credentials injected server-side. - Provides schema-first execution guidance for building valid action payloads before each run. - Supports core messaging actions including sending text, media, polls, locations, contacts, albums, reactions, and chat actions. - Includes chat and member administration capabilities such as invites, pins, permissions, bans, promotions, and join request handling. - Covers bot update and webhook workflows, plus business connection and business message actions. - Defines safety expectations for read, write, and destructive Telegram operations. Source: `oomol-lab/skills@792ad44`","fileCount":3,"zipByteSize":4630},{"version":"1.0.4","createdAt":"2026-09-15T05:15:33.204Z","changelog":"- Adds a Telegram Bot skill for operating bots through the OOMOL `telegram` connector using the `oo` CLI. - Supports message sending across text, media, polls, contacts, locations, venues, reactions, and chat actions. - Includes chat administration actions for members, permissions, pins, invite links, join requests, and bot commands. - Provides webhook and update management for configuring delivery, polling updates, and checking webhook status. - Documents safety rules for read, write, and destructive Telegram actions, with schema inspection before execution. Source: `oomol-lab/skills@75bac03`","fileCount":3,"zipByteSize":4714},{"version":"1.0.2","createdAt":"2026-07-28T00:56:06.398Z","changelog":"- Provides OOMOL-backed access to Telegram Bot operations through the `oo` CLI without exposing raw bot tokens. - Supports schema-first execution with `oo connector schema` and `oo connector run` for validated action payloads. - Covers messaging workflows including sending, forwarding, copying, editing, pinning, reacting, and deleting messages. - Includes chat administration actions for members, permissions, invite links, join requests, commands, and webhooks. - Documents safety expectations for read, write, and destructive Telegram Bot actions. Source: `oomol-lab/skills@0fdcf2d`","fileCount":3,"zipByteSize":4759},{"version":"1.0.1","createdAt":"2026-06-09T10:22:17.239Z","changelog":"- Operates Telegram Bots through an OOMOL-connected account using the `oo` CLI, with credentials injected server-side. - Supports bot profile and chat reads, including `get_me`, chat metadata, administrators, members, member counts, updates, webhook info, and chat history polling. - Sends and manages chat content with messages, photos, documents, locations, polls, forwards, and message text edits. - Provides bot administration actions for invite links, command lists, callback query answers, and webhook configuration. - Marks write and destructive actions clearly, requiring confirmation before changing or deleting Telegram state. Source: `oomol-lab/skills@146ef20`","fileCount":3,"zipByteSize":3957},{"version":"1.0.0","createdAt":"2026-06-04T11:07:19.842Z","changelog":"- Initial release of `oo-telegram`, an OOMOL skill for operating Telegram Bot accounts through the `telegram` connector and `oo` CLI. - Adds 21 Telegram Bot actions covering messaging, media delivery, polls, locations, forwarding, message editing, and message deletion. - Supports bot and chat inspection workflows, including bot profile lookup, chat metadata, administrators, members, member counts, updates, and filtered chat history. - Includes webhook management actions for setting, deleting, and inspecting Telegram Bot webhook configuration. - Provides chat administration helpers such as command setup, invite link creation, and callback query responses. - Documents safe execution patterns, including live schema inspection before action calls and explicit confirmation for state-changing or destructive operations.","fileCount":24,"zipByteSize":15600}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-telegram","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-telegram` 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/oomol/oo-telegram 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-oomol-oo-telegram/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/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-11T20:56:58.417Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-telegram/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-11T16:50:25.685Z","emptyReason":null},"readme":"Skill: Telegram Bot\n\nOwner: oomol\n\nSummary: Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-09-20T03:32:10.467Z | user\n\n- Operates Telegram Bot accounts through the OOMOL `telegram` connector and `oo` CLI, with credentials injected server-side.\n- Provides schema-first execution guidance for building valid action payloads before each run.\n- Supports core messaging actions including sending text, media, polls, locations, contacts, albums, reactions, and chat actions.\n- Includes chat and member administration capabilities such as invites, pins, permissions, bans, promotions, and join request handling.\n- Covers bot update and webhook workflows, plus business connection and business message actions.\n- Defines safety expectations for read, write, and destructive Telegram operations.\n\nSource: `oomol-lab/skills@792ad44`\n\nv1.0.4 | 2026-09-15T05:15:33.204Z | user\n\n- Adds a Telegram Bot skill for operating bots through the OOMOL `telegram` connector using the `oo` CLI.\n- Supports message sending across text, media, polls, contacts, locations, venues, reactions, and chat actions.\n- Includes chat administration actions for members, permissions, pins, invite links, join requests, and bot commands.\n- Provides webhook and update management for configuring delivery, polling updates, and checking webhook status.\n- Documents safety rules for read, write, and destructive Telegram actions, with schema inspection before execution.\n\nSource: `oomol-lab/skills@75bac03`\n\nv1.0.2 | 2026-07-28T00:56:06.398Z | user\n\n- Provides OOMOL-backed access to Telegram Bot operations through the `oo` CLI without exposing raw bot tokens.\n- Supports schema-first execution with `oo connector schema` and `oo connector run` for validated action payloads.\n- Covers messaging workflows including sending, forwarding, copying, editing, pinning, reacting, and deleting messages.\n- Includes chat administration actions for members, permissions, invite links, join requests, commands, and webhooks.\n- Documents safety expectations for read, write, and destructive Telegram Bot actions.\n\nSource: `oomol-lab/skills@0fdcf2d`\n\nv1.0.1 | 2026-06-09T10:22:17.239Z | user\n\n- Operates Telegram Bots through an OOMOL-connected account using the `oo` CLI, with credentials injected server-side.\n- Supports bot profile and chat reads, including `get_me`, chat metadata, administrators, members, member counts, updates, webhook info, and chat history polling.\n- Sends and manages chat content with messages, photos, documents, locations, polls, forwards, and message text edits.\n- Provides bot administration actions for invite links, command lists, callback query answers, and webhook configuration.\n- Marks write and destructive actions clearly, requiring confirmation before changing or deleting Telegram state.\n\nSource: `oomol-lab/skills@146ef20`\n\nv1.0.0 | 2026-06-04T11:07:19.842Z | user\n\n- Initial release of `oo-telegram`, an OOMOL skill for operating Telegram Bot accounts through the `telegram` connector and `oo` CLI.\n- Adds 21 Telegram Bot actions covering messaging, media delivery, polls, locations, forwarding, message editing, and message deletion.\n- Supports bot and chat inspection workflows, including bot profile lookup, chat metadata, administrators, members, member counts, updates, and filtered chat history.\n- Includes webhook management actions for setting, deleting, and inspecting Telegram Bot webhook configuration.\n- Provides chat administration helpers such as command setup, invite link creation, and callback query responses.\n- Documents safe execution patterns, including live schema inspection before action calls and explicit confirmation for state-changing or destructive operations.\n\nArchive index:\n\nArchive v1.0.5: 3 files, 4630 bytes\n\nFiles: skill-card.md (2115b), SKILL.md (8018b), _meta.json (130b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: oo-telegram\ndescription: \"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Telegram Bot\"\n  author: \"OOMOL\"\n  version: \"1.0.5\"\n  services: [\"telegram\"]\n  icon: \"https://static.oomol.com/logo/third-party/Telegram.svg\"\n---\n\n# Telegram Bot\n\nOperate **Telegram Bot** through your OOMOL-connected account. This skill calls the `telegram` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Telegram Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"telegram\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `answer_callback_query` — Answer an inline keyboard callback query.\n- `approve_chat_join_request` — Approve a user's pending request to join a Telegram chat. [write]\n- `ban_chat_member` — Ban a user from a group, supergroup, or channel. [destructive]\n- `copy_message` — Copy one message without linking back to the original message. [write]\n- `copy_messages` — Copy 1-100 messages without links to the originals while preserving album grouping. [write]\n- `create_chat_invite_link` — Create an additional Telegram chat invite link with optional expiry or approval rules. [write]\n- `decline_chat_join_request` — Decline a user's pending request to join a Telegram chat. [destructive]\n- `delete_business_messages` — Delete one or more messages on behalf of a connected Telegram business account. [destructive]\n- `delete_message` — Delete a message from a chat. [destructive]\n- `delete_messages` — Delete 1-100 messages from one Telegram chat. [destructive]\n- `delete_webhook` — Delete the configured webhook and optionally drop pending updates. [destructive]\n- `edit_chat_invite_link` — Edit an additional Telegram chat invite link created by the bot. [write]\n- `edit_message_text` — Edit the text of a previously sent message or an inline message. [write]\n- `export_chat_invite_link` — Export the primary invite link for a Telegram chat. [write]\n- `forward_message` — Forward a message from one chat to another. [write]\n- `forward_messages` — Forward 1-100 messages while preserving links and album grouping. [write]\n- `get_business_connection` — Return the current state and granted rights of a Telegram business connection.\n- `get_chat` — Return metadata for a chat the bot can access.\n- `get_chat_administrators` — Return the chat administrators visible to the bot.\n- `get_chat_member` — Return information about one chat member.\n- `get_chat_members_count` — Return the number of members in a chat.\n- `get_me` — Validate the bot token and return the bot profile from Telegram Bot API.\n- `get_updates` — Poll pending updates for the bot. Use this only when webhook delivery is disabled or for debugging.\n- `get_webhook_info` — Return the webhook status configured for the bot.\n- `pin_chat_message` — Pin a message in a Telegram chat. [write]\n- `promote_chat_member` — Promote, update, or demote a supergroup or channel administrator. [write]\n- `read_business_message` — Mark an incoming message as read on behalf of a connected Telegram business account. [write]\n- `restrict_chat_member` — Set temporary or permanent permissions for one supergroup member. [write]\n- `revoke_chat_invite_link` — Revoke a Telegram chat invite link created by the bot. [destructive]\n- `send_animation` — Send a GIF or silent MPEG-4 animation by URL or Telegram file_id. [write]\n- `send_audio` — Send an MP3 or M4A audio track by URL or Telegram file_id. [write]\n- `send_chat_action` — Show a temporary typing, upload, recording, or location activity status in a chat. [write]\n- `send_contact` — Send a phone contact to a Telegram chat. [write]\n- `send_dice` — Send an animated dice, darts, basketball, football, bowling, or slot-machine emoji. [write]\n- `send_document` — Send a document by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this provider pass. [write]\n- `send_location` — Send a map location to a chat. [write]\n- `send_media_group` — Send an album containing 2-10 photos, videos, documents, or audio items. [write]\n- `send_message` — Send a text message to a chat, group, supergroup, channel, or forum topic. [write]\n- `send_photo` — Send a photo by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this first pass. [write]\n- `send_poll` — Send a native Telegram poll to a chat. [write]\n- `send_venue` — Send a venue with coordinates, title, address, and optional place identifiers. [write]\n- `send_video` — Send an MPEG-4 video by URL or Telegram file_id. [write]\n- `send_voice` — Send a playable voice message by URL or Telegram file_id. [write]\n- `set_chat_permissions` — Set default permissions for all members of a group or supergroup. [write]\n- `set_message_reaction` — Replace the bot's chosen reaction on a Telegram message. [destructive]\n- `set_my_commands` — Set the bot command list exposed in Telegram clients. [write]\n- `set_webhook` — Configure a webhook endpoint for update delivery. [write]\n- `unban_chat_member` — Unban a user so they can join the chat again. [write]\n- `unpin_all_chat_messages` — Remove all pinned messages from a Telegram chat. [destructive]\n- `unpin_chat_message` — Unpin one message, or the most recently pinned message, from a Telegram chat. [destructive]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Telegram Bot state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Telegram Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=telegram\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Telegram Bot homepage: https://core.telegram.org/bots\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn78y60sfta5p7kq45p63gehhd87z1wk\",\n  \"slug\": \"oo-telegram\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1789875130467\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nOperates Telegram Bot accounts through OOMOL's Telegram connector and oo CLI for reading bot data, sending messages, and administering chats.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to manage Telegram Bot workflows from an agent, including reading bot and chat data, sending messages or media, managing webhooks, and administering chat membership.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup can run a remote installer script on the user's machine.\n\nMitigation: Review the OOMOL CLI installation path before installing and prefer an official package or a downloaded installer that can be inspected and verified.\n\nRisk: Telegram Bot actions can send messages, delete content, ban or promote users, configure webhooks, or act through business-message permissions.\n\nMitigation: Connect only a Telegram Bot account whose permissions match the intended delegation, and confirm the exact target, payload, and effect before write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-telegram)\n- [Telegram Bot documentation](https://core.telegram.org/bots)\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)\n- [OOMOL CLI install guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with bash commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Connector executions produce JSON responses with data and execution metadata.]\n\n## Skill Version(s):\n\n1.0.5 (source: frontmatter and release evidence)\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.0.4: 3 files, 4714 bytes\n\nFiles: skill-card.md (2273b), SKILL.md (7938b), _meta.json (130b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: oo-telegram\ndescription: \"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Telegram Bot\"\n  author: \"OOMOL\"\n  version: \"1.0.4\"\n  services: [\"telegram\"]\n  icon: \"https://static.oomol.com/logo/third-party/Telegram.svg\"\n---\n\n# Telegram Bot\n\nOperate **Telegram Bot** through your OOMOL-connected account. This skill calls the `telegram` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Telegram Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"telegram\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `answer_callback_query` — Answer an inline keyboard callback query.\n- `approve_chat_join_request` — Approve a user's pending request to join a Telegram chat. [write]\n- `ban_chat_member` — Ban a user from a group, supergroup, or channel. [destructive]\n- `copy_message` — Copy one message without linking back to the original message. [write]\n- `copy_messages` — Copy 1-100 messages without links to the originals while preserving album grouping. [write]\n- `create_chat_invite_link` — Create an additional Telegram chat invite link with optional expiry or approval rules. [write]\n- `decline_chat_join_request` — Decline a user's pending request to join a Telegram chat. [write]\n- `delete_business_messages` — Delete one or more messages on behalf of a connected Telegram business account. [destructive]\n- `delete_message` — Delete a message from a chat. [destructive]\n- `delete_messages` — Delete 1-100 messages from one Telegram chat. [destructive]\n- `delete_webhook` — Delete the configured webhook and optionally drop pending updates. [destructive]\n- `edit_chat_invite_link` — Edit an additional Telegram chat invite link created by the bot. [write]\n- `edit_message_text` — Edit the text of a previously sent message or an inline message. [write]\n- `export_chat_invite_link` — Export the primary invite link for a Telegram chat. [write]\n- `forward_message` — Forward a message from one chat to another. [write]\n- `forward_messages` — Forward 1-100 messages while preserving links and album grouping. [write]\n- `get_business_connection` — Return the current state and granted rights of a Telegram business connection.\n- `get_chat` — Return metadata for a chat the bot can access.\n- `get_chat_administrators` — Return the chat administrators visible to the bot.\n- `get_chat_member` — Return information about one chat member.\n- `get_chat_members_count` — Return the number of members in a chat.\n- `get_me` — Validate the bot token and return the bot profile from Telegram Bot API.\n- `get_updates` — Poll pending updates for the bot. Use this only when webhook delivery is disabled or for debugging.\n- `get_webhook_info` — Return the webhook status configured for the bot.\n- `pin_chat_message` — Pin a message in a Telegram chat.\n- `promote_chat_member` — Promote, update, or demote a supergroup or channel administrator.\n- `read_business_message` — Mark an incoming message as read on behalf of a connected Telegram business account.\n- `restrict_chat_member` — Set temporary or permanent permissions for one supergroup member.\n- `revoke_chat_invite_link` — Revoke a Telegram chat invite link created by the bot. [destructive]\n- `send_animation` — Send a GIF or silent MPEG-4 animation by URL or Telegram file_id. [write]\n- `send_audio` — Send an MP3 or M4A audio track by URL or Telegram file_id. [write]\n- `send_chat_action` — Show a temporary typing, upload, recording, or location activity status in a chat. [write]\n- `send_contact` — Send a phone contact to a Telegram chat. [write]\n- `send_dice` — Send an animated dice, darts, basketball, football, bowling, or slot-machine emoji. [write]\n- `send_document` — Send a document by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this provider pass. [write]\n- `send_location` — Send a map location to a chat. [write]\n- `send_media_group` — Send an album containing 2-10 photos, videos, documents, or audio items. [write]\n- `send_message` — Send a text message to a chat, group, supergroup, channel, or forum topic. [write]\n- `send_photo` — Send a photo by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this first pass. [write]\n- `send_poll` — Send a native Telegram poll to a chat. [write]\n- `send_venue` — Send a venue with coordinates, title, address, and optional place identifiers. [write]\n- `send_video` — Send an MPEG-4 video by URL or Telegram file_id. [write]\n- `send_voice` — Send a playable voice message by URL or Telegram file_id. [write]\n- `set_chat_permissions` — Set default permissions for all members of a group or supergroup. [write]\n- `set_message_reaction` — Replace the bot's chosen reaction on a Telegram message. [write]\n- `set_my_commands` — Set the bot command list exposed in Telegram clients. [write]\n- `set_webhook` — Configure a webhook endpoint for update delivery. [write]\n- `unban_chat_member` — Unban a user so they can join the chat again.\n- `unpin_all_chat_messages` — Remove all pinned messages from a Telegram chat.\n- `unpin_chat_message` — Unpin one message, or the most recently pinned message, from a Telegram chat.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Telegram Bot state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Telegram Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=telegram\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Telegram Bot homepage: https://core.telegram.org/bots\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn78y60sfta5p7kq45p63gehhd87z1wk\",\n  \"slug\": \"oo-telegram\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1789449333204\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:\n\nTelegram Bot lets agents operate Telegram Bot actions through the OOMOL `telegram` connector and `oo` CLI for reading, sending, updating, and deleting bot data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and external users use this skill to perform Telegram Bot API tasks through an OOMOL-connected account, including messaging, webhook and update management, and chat administration.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The first-time setup path includes remote installer commands that execute downloaded shell or PowerShell scripts.\n\nMitigation: Install the `oo` CLI only from a verified, pinned, or package-manager source, and review the installer before execution.\n\nRisk: Write and destructive Telegram actions can change chat state, remove messages, alter permissions, revoke invite links, or change webhook delivery.\n\nMitigation: Confirm the exact action, target chat or message, and payload with the user before running tagged write or destructive actions.\n\nRisk: Telegram action payloads may be incorrect if they are constructed from stale assumptions.\n\nMitigation: Inspect the live connector schema with `oo connector schema` before building each payload.\n\n## Reference(s):\n\n- [ClawHub Telegram Bot Skill](https://clawhub.ai/oomol/skills/oo-telegram)\n- [Telegram Bot Documentation](https://core.telegram.org/bots)\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)\n\n## Skill Output:\n\n**Output Type(s):** [shell commands, configuration, guidance, JSON]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Execution depends on the `oo` CLI, an authenticated OOMOL account, and a connected Telegram Bot account.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release evidence and SKILL.md frontmatter)\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.0.2: 3 files, 4759 bytes\n\nFiles: skill-card.md (2540b), SKILL.md (7938b), _meta.json (130b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: oo-telegram\ndescription: \"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Telegram Bot\"\n  author: \"OOMOL\"\n  version: \"1.0.2\"\n  services: [\"telegram\"]\n  icon: \"https://static.oomol.com/logo/third-party/Telegram.svg\"\n---\n\n# Telegram Bot\n\nOperate **Telegram Bot** through your OOMOL-connected account. This skill calls the `telegram` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Telegram Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"telegram\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `answer_callback_query` — Answer an inline keyboard callback query.\n- `approve_chat_join_request` — Approve a user's pending request to join a Telegram chat. [write]\n- `ban_chat_member` — Ban a user from a group, supergroup, or channel. [destructive]\n- `copy_message` — Copy one message without linking back to the original message. [write]\n- `copy_messages` — Copy 1-100 messages without links to the originals while preserving album grouping. [write]\n- `create_chat_invite_link` — Create an additional Telegram chat invite link with optional expiry or approval rules. [write]\n- `decline_chat_join_request` — Decline a user's pending request to join a Telegram chat. [write]\n- `delete_business_messages` — Delete one or more messages on behalf of a connected Telegram business account. [destructive]\n- `delete_message` — Delete a message from a chat. [destructive]\n- `delete_messages` — Delete 1-100 messages from one Telegram chat. [destructive]\n- `delete_webhook` — Delete the configured webhook and optionally drop pending updates. [destructive]\n- `edit_chat_invite_link` — Edit an additional Telegram chat invite link created by the bot. [write]\n- `edit_message_text` — Edit the text of a previously sent message or an inline message. [write]\n- `export_chat_invite_link` — Export the primary invite link for a Telegram chat. [write]\n- `forward_message` — Forward a message from one chat to another. [write]\n- `forward_messages` — Forward 1-100 messages while preserving links and album grouping. [write]\n- `get_business_connection` — Return the current state and granted rights of a Telegram business connection.\n- `get_chat` — Return metadata for a chat the bot can access.\n- `get_chat_administrators` — Return the chat administrators visible to the bot.\n- `get_chat_member` — Return information about one chat member.\n- `get_chat_members_count` — Return the number of members in a chat.\n- `get_me` — Validate the bot token and return the bot profile from Telegram Bot API.\n- `get_updates` — Poll pending updates for the bot. Use this only when webhook delivery is disabled or for debugging.\n- `get_webhook_info` — Return the webhook status configured for the bot.\n- `pin_chat_message` — Pin a message in a Telegram chat.\n- `promote_chat_member` — Promote, update, or demote a supergroup or channel administrator.\n- `read_business_message` — Mark an incoming message as read on behalf of a connected Telegram business account.\n- `restrict_chat_member` — Set temporary or permanent permissions for one supergroup member.\n- `revoke_chat_invite_link` — Revoke a Telegram chat invite link created by the bot. [destructive]\n- `send_animation` — Send a GIF or silent MPEG-4 animation by URL or Telegram file_id. [write]\n- `send_audio` — Send an MP3 or M4A audio track by URL or Telegram file_id. [write]\n- `send_chat_action` — Show a temporary typing, upload, recording, or location activity status in a chat. [write]\n- `send_contact` — Send a phone contact to a Telegram chat. [write]\n- `send_dice` — Send an animated dice, darts, basketball, football, bowling, or slot-machine emoji. [write]\n- `send_document` — Send a document by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this provider pass. [write]\n- `send_location` — Send a map location to a chat. [write]\n- `send_media_group` — Send an album containing 2-10 photos, videos, documents, or audio items. [write]\n- `send_message` — Send a text message to a chat, group, supergroup, channel, or forum topic. [write]\n- `send_photo` — Send a photo by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this first pass. [write]\n- `send_poll` — Send a native Telegram poll to a chat. [write]\n- `send_venue` — Send a venue with coordinates, title, address, and optional place identifiers. [write]\n- `send_video` — Send an MPEG-4 video by URL or Telegram file_id. [write]\n- `send_voice` — Send a playable voice message by URL or Telegram file_id. [write]\n- `set_chat_permissions` — Set default permissions for all members of a group or supergroup. [write]\n- `set_message_reaction` — Replace the bot's chosen reaction on a Telegram message. [write]\n- `set_my_commands` — Set the bot command list exposed in Telegram clients. [write]\n- `set_webhook` — Configure a webhook endpoint for update delivery. [write]\n- `unban_chat_member` — Unban a user so they can join the chat again.\n- `unpin_all_chat_messages` — Remove all pinned messages from a Telegram chat.\n- `unpin_chat_message` — Unpin one message, or the most recently pinned message, from a Telegram chat.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Telegram Bot state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Telegram Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=telegram\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Telegram Bot homepage: https://core.telegram.org/bots\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn78y60sfta5p7kq45p63gehhd87z1wk\",\n  \"slug\": \"oo-telegram\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1785200166398\n}\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nTelegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request - reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and external users with a connected Telegram Bot use this skill to inspect live connector schemas and run Telegram Bot actions through the OOMOL CLI. It supports messaging, message edits and deletion, chat administration, invite links, join requests, commands, reactions, and webhook operations. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The security evidence says several state-changing moderation actions are under-labeled as safe read-like actions. <br>\nMitigation: Require explicit user confirmation before any action that posts, deletes, moderates users, changes permissions or admin status, pins or unpins messages, marks business messages read, or changes webhook or invite settings. <br>\nRisk: The skill can operate on real Telegram groups, channels, business messages, and webhooks through a connected account. <br>\nMitigation: Review the exact action name, target chat or message, and payload before execution, especially for write and destructive actions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Telegram Bot skill page](https://clawhub.ai/oomol/skills/oo-telegram) <br>\n- [Telegram Bot documentation](https://core.telegram.org/bots) <br>\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [OOMOL CLI install guide](https://cli.oomol.com/install-guide.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Shell commands, Configuration instructions, Guidance] <br>\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses live connector schemas before execution and returns Telegram connector responses as JSON when actions run.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release metadata and skill 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>\n\nArchive v1.0.1: 3 files, 3957 bytes\n\nFiles: skill-card.md (2452b), SKILL.md (5254b), _meta.json (130b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: oo-telegram\ndescription: \"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Telegram Bot\"\n  author: \"OOMOL\"\n  version: \"1.0.1\"\n  services: [\"telegram\"]\n  icon: \"https://static.oomol.com/logo/third-party/Telegram.svg\"\n---\n\n# Telegram Bot\n\nOperate **Telegram Bot** through your OOMOL-connected account. This skill calls the `telegram` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Telegram Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"telegram\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `answer_callback_query` — Answer an inline keyboard callback query.\n- `create_chat_invite_link` — Export a new primary invite link for a chat. This maps to Telegram Bot API exportChatInviteLink. [write]\n- `delete_message` — Delete a message from a chat. [destructive]\n- `delete_webhook` — Delete the configured webhook and optionally drop pending updates. [destructive]\n- `edit_message_text` — Edit the text of a previously sent message or an inline message. [write]\n- `forward_message` — Forward a message from one chat to another. [write]\n- `get_chat` — Return metadata for a chat the bot can access.\n- `get_chat_administrators` — Return the chat administrators visible to the bot.\n- `get_chat_history` — Get chat history by polling getUpdates, filtering to one chat, and returning message-bearing updates only. This helper requires webhook delivery to be disabled.\n- `get_chat_member` — Return information about one chat member.\n- `get_chat_members_count` — Return the number of members in a chat.\n- `get_me` — Validate the bot token and return the bot profile from Telegram Bot API.\n- `get_updates` — Poll pending updates for the bot. Use this only when webhook delivery is disabled or for debugging.\n- `get_webhook_info` — Return the webhook status configured for the bot.\n- `send_document` — Send a document by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this provider pass. [write]\n- `send_location` — Send a map location to a chat. [write]\n- `send_message` — Send a text message to a chat, group, supergroup, channel, or forum topic. [write]\n- `send_photo` — Send a photo by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this first pass. [write]\n- `send_poll` — Send a native Telegram poll to a chat. [write]\n- `set_my_commands` — Set the bot command list exposed in Telegram clients. [write]\n- `set_webhook` — Configure a webhook endpoint for update delivery. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Telegram Bot state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Telegram Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=telegram\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Telegram Bot homepage: https://core.telegram.org/bots\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn78y60sfta5p7kq45p63gehhd87z1wk\",\n  \"slug\": \"oo-telegram\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1781000537239\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nTelegram Bot (core.telegram.org) enables an agent to read, create, update, and delete Telegram Bot data through an OOMOL-connected account. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[oomol](https://clawhub.ai/user/oomol) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to let an agent inspect Telegram bot state, send and manage messages, configure webhooks, and perform bot administration through approved OOMOL CLI actions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill requires a connected Telegram Bot credential managed through OOMOL. <br>\nMitigation: Install and use it only when the user trusts OOMOL with the Telegram Bot connection, and avoid login or connection setup unless the user intentionally wants this environment connected. <br>\nRisk: Confirmed write and destructive actions can post, edit, configure webhooks, create invite links, or delete bot-accessible messages. <br>\nMitigation: Review the exact action, target, and JSON payload with the user before approving write or destructive commands. <br>\nRisk: Some history and update polling behavior depends on webhook delivery being disabled. <br>\nMitigation: Check webhook status and explain the delivery requirement before using polling-based chat history or update actions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/oomol/oo-telegram) <br>\n- [Telegram Bot documentation](https://core.telegram.org/bots) <br>\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli) <br>\n- [OOMOL CLI install guide](https://cli.oomol.com/install-guide.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Shell commands, Configuration, Guidance, JSON] <br>\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Responses from connector runs are JSON objects containing data and execution metadata.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release metadata and skill 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>\n\nArchive v1.0.0: 24 files, 15600 bytes\n\nFiles: actions/answer_callback_query.md (657b), actions/create_chat_invite_link.md (852b), actions/delete_message.md (756b), actions/delete_webhook.md (793b), actions/edit_message_text.md (790b), actions/forward_message.md (759b), actions/get_chat_administrators.md (676b), actions/get_chat_history.md (751b), actions/get_chat_member.md (627b), actions/get_chat_members_count.md (660b), actions/get_chat.md (597b), actions/get_me.md (613b), actions/get_updates.md (665b), actions/get_webhook_info.md (640b), actions/send_document.md (831b), actions/send_location.md (736b), actions/send_message.md (775b), actions/send_photo.md (810b), actions/send_poll.md (724b), actions/set_my_commands.md (769b), actions/set_webhook.md (745b), skill-card.md (2494b), SKILL.md (5820b), _meta.json (130b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: oo-telegram\ndescription: \"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Telegram Bot\"\n  author: \"OOMOL\"\n  version: \"1.0.0\"\n  service: \"telegram\"\n  categories: \"Communication, Social\"\n  homepage: \"https://core.telegram.org/bots\"\n  icon: \"https://static.oomol.com/logo/third-party/Telegram.svg\"\n---\n\n# Telegram Bot\n\nOperate **Telegram Bot** through your OOMOL-connected account. This skill calls the `telegram` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Communication, Social. Exposes 21 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Telegram Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"telegram\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`answer_callback_query`](actions/answer_callback_query.md) — Answer an inline keyboard callback query.\n- [`create_chat_invite_link`](actions/create_chat_invite_link.md) — Export a new primary invite link for a chat. This maps to Telegram Bot API exportChatInviteLink.\n- [`delete_message`](actions/delete_message.md) — Delete a message from a chat.\n- [`delete_webhook`](actions/delete_webhook.md) — Delete the configured webhook and optionally drop pending updates.\n- [`edit_message_text`](actions/edit_message_text.md) — Edit the text of a previously sent message or an inline message.\n- [`forward_message`](actions/forward_message.md) — Forward a message from one chat to another.\n- [`get_chat`](actions/get_chat.md) — Return metadata for a chat the bot can access.\n- [`get_chat_administrators`](actions/get_chat_administrators.md) — Return the chat administrators visible to the bot.\n- [`get_chat_history`](actions/get_chat_history.md) — Get chat history by polling getUpdates, filtering to one chat, and returning message-bearing updates only. This helper requires webhook delivery to be disabled.\n- [`get_chat_member`](actions/get_chat_member.md) — Return information about one chat member.\n- [`get_chat_members_count`](actions/get_chat_members_count.md) — Return the number of members in a chat.\n- [`get_me`](actions/get_me.md) — Validate the bot token and return the bot profile from Telegram Bot API.\n- [`get_updates`](actions/get_updates.md) — Poll pending updates for the bot. Use this only when webhook delivery is disabled or for debugging.\n- [`get_webhook_info`](actions/get_webhook_info.md) — Return the webhook status configured for the bot.\n- [`send_document`](actions/send_document.md) — Send a document by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this provider pass.\n- [`send_location`](actions/send_location.md) — Send a map location to a chat.\n- [`send_message`](actions/send_message.md) — Send a text message to a chat, group, supergroup, channel, or forum topic.\n- [`send_photo`](actions/send_photo.md) — Send a photo by URL or existing Telegram file_id. Multipart uploads are intentionally out of scope for this first pass.\n- [`send_poll`](actions/send_poll.md) — Send a native Telegram poll to a chat.\n- [`set_my_commands`](actions/set_my_commands.md) — Set the bot command list exposed in Telegram clients.\n- [`set_webhook`](actions/set_webhook.md) — Configure a webhook endpoint for update delivery.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Telegram Bot state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):\n\n  ```bash\n  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux\n  ```\n\n  ```powershell\n  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell\n  ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n  ```bash\n  oo auth login\n  ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Telegram Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n  ```text\n  https://console.oomol.com/app-connections?provider=telegram\n  ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Telegram Bot homepage: https://core.telegram.org/bots\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn78y60sfta5p7kq45p63gehhd87z1wk\",\n  \"slug\": \"oo-telegram\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1780571239842\n}\n\nFile v1.0.0:actions/answer_callback_query.md\n\n# Telegram Bot · `answer_callback_query`\n\nAnswer an inline keyboard callback query.\n\n- **Service**: `telegram`\n- **Action**: `answer_callback_query`\n- **Action id**: `telegram.answer_callback_query`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"answer_callback_query\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"answer_callback_query\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/create_chat_invite_link.md\n\n# Telegram Bot · `create_chat_invite_link`\n\nExport a new primary invite link for a chat. This maps to Telegram Bot API exportChatInviteLink.\n\n- **Service**: `telegram`\n- **Action**: `create_chat_invite_link`\n- **Action id**: `telegram.create_chat_invite_link`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"create_chat_invite_link\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"create_chat_invite_link\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Telegram Bot state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/delete_message.md\n\n# Telegram Bot · `delete_message`\n\nDelete a message from a chat.\n\n- **Service**: `telegram`\n- **Action**: `delete_message`\n- **Action id**: `telegram.delete_message`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"delete_message\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"delete_message\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Destructive action.** This removes or overwrites Telegram Bot data. Always confirm the target and get explicit user approval before running.\n\nFile v1.0.0:actions/delete_webhook.md\n\n# Telegram Bot · `delete_webhook`\n\nDelete the configured webhook and optionally drop pending updates.\n\n- **Service**: `telegram`\n- **Action**: `delete_webhook`\n- **Action id**: `telegram.delete_webhook`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"delete_webhook\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"delete_webhook\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Destructive action.** This removes or overwrites Telegram Bot data. Always confirm the target and get explicit user approval before running.\n\nFile v1.0.0:actions/edit_message_text.md\n\n# Telegram Bot · `edit_message_text`\n\nEdit the text of a previously sent message or an inline message.\n\n- **Service**: `telegram`\n- **Action**: `edit_message_text`\n- **Action id**: `telegram.edit_message_text`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"edit_message_text\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"edit_message_text\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Telegram Bot state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/forward_message.md\n\n# Telegram Bot · `forward_message`\n\nForward a message from one chat to another.\n\n- **Service**: `telegram`\n- **Action**: `forward_message`\n- **Action id**: `telegram.forward_message`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"forward_message\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"forward_message\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Telegram Bot state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/get_chat_administrators.md\n\n# Telegram Bot · `get_chat_administrators`\n\nReturn the chat administrators visible to the bot.\n\n- **Service**: `telegram`\n- **Action**: `get_chat_administrators`\n- **Action id**: `telegram.get_chat_administrators`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"get_chat_administrators\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"get_chat_administrators\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_chat_history.md\n\n# Telegram Bot · `get_chat_history`\n\nGet chat history by polling getUpdates, filtering to one chat, and returning message-bearing updates only. This helper requires webhook delivery to be disabled.\n\n- **Service**: `telegram`\n- **Action**: `get_chat_history`\n- **Action id**: `telegram.get_chat_history`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"get_chat_history\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"get_chat_history\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_chat_member.md\n\n# Telegram Bot · `get_chat_member`\n\nReturn information about one chat member.\n\n- **Service**: `telegram`\n- **Action**: `get_chat_member`\n- **Action id**: `telegram.get_chat_member`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"get_chat_member\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"get_chat_member\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_chat_members_count.md\n\n# Telegram Bot · `get_chat_members_count`\n\nReturn the number of members in a chat.\n\n- **Service**: `telegram`\n- **Action**: `get_chat_members_count`\n- **Action id**: `telegram.get_chat_members_count`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"telegram\" --action \"get_chat_members_count\"\n```\n\n## Run\n\n```bash\noo connector run \"telegram\" --action \"get_chat_members_count\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.","readmeExcerpt":"Skill: Telegram Bot Owner: oomol Summary: Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly. Tags: latest:1.0.5 Version history: v1.0.5 | 2026-09-20T03:32:10.467Z | user - Operates Telegram Bot accounts through the OOMOL telegram connector and oo CLI, ","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"oo connector schema \"telegram\" --action \"<action_name>\""},{"language":"bash","snippet":"oo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux"},{"language":"powershell","snippet":"irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell"},{"language":"bash","snippet":"oo auth login"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: oo-telegram\ndescription: \"Telegram Bot (core.telegram.org). Use this skill for ANY Telegram Bot request — reading, creating, updating, and deleting data. Whenever a task involves Telegram Bot, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n  title: \"Telegram Bot\"\n  author: \"OOMOL\"\n  version: \"1.0.5\"\n  services: [\"telegram\"]\n  icon: \"https://static.oomol.com/logo/third-party/Telegram.svg\"\n---\n\n# Telegram Bot\n\nOperate **Telegram Bot** through your OOMOL-connected account. This skill calls the `telegram` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Telegram Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"telegram\" --action \"<action_name>\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"telegram\" --action \"<action_name>\" --data '<json>' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `answer_callback_query` — Answer an inline keyboard callback query.\n- `approve_chat_join_request` — Approve a user's pending request to join a Telegram chat. [write]\n- `ban_chat_member` — Ban a user from a group, supergroup, or channel. [destructive]\n- `copy_message` — Copy one message without linking back to the original message. [write]\n- `copy_messages` — Copy 1-100 messages without links to the originals while preserving album grouping. [write]\n- `create_chat_invite_link` — Create an additional Telegram chat invite link with optional expiry or approval rules. [write]\n- `decline_chat_join_request` — Decline a user's pending request to join a Telegram chat. [destructive]\n- `delete_business_messages` — Delete one or more messages on behalf of a connected Telegram business account. [destructive]\n- `delete_message` — Delete a message from a chat. [destructive]\n- `delete_messages` — Delete 1-100 messages from one Telegram chat. [destructive]\n- `delete_webhook` — Delete the configured webhook and optionally drop pending updates. [destructive]\n- `edit_chat_invite_link` — Edit an additional Telegram chat invite link created by the bot. [write]\n- `"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn78y60sfta5p7kq45p63gehhd87z1wk\",\n  \"slug\": \"oo-telegram\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1789875130467\n}"},{"path":"skill-card.md","content":"## Description:\n\nOperates Telegram Bot accounts through OOMOL's Telegram connector and oo CLI for reading bot data, sending messages, and administering chats.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill to manage Telegram Bot workflows from an agent, including reading bot and chat data, sending messages or media, managing webhooks, and administering chat membership.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup can run a remote installer script on the user's machine.\n\nMitigation: Review the OOMOL CLI installation path before installing and prefer an official package or a downloaded installer that can be inspected and verified.\n\nRisk: Telegram Bot actions can send messages, delete content, ban or promote users, configure webhooks, or act through business-message permissions.\n\nMitigation: Connect only a Telegram Bot account whose permissions match the intended delegation, and confirm the exact target, payload, and effect before write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-telegram)\n- [Telegram Bot documentation](https://core.telegram.org/bots)\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)\n- [OOMOL CLI install guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with bash commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Connector executions produce JSON responses with data and execution metadata.]\n\n## Skill Version(s):\n\n1.0.5 (source: frontmatter and release evidence)\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":1486,"uniquenessScore":42,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:50:25.685Z","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-11T16:50:25.685Z","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-11T20:56:58.418Z","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"}]}}}