Hiring Pipeline

Track candidates and hiring conversations in Telegram with stage tags, summaries, and follow-up tasks. Use when the user wants to manage recruiting or candidate follow-ups from Telegram.

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.
Scoped Agent Access tokens that can be created, limited, and revoked.
Team permissions, approval policies, audit logs, and durable cloud jobs.
No local Telegram worker, database, or MCP runtime to operate.

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

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

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