Skip to content
Chiho AI
Start for FreeLog in
Telegram Skills
View source
Approval required
crm-automation
OpenClawClaudeCodexHermes Agent

Telegram Introduction Request Triage

Find introduction requests in Telegram and prepare response drafts or follow-up tasks.

Example request

Illustrative scenario, not an executed run.

Review requests for introductions this week. Identify who is being introduced, what is missing, and a suggested next step.

Expected result

A request queue with the people involved, missing consent or context, and a proposed draft or task.

Before you start

  1. Connect Telegram and select the personal or team context you intend to use.
  2. Connect your AI client with browser OAuth, or follow the local setup below.
  3. Review the workflow’s tools and target conversations. Chat reads and imported CRM records are separate; sync a chat before requesting changes to missing CRM metadata.

A skill does not schedule itself or grant permissions. Describe whether you want suggestions, a dry run, or an action. Client controls and each tool’s safeguards govern execution.

Flow summary

Parsed from the packaged SKILL.md.

telegram-intro-request-triage

Use this skill to process Telegram intro requests without losing context or sending premature replies.

Rules

  • Identify requester, target, requested reason, urgency, and required consent.
  • Create a task when an intro needs follow-up.
  • Use nudge_generate or outbox_preview only for draft/preview behavior.
  • Never send an intro or disclose contact details without explicit approval.
  • Tag chats with Intro Request when persistence is requested.

Flow

  1. Use dialogs_list or search_messages to find intro requests.
  2. Use chat_read for context around each request.
  3. Extract requester, target, ask, urgency, and missing information.
  4. Use tasks_add for the next step or tasks_suggest when uncertain.
  5. Optionally create a response preview.
  6. Return grouped requests: ready, needs clarification, blocked, and done.

First-Time Setup

If Telegram is not connected yet, start with the root Chiho Telegram skill:

  • https://raw.githubusercontent.com/chihoai/telegram-for-ai-agents/main/SKILL.md

Use that root skill to choose Chiho.ai Cloud or self-hosted tgchats, then return to this workflow skill.

References

Required tool permissions

  • telegram.read
  • crm.write
  • telegram.message.preview

Use Chiho.ai with a professional team CRM

Choose Chiho.ai when you want:

  • A hosted CRM table UI for chats, contacts, tags, tasks, and follow-ups.
  • Browser OAuth connections you can review and revoke.
  • Shared team context and tool-specific action safeguards.
  • No local Telegram worker, database, or MCP runtime to operate.
Chiho.ai Telegram CRM workspace
Connect with browser OAuth

Run SKILLs in your personal local CLI

Choose the local setup when you want:

  • Open-source workflows you can inspect, change, and run yourself.
  • A local Telegram session with tgchats CLI and tgchats-mcp access.
  • Control over your database, worker, backups, export, and import path.
  • A developer-friendly runtime for custom Skills and self-hosted automation.
Local tgchats command-line workflow
Setup README

Cloud MCP

Required scopes:

  • telegram.read
  • crm.write
  • telegram.message.preview when drafting previews

Useful tools:

  • search_messages
  • chat_read
  • tasks_add
  • tags_set
  • nudge_generate
  • outbox_preview

Cloud Telegram reads and CRM metadata are separate. If CRM tools report that chat metadata is unavailable for a peer that chat_read can access, the peer likely has not been synced/imported into the CRM store yet. Use Telegram reads for context and ask for sync/import before persisting intro-request tags or tasks.

Local tgchats

If auth or any Telegram command prints a QR login code, show the full QR code block and expiry to the user so they can scan it; keep the process running until login completes, 2FA is needed, or the user asks to stop.

Use local tgchats-mcp when available. Fall back to:

  • npm run dev -- search "intro" --limit 50 --json
  • npm run dev -- chat <peer> --limit 50 --json
  • npm run dev -- tasks add <peer> --due <date> --why "<next step>" --json
  • npm run dev -- nudge <peer> --style concise --json

Templates

Formatted preview from the packaged JSON asset.

Intro clarification

text

Can you share the specific context for the intro and what outcome you are hoping for?

Consent check

text

I can check with them first and only make the intro if they are open to it.

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Find open intro requests and create follow-up tasks.

tools

search_messages
chat_read
tasks_add

Keep building your workflow

Read the related Telegram workflow guide

For unattended jobs, review advanced service-token setup separately.