Review tool permissions

crm-automation

OpenClawClaudeCodexHermes Agent

Telegram Hiring Conversation Tracker

Organize candidate conversations with stage tags, summaries, and follow-up tasks.

Example request

Illustrative scenario, not an executed run.

Organize the candidate chats I selected by the interview stage explicitly recorded in each conversation. Suggest next tasks.

Expected result

A proposed stage and follow-up queue based on recorded hiring conversations, with ambiguous stages left for review.

Before you start

Connect Telegram and select the personal or team context you intend to use.
Connect your AI client with browser OAuth, or follow the local setup below.
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-hiring-pipeline

Use this skill to organize Telegram recruiting conversations into a hiring pipeline.

Rules

Use candidate-stage tags only from conversation evidence.
Avoid sensitive or protected-class inferences.
Create tasks for interview scheduling, feedback, or next steps.
Do not send candidate messages directly.

Flow

Find candidate chats by search, tags, or recent dialogs.
Read recent context.
Suggest stage tags and follow-up tasks.
Refresh summaries for active candidates.
Return pipeline status and overdue next steps.

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

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.

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.

Setup README

Cloud MCP

Required scopes:

telegram.read
crm.write

Useful tools:

search_messages
chat_read
tags_suggest
tags_set
tasks_suggest
tasks_add
summary_refresh

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 candidate 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 "interview" --limit 50 --json
npm run dev -- chat <peer> --limit 50 --json
npm run dev -- tags suggest <peer> --json
npm run dev -- tasks suggest <peer> --json
npm run dev -- tasks add <peer> --due <date> --why "<hiring next step>" --json

Templates

Formatted preview from the packaged JSON asset.

Hiring pipeline stages

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Show candidates I need to follow up with from Telegram.

tools

search_messages

chat_read

tasks_suggest

Keep building your workflow

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