194 件 ・ 関連度順
概要と使いどころ
MTProto-over-WebSocket tunnel for Telegram: DC classification, obfuscated2 detection, TLS backend choice, and the relay loop. Use when touching Telegram DC routing, MTProto classification, or ripdpi-ws-tunnel.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to post or schedule to a Telegram channel or group through Publora, using a bot. Covers Telegram markdown, silent delivery, link previews and forward protection. Bot API caps media captions at 1,024 characters and videos at 50 MB. Not for other platforms (each has its own skill).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building, debugging, or documenting Telegram bot polling flows that need safe agent routing, state tracking, and final-only replies without webhooks.
日本語の概要は準備中です。原文の説明を表示しています。
Check Telegram bot configuration and guide setup if anything is missing.
日本語の概要は準備中です。原文の説明を表示しています。
Start Telegram monitoring. Auto-enables voice pipeline if ElevenLabs or OpenAI TTS keys are detected.
日本語の概要は準備中です。原文の説明を表示しています。
Stop the Telegram channel daemon.
日本語の概要は準備中です。原文の説明を表示しています。
Dark web intelligence collection methodology — vendor-first access posture, sourced reference lists for 35+ underground forums and 30+ Telegram channels, OPSEC primer, passive-monitoring strategy, and bundled Python CLIs for onion-indexer search, Telegram channel monitoring, and local keyword matching. Use when the user wants to design or run dark-web collection, build a selector list, pick a vendor, or set up monitoring infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Reverse engineer and security-test Telegram bots — API analysis, callback interception, exploit discovery, and vulnerability documentation
日本語の概要は準備中です。原文の説明を表示しています。
Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).
日本語の概要は準備中です。原文の説明を表示しています。
Telegram Bot API の long-polling を cloud routine 上で常駐させ、認可済みチャットからのメッセージに秘書エージェント（SecretaryRole）が即応する対話チャネル。Webhook 不可な cloud routine 環境制約を long-polling + /goal deadline 駆動ループで回避する。
Fold a fresh export of an already-imported Telegram chat into a vault, adding only the new messages. Idempotent by message id, so it never duplicates. Triggers: "re-import <chat>", "update the telegram import".
日本語の概要は準備中です。原文の説明を表示しています。
ПОДКЛЮЧИТЬ Telegram на ЭТОЙ машине — оба стека сразу: Telethon-рельса (роботы, 0 LLM) и MCP (живые сессии). Триггеры «/tg-connect», «/tg-login», «подключи телегу», «подключи телеграм на этой машине», «залогинь телегу», «телега отвалилась», «AuthKeyDuplicated», «перелогинь аккаунт <имя>», «настрой telethon и mcp», «connect telegram», «relogin telegram»
日本語の概要は準備中です。原文の説明を表示しています。
Operating manual for Telegram over its MCP connector and roughly 115 tools: how to find a chat by title, the tool inventory grouped by job, resolving chat ids, auto-transcribing voice notes, and the connector gotchas (pinned-first ordering, big-page crashes, reload after reconnect, untrusted fields, always passing an explicit account). Load before any non-trivial Telegram work.
日本語の概要は準備中です。原文の説明を表示しています。
Run Telegram as a scoped auto-reply assistant grounded in the owner's vault and written in their voice: whitelisted low-stakes chats are answered autonomously, while anything financial, committing, sensitive or from an unknown contact becomes a draft for the owner. Triggers: "handle my telegram", "reply for me in <chat>", or a new message in a whitelisted chat.
日本語の概要は準備中です。原文の説明を表示しています。
Unified chat inbox (Busabase App-in-Skill) aggregating WhatsApp, Discord, Slack, and Telegram messages into one place with a reply queue. Use when the user invokes $kelly-messenger or /kelly-messenger, wants a unified inbox, chat aggregation, to read WhatsApp/Discord/Slack/Telegram messages in one place, review unanswered conversations, queue or approve replies, run connector sync, or manage the outgoing reply queue.
日本語の概要は準備中です。原文の説明を表示しています。
Interactively create, install, activate, and verify custom claude-mem modes, including domain-specific observation types, concept tags, optional Telegram alerts, bot setup, worker restart, and startup-context verification. Use this whenever someone asks to customize what claude-mem remembers, create or change a mode, track domain-specific notes, add observation types or tags, or send Telegram notifications for particular memories—even if they do not use the word "mode."
日本語の概要は準備中です。原文の説明を表示しています。
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
日本語の概要は準備中です。原文の説明を表示しています。
Add Telegram channel integration via Chat SDK.
日本語の概要は準備中です。原文の説明を表示しています。
Telegram 生态开发全栈指南 - 涵盖 Bot API、Mini Apps (Web Apps)、MTProto 客户端开发。包括消息处理、支付、内联模式、Webhook、认证、存储、传感器 API 等完整开发资源。
日本語の概要は準備中です。原文の説明を表示しています。
Build multi-platform chat bots with Chat SDK (`chat` npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI streaming, (3) Set up webhook routes or multi-adapter bots, (4) Send rich cards or streamed AI responses to chat platforms, (5) Build or maintain a custom adapter or state adapter. Triggers on "chat sdk", "chat bot", "slack bot", "teams bot", "google chat bot", "discord bot", "telegram bot", "whatsapp bot", "@chat-adapter", "@chat-adapter/state-", "custom adapter", "state adapter", "build adapter", and building bots that work across multiple chat platforms.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Turns one-shot external recon into a continuous monitoring program. Covers the scheduled re-scan-and-diff loop (baseline snapshot -> interval sleep -> re-scan -> asset/finding delta -> threshold-gated webhook alert), the scan-to-scan diff engine (new/removed/changed assets by a tracked-attribute table, new/resolved findings by a stable cross-scan fingerprint), adversary CTI / chatter monitoring across six public feeds (ransomwatch, ransomware.live, HackerNews Algolia search, Reddit security-subreddit RSS, GitHub Gist code-search, public Telegram channel scraping) with a source-kind-aware severity engine (leak-site/forum/telegram/paste tiers, CRITICAL through INFO), literal/glob/regex watchlist pattern matching, full-corpus capture with retroactive rescan on new watchlist entries, infrastructure-tracking-over-time discipline (certificate-transparency, passive-DNS, port/service, and typosquat re-enumeration cadence, and what a genuine 'perimeter drift' event looks like in the diff output), a five-state finding-lifecycle state machine (open/triaged/risk_accepted/resolved/false_positive) with per-severity SLA and fingerprint-based cross-scan dedup and auto-resolve/reopen rules, the alert-fatigue trap where a lifecycle-unaware rule re-fires on an already-accepted finding, a durable retry/backoff alert-outbox pattern ('queued is not delivered'), and copy-paste bash-cron plus PowerShell-Scheduled-Task recipes for a re-scan+diff loop with the Slack-compatible webhook payload shape. Passive OSINT and analysis only -- no new active-intrusion technique. Use when setting up ongoing monitoring for a retainer or MSSP engagement, tuning alert thresholds to avoid fatigue, triaging a finding's lifecycle status, investigating adversary chatter about a brand, building a 'what changed on the perimeter since last week' report, or deciding whether a persisting finding should re-alert.
日本語の概要は準備中です。原文の説明を表示しています。
AI DevKit · Connect the current agent session to an available Telegram channel bridge.
日本語の概要は準備中です。原文の説明を表示しています。
Telegram 生态开发全栈指南 - 涵盖 Bot API、Mini Apps (Web Apps)、MTProto 客户端开发。包括消息处理、支付、内联模式、Webhook、认证、存储、传感器 API 等完整开发资源。
日本語の概要は準備中です。原文の説明を表示しています。