「telegram」の検索結果

Full-text keyword search across every conversation at once (Telegram, Facebook, ChatGPT, Claude, notes, transcripts) over a local BM25/FTS5 catalog: instant, zero tokens, with snippets and chat-title hits. The exact-words lane, complementary to semantic search. Triggers: "/search <words>", "where did I write about <X>".

日本語の概要は準備中です。原文の説明を表示しています。

Единый вход публикации контент-фабрики на все живые площадки: Facebook, X, Telegram-каналы, Threads, Instagram. Публикую САМ. Триггеры: /social-daily, /autopost, /postall, постить везде, разгреби очередь постинга, прогони автопостинг, постим следующий, поставь в отложку, что в очереди постинга, next social post. НЕ путать: /fb-post /x-post /tg-post = точечная дверь под один пост.

日本語の概要は準備中です。原文の説明を表示しています。

- Deep-dive a subject's social media presence — profile metadata, follower and mutual network, content analysis, and posting-time pattern of life across Instagram, Facebook, X/Twitter, TikTok, LinkedIn, Reddit, Telegram and… Use when profiling a social account, mapping someone's associates, inferring a subject's timezone or routine from their posts, or archiving a profile before it is deleted

日本語の概要は準備中です。原文の説明を表示しています。

Pull fresh messages from a set of health-related Telegram chats (medicine, supplements, longevity, fasting) into an Obsidian vault. Incremental and idempotent by message id, and the manual counterpart of the weekly job. Triggers: "/health-sync", "pull the health chats".

日本語の概要は準備中です。原文の説明を表示しています。

Mine any Telegram channel or chat for signal in one command: incremental zero-token scrape, deterministic detector shortlist, LLM judge for what is genuinely valuable to this owner, then linked vault notes, a database row, a map-of-content entry and reindex. Triggers: "/mine-channel <@channel|id>", "alpha from <channel>".

日本語の概要は準備中です。原文の説明を表示しています。

Import any source into an Obsidian vault as well-linked atomic notes: social posts, Telegram HTML exports, ChatGPT JSON, voice-note transcripts, WhatsApp exports, Apple Notes, Notion dumps, pasted text, articles. Handles structure, frontmatter, provenance, dedup against existing notes and a closing RAG reindex. Triggers: "/obsidian-ingest", "import this into the vault", "file this".

日本語の概要は準備中です。原文の説明を表示しています。

- Find leaked or mentioned selectors circulating in pastes, leak forums, Telegram channels and dump markets, and judge whether a claimed leak is genuine or a recycled combolist. Use when checking whether a name, email, domain or credential is circulating, verifying a breach claim made against your organisation, or setting up ongoing leak monitoring

日本語の概要は準備中です。原文の説明を表示しています。

Pull fresh follow-up call notes from a dedicated Telegram group into the CRM layer of a vault. Incremental and idempotent by message id, safe to re-run, and the manual counterpart of the weekly scheduled job. Triggers: "/faaa-sync", "pull the follow-up notes".

日本語の概要は準備中です。原文の説明を表示しています。

Send and read messages between machines in a fleet over a shared Telegram group, so cross-machine coordination survives a file-sync outage and humans can watch the machines talk. A synced folder stays as the fallback for oversized payloads. Triggers: "/bus", "post to the bus", "check the bus", "tell the other machines".

日本語の概要は準備中です。原文の説明を表示しています。

Find a Telegram chat, group or channel by name and return its numeric id and t.me link from a local index, with no live crawl. Also answers which groups you share with a person or company. This is the chat lane, not people search. Triggers: "/chat <query>", "find the <X> chat", "chat id for <X>".

日本語の概要は準備中です。原文の説明を表示しています。

Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".

日本語の概要は準備中です。原文の説明を表示しています。

Use when: reviewing or producing any external-facing prose — ADRs, proposals, GitHub comments, Telegram messages, cover letters, client drafts, or planner-mode wording. Removes AI-tell patterns and raises writing quality before output leaves the team.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive guide for installing, configuring, operating, and troubleshooting OpenClaw — a self-hosted, multi-channel AI agent gateway. Use when the user asks about OpenClaw setup, configuration, channel management (WhatsApp/Telegram/Discord/Slack/iMessage/etc.), model provider setup, Gateway operations, multi-agent routing, security hardening, troubleshooting, or any maintenance task related to their local OpenClaw installation. Also use when encountering errors from `openclaw` CLI commands or the Gateway daemon.

日本語の概要は準備中です。原文の説明を表示しています。

Create a new Hydra agent with full configuration. Use when user wants to add an agent, new agent, create agent, or set up another agent. Walks through persona, mounts, Telegram, model, and secrets.

日本語の概要は準備中です。原文の説明を表示しています。

Guide for adult content payment processor selection, merchant account application, compliance, webhook integration, and fallback strategies (CCBill, SegPay, AllSecure, Epoch, Telegram Stars, crypto)

日本語の概要は準備中です。原文の説明を表示しています。

Find nearby places (restaurants, cafes, bars, pharmacies, etc.) using OpenStreetMap. Works with coordinates, addresses, cities, zip codes, or Telegram location pins. No API keys needed.

日本語の概要は準備中です。原文の説明を表示しています。

Tracks competitors weekly across 6 signals: pricing page diffs, homepage positioning changes, blog/RSS posts, job postings (hiring as strategy signal), GitHub star velocity and releases, and daily critical-change alerts for pricing or funding keywords. Delivers a structured digest to Slack, Telegram, WhatsApp, or Discord every Monday. Fires same-day alerts for critical changes. Use when asked to "add competitor", "track competitor", "competitor digest", "what changed at [company]", "competitor report", "monitor [company]", "who is [company] hiring", "did [company] change pricing".

日本語の概要は準備中です。原文の説明を表示しています。

Proactive monitoring of Aave V3 borrow positions with liquidation alerts. Queries user collateral, debt, and health factor across chains (Ethereum, Polygon, Arbitrum, etc.). Sends urgent alerts to Telegram/Discord/Slack when health factor drops below configurable thresholds (critical at 1.05, warning at 1.2). Use when you need continuous monitoring of Aave positions, want alerts before liquidation risk occurs, or need periodic summaries of your borrowing health.

日本語の概要は準備中です。原文の説明を表示しています。

Complete community building, engagement, and monetization system. From zero to thriving community — launch strategy, member engagement loops, content programming, moderation frameworks, growth tactics, monetization models, and health metrics. Works for Discord, Slack, Telegram, Circle, forums, or any platform.

日本語の概要は準備中です。原文の説明を表示しています。

Search and browse Pinterest pins, get pin details, and send actual images to the user via Telegram/messaging. Use when the user wants to find inspiration, search for images/ideas, or browse Pinterest content. Sends images directly, not just links.

日本語の概要は準備中です。原文の説明を表示しています。

Promote Doppel world builds across social platforms. Use when the agent wants to share builds on Twitter/X, Farcaster, Telegram, or Moltbook to drive observers, grow reputation, and recruit collaborators.

日本語の概要は準備中です。原文の説明を表示しています。

End-of-day response check and pipeline update. Run at 6 PM via cron. Checks all channels for replies via Chrome DevTools MCP + Zoho MCP, updates lead statuses, pauses cadence for responded leads, sends EOD report via Telegram.

日本語の概要は準備中です。原文の説明を表示しています。

Determines all follow-up actions due today across the 10-day outreach cadence. Generates content and delivers automatically via Chrome DevTools MCP. Sends Telegram confirmation after completion.

日本語の概要は準備中です。原文の説明を表示しています。

Architects the encryption, codec/transport, and premium-feature layer of a group video-calling product, on top of an already-chosen SFU topology. Covers E2EE patterns (Zoom leader-fan-out, Signal pairwise-fan-out, MLS/TreeKEM as in Discord's DAVE, Telegram's ledger consensus), the SFrame (RFC 9605) + WebRTC Insertable Streams mechanism letting an SFU relay encrypted frames it can't read, codec/transport choice (AV1/VP9 SVC vs. simulcast, Opus, congestion control, Media-over-QUIC, WHIP/WHEP), and which "premium" features (virtual backgrounds, live captions, recording, breakout rooms, spatial audio) survive E2EE vs. structurally can't. Use when adding E2EE to an SFU-based call, choosing a 2026 codec/SVC strategy, or deciding which features to disable under E2EE mode. NOT for call topology/platform choice (see webrtc-adhoc-video-chat, which this composes with). NOT for one-way broadcast (see managed-video-streaming-pipeline). NOT for the DM/group-chat text backend (see realtime-messaging-backend-architecture).

日本語の概要は準備中です。原文の説明を表示しています。