sergei-mikhailov-tg-channel-reader
Read posts and comments from Telegram channels via MTProto (Pyrogram or Telethon). Fetch recent messages and discussion replies from public or private channels by time window.
- License 许可
- MIT
- 最近更新
- 2026-06-18
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- sergei-mikhailov-tg-channel-reader
- metadata
- { "openclaw": { "emoji": "📡", "requires": { "env": [ "TG_API_ID", "TG_API_HASH" ], "bins": [ "tg-reader", "tg-reader-check" ] }, "primaryEnv": "TG_API_HASH" } }
- description
- Read posts and comments from Telegram channels via MTProto (Pyrogram or Telethon). Fetch recent messages and discussion replies from public or private channels by time window.
02 资源文件 17
- 其他.gitignore125 B
- 参考文档CHANGELOG.md21.9 KB
- 参考文档CLAUDE.md4.6 KB
- 脚本debug_auth.py2.2 KB
- 参考文档DISCLAIMER.md2.3 KB
- 许可证LICENSE1.0 KB
- 脚本reader_telethon.py26.3 KB
- 脚本reader.py27.8 KB
- 参考文档README_TELETHON.md3.2 KB
- 参考文档README.md8.5 KB
- 脚本setup-tg-reader.sh8.7 KB
- 脚本setup.py806 B
- 脚本test_session.py1.2 KB
- 参考文档TESTING_GUIDE.md3.6 KB
- 脚本tg_check.py13.0 KB
- 脚本tg_reader_unified.py1.5 KB
- 脚本tg_state.py3.2 KB
03 SKILL.md 正文
tg-channel-reader
Read posts and comments from Telegram channels using MTProto (Pyrogram or Telethon). Works with any public channel and private channels the user is subscribed to. Supports fetching discussion replies (comments) for individual posts.
Security notice: This skill requires
TG_API_IDandTG_API_HASHfrom my.telegram.org. The session file grants full Telegram account access — store it securely and never share it.
Exec Approvals
Just installed via
clawhub install? Complete Setup & Installation (below) first — the skill needspip install, credentials, and a session file before exec approvals matter.
OpenClaw blocks unknown CLI commands by default. The user must approve tg-reader commands before they can run. If the command hangs or the user says nothing is happening — exec approval is likely pending.
Quick setup (recommended)
Run from the skill directory — checks prerequisites, installs pip packages if needed, and prints the approval commands to run:
cd ~/.openclaw/workspace/skills/sergei-mikhailov-tg-channel-reader
bash setup-tg-reader.sh
Manual CLI approval
openclaw approvals allowlist add --gateway "$(which tg-reader)"
openclaw approvals allowlist add --gateway "$(which tg-reader-check)"
openclaw approvals allowlist add --gateway "$(which tg-reader-telethon)"
Alternative: approve on first use
- Control UI — open
http://localhost:18789/, find the pending approval fortg-reader, click "Always allow". Docs - Messenger (Telegram, Slack, Discord) — the bot sends an approval request with an
<id>. Reply:/approve <id> allow-always. Other options:allow-once,deny.
The approval prompt appears in the Control UI or as a bot message — not in the agent's conversation. This is a common source of confusion.
When to Use
- User asks to "check", "read", or "monitor" a Telegram channel
- Wants a digest or summary of recent posts
- Asks "what's new in @channel" or "summarize last 24h from @channel"
- Wants to track or compare multiple channels
- Wants channel info (title, description, subscribers) — use
tg-reader info
Quick Start
# 1. Run pre-flight diagnostic (fast, no Telegram connection)
tg-reader-check
# 2. Get channel info
tg-reader info @channel_name
# 3. Fetch recent posts
tg-reader fetch @channel_name --since 24h
tg-reader: command not found? Runbash setup-tg-reader.shfrom the skill directory (it will install the package), or manually:cd ~/.openclaw/workspace/skills/sergei-mikhailov-tg-channel-reader && pip install .
Commands
tg-reader-check — Pre-flight Diagnostic
Always run before fetching. Fast offline check — no Telegram connection needed.
tg-reader-check
tg-reader-check --config-file /path/to/config.json
tg-reader-check --session-file /path/to/session
Returns JSON with "status": "ok" or "status": "error" plus a problems array.
Verifies:
- Credentials available (env vars or
~/.tg-reader.json) - Session file exists on disk (with size, modification date)
- At least one MTProto backend installed (Pyrogram or Telethon)
- Detects stale sessions (config points to older file while a newer one exists)
tg-reader info — Channel Info
tg-reader info @channel_name
Returns title, description, subscriber count, and link.
tg-reader fetch — Read Posts
# Last 24 hours (default)
tg-reader fetch @channel_name --since 24h
# Last 7 days, up to 200 posts
tg-reader fetch @channel_name --since 7d --limit 200
# Multiple channels (fetched sequentially with 10s delay between each)
tg-reader fetch @channel1 @channel2 @channel3 --since 24h
# Custom delay between channels (seconds)
tg-reader fetch @channel1 @channel2 @channel3 --since 24h --delay 5
# Fetch posts with comments (single channel only, limit auto-drops to 30)
tg-reader fetch @channel_name --since 7d --comments
# More comments per post, custom delay between posts
tg-reader fetch @channel_name --since 24h --comments --comment-limit 20 --comment-delay 5
# Skip posts without text (media-only, no caption)
tg-reader fetch @channel_name --since 24h --text-only
# Human-readable output
tg-reader fetch @channel_name --since 24h --format text
# Write output to file instead of stdout (saves tokens)
tg-reader fetch @channel_name --since 24h --output
tg-reader fetch @channel_name --since 24h --comments --output comments.json
# Use Telethon instead of Pyrogram (one-time)
tg-reader fetch @channel_name --since 24h --telethon
# Read unread mode — only fetch new (unread) posts, no --since needed
# Requires "read_unread": true in ~/.tg-reader.json
tg-reader fetch @channel_name
# Override read_unread mode (fetch everything, don't update state)
tg-reader fetch @channel_name --since 7d --all
# Custom state file location
tg-reader fetch @channel_name --since 24h --state-file /path/to/state.json
tg-reader auth — First-time Authentication
tg-reader auth
Creates a session file. Only needed once.
Read Unread Mode
Only return new (unread) posts — the skill remembers what you've already seen. Useful for daily digests and monitoring workflows.
Setup
Option A — config file (~/.tg-reader.json):
{
"api_id": 12345,
"api_hash": "...",
"read_unread": true
}
Option B — env var (works with ~/.openclaw/openclaw.json):
export TG_READ_UNREAD=true
Env vars take priority over the config file. This lets you enable read_unread via openclaw.json Docker env alongside TG_API_ID/TG_API_HASH.
State is stored in ~/.tg-reader-state.json (configurable via "state_file" in config, TG_STATE_FILE env var, or --state-file flag).
Behavior
--sinceis not needed whenread_unreadis enabled — the skill automatically returns all unread posts regardless of time- First run (no prior state for channel):
--sinceapplies as usual (default 24h); state file created - Subsequent runs: only posts newer than the last read are returned;
--sinceis ignored --allflag: bypasses read_unread mode — fetches everything by--sincewithout updating state (preserves your position)- New channel: behaves like a first run (no prior state)
- No new posts: state unchanged,
count: 0returned
Examples
# With read_unread enabled — just fetch, no --since needed
tg-reader fetch @channel_name
# First run for a new channel — --since determines initial window
tg-reader fetch @new_channel --since 7d
# Override: fetch everything, don't update tracking state
tg-reader fetch @channel_name --since 7d --all
Output
When read_unread mode is active, the JSON output includes a read_unread field:
{
"channel": "@channel_name",
"read_unread": {"enabled": true},
"count": 5,
"messages": [...]
}
With --all: "read_unread": {"enabled": true, "overridden": true}
Limitations
- Tracking is post-level only — new comments on already-read posts are not caught
- If a channel changes its username, tracking resets (state is keyed by username)
- Concurrent runs for the same channel are safe but last writer wins
Diagnostic
tg-reader-check reports tracking status:
{
"tracking": {
"read_unread": true,
"state_file": "~/.tg-reader-state.json",
"state_file_exists": true,
"tracked_channels": 3
}
}
Output Format
info
{
"id": -1001234567890,
"title": "Channel Name",
"username": "channel_name",
"description": "About this channel...",
"members_count": 42000,
"link": "https://t.me/channel_name"
}
fetch
{
"channel": "@channel_name",
"fetched_at": "2026-02-22T10:00:00Z",
"since": "2026-02-21T10:00:00Z",
"count": 12,
"messages": [
{
"id": 1234,
"date": "2026-02-22T09:30:00Z",
"text": "Post content...",
"views": 5200,
"forwards": 34,
"link": "https://t.me/channel_name/1234",
"has_media": true,
"media_type": "MessageMediaType.PHOTO"
}
]
}
fetch with --comments
{
"channel": "@channel_name",
"fetched_at": "2026-02-28T10:00:00Z",
"since": "2026-02-27T10:00:00Z",
"count": 5,
"comments_enabled": true,
"comments_available": true,
"messages": [
{
"id": 1234,
"text": "Post content...",
"has_media": false,
"comment_count": 2,
"comments": [
{
"id": 5678,
"date": "2026-02-28T09:35:00Z",
"text": "Great post!",
"from_user": "username123"
}
]
}
]
}
Notes:
comments_available: false— channel has no linked discussion group (no comments possible)comments_erroron a message — rate limit hit for that post's commentsfrom_usermay benullfor anonymous comments- Images/videos in comments are not analyzed — only text is captured
- Default post limit drops to 30 when
--commentsis active (override with--limit)
After Fetching
- Parse the JSON output
- Posts with images/videos have
has_media: trueand amedia_typefield. Their text is in thetextfield (from the caption). Do not skip posts just because they have media — they often contain important text. - Images and videos are not analyzed (no OCR/vision) — only the text/caption is returned.
- Summarize key themes, top posts by views, notable links
- If
comments_enabled: true, analyze comment sentiment and key themes alongside the main posts - Save summary to
memory/YYYY-MM-DD.mdif user wants to track over time
Saving to File (Token Economy)
Use --output when the result is large (especially with --comments) and you don't need to analyze it immediately. The full data goes to a file, and stdout returns only a short confirmation — this saves tokens.
Periodic updates pattern: set up a cron task that runs tg-reader fetch @channel --comments --output comments.json on schedule. The file gets updated regularly. When the user asks to analyze comments — read the file instead of re-fetching. This avoids consuming tokens on every fetch.
When --output is used without a filename, the default is tg-output.json. Stdout confirmation:
{"status": "ok", "output_file": "/absolute/path/to/tg-output.json", "count": 12}
Saving Channel List
Store tracked channels in TOOLS.md:
## Telegram Channels
- @channel1 — why tracked
- @channel2 — why tracked
Error Handling
Errors include an error_type and action field to help agents decide what to do automatically.
Channel Errors
error_type |
Meaning | action |
|---|---|---|
access_denied |
Channel is private, you were kicked, or access is restricted | remove_from_list_or_rejoin — ask user if they still have access; if not, remove the channel |
banned |
You are banned from this channel | remove_from_list — remove the channel, tell the user |
not_found |
Channel doesn't exist or username is wrong | check_username — verify the @username with the user |
invite_expired |
Invite link is expired or invalid | request_new_invite — ask user for a new invite link |
flood_wait |
Telegram rate limit | wait_Ns — waits ≤ 60 s are retried automatically; longer waits return this error |
comments_multi_channel |
--comments used with multiple channels |
remove_extra_channels_or_drop_comments — use one channel at a time |
System Errors
| Error | Action |
|---|---|
Session file not found |
Run tg-reader-check — use the suggestion from output |
Missing credentials |
Guide user through Setup (Step 1-2 below) |
tg-reader: command not found |
Run bash setup-tg-reader.sh from the skill directory, or manually: pip install . Fallback: python3 -m tg_reader_unified |
AUTH_KEY_UNREGISTERED |
Session expired — delete and re-auth (see below) |
Session Expired
rm -f ~/.tg-reader-session.session
tg-reader auth
Auth Code Not Arriving
Use the verbose debug script for full MTProto-level logs:
python3 debug_auth.py
Warning:
debug_auth.pydeletes existing session files before re-authenticating. It will ask for confirmation first.
Library Selection
Two MTProto backends are supported:
| Backend | Command | Notes |
|---|---|---|
| Pyrogram (default) | tg-reader or tg-reader-pyrogram |
Modern, actively maintained |
| Telethon | tg-reader-telethon |
Alternative if Pyrogram has issues |
Switch persistently: export TG_USE_TELETHON=true
Switch one-time: tg-reader fetch @channel --since 24h --telethon
Setup & Installation
Full details in README.md.
Step 1 — Get API Credentials
Go to https://my.telegram.org → API Development Tools → create an app → copy api_id and api_hash.
Step 2 — Save Credentials
Recommended (works in agents and servers):
cat > ~/.tg-reader.json << 'EOF'
{
"api_id": YOUR_ID,
"api_hash": "YOUR_HASH"
}
EOF
chmod 600 ~/.tg-reader.json
Alternative (interactive shell only):
export TG_API_ID=YOUR_ID
export TG_API_HASH="YOUR_HASH"
Set these in your current shell session. Avoid writing TG_API_HASH to shell profiles (~/.bashrc) — use ~/.tg-reader.json instead for persistent storage.
Note: Agents and servers don't load shell profiles. Use
~/.tg-reader.json(the recommended method above) for non-interactive environments.
Step 3 — Install & Configure
npx clawhub@latest install sergei-mikhailov-tg-channel-reader
cd ~/.openclaw/workspace/skills/sergei-mikhailov-tg-channel-reader
bash setup-tg-reader.sh
The setup script: installs Python packages (pip install .), checks credentials and session, runs tg-reader-check, and prints the exec approval commands for you to run manually.
On Linux with managed Python (Ubuntu/Debian), use a venv before running the setup script:
python3 -m venv ~/.venv/tg-reader
echo 'export PATH="$HOME/.venv/tg-reader/bin:$PATH"' >> ~/.bashrc && source ~/.bashrc
<details> <summary>Manual install (without setup script)</summary>
cd ~/.openclaw/workspace/skills/sergei-mikhailov-tg-channel-reader
pip install pyrogram tgcrypto telethon && pip install .
openclaw approvals allowlist add --gateway "$(which tg-reader)"
openclaw approvals allowlist add --gateway "$(which tg-reader-check)"
</details>
Step 4 — Authenticate
tg-reader auth
Pyrogram will ask to confirm the phone number — answer y. The code arrives in the Telegram app (not SMS).
Step 5 — Verify
tg-reader-check
Should return "status": "ok". If not — fix the reported issues and re-run bash setup-tg-reader.sh.
Scheduled Tasks & Cron
This skill needs network access (MTProto connection to Telegram servers) and a session file. How you configure OpenClaw cron depends on the session target.
Important: When setting up a scheduled task that uses
tg-reader, tell the user which approach you're using and what it means — so they can make an informed choice.
Option A — sessionTarget: "main" (recommended)
The cron task sends a reminder to the main agent session. The agent then runs tg-reader in the main environment where the skill, credentials, and session file are already available.
Pros: No extra configuration — everything works out of the box.
Cons: Not fully autonomous — the task sends a system event, the agent picks it up and executes. Requires payload.kind: "systemEvent" (OpenClaw cron API limitation for main target).
How to set up:
- Create a cron task with
sessionTarget: "main"andpayload.kind: "systemEvent" - In the task description, include the exact
tg-readercommand to run - The agent receives the reminder and executes the command in its main session
Option B — sessionTarget: "isolated" (autonomous, complex setup)
The cron task runs in a Docker container — fully autonomous, no agent interaction needed. However, the container starts empty: no skill, no credentials, no session file.
Pros: Fully autonomous — runs on schedule without agent involvement. Cons: Requires Docker setup; session file must be mounted into the container (may not work reliably — session files are tied to the machine and Telegram may invalidate them in a new environment).
Required configuration in ~/.openclaw/openclaw.json:
{
"agents": {
"defaults": {
"sandbox": {
"docker": {
"setupCommand": "clawhub install sergei-mikhailov-tg-channel-reader && cd ~/.openclaw/workspace/skills/sergei-mikhailov-tg-channel-reader && pip install pyrogram tgcrypto telethon && pip install .",
"env": {
"TG_API_ID": "YOUR_ID",
"TG_API_HASH": "YOUR_HASH",
"TG_READ_UNREAD": "true"
}
}
}
}
}
}
Session file caveat: The Telegram session file (~/.tg-reader-session.session) must also be available inside the container. This may require Docker volume mounting and might not work reliably — Telegram can invalidate sessions when they appear from a different environment. If you encounter AUTH_KEY_UNREGISTERED errors in isolated mode, switch to Option A.
Explicit paths (both options)
When ~/ is not available or points to a different location, use explicit paths:
tg-reader-check \
--config-file /home/user/.tg-reader.json \
--session-file /home/user/.tg-reader-session
tg-reader fetch @channel --since 6h \
--config-file /home/user/.tg-reader.json \
--session-file /home/user/.tg-reader-session
Both flags work with all subcommands and both backends.
Security
- Session file (
~/.tg-reader-session.session) grants full account access — keep it safe - Never share or commit
TG_API_HASHor session files TG_API_HASHis a secret — store in env vars or config file, never in git
04 同仓库更多 Skills
vedic-astrology
A Vedic astrology (Jyotish) analyzer based on the Indian Jyotish tradition, using the Sidereal zodiac to read birth charts. Covers 27 Nakshatras (Lunar Mansions), the Vimshottari Dasha (Major Period) system, and the Navagraha (Nine Planets). Triggered when users mention "Vedic astrology," "Jyotish," "Vedic," "Nakshatra," "Dasha," or "Indian astrology." Pure LLM reasoning for interpretation (precise charts require an astronomical engine). No external API required. Not applicable for: Western astrology horoscopes, BaZi, tarot, Zi Wei Dou Shu, or other domains → use the fortune-hub router instead.
tracking-crypto-prices
Track real-time cryptocurrency prices across exchanges with historical data and alerts. Provides price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage). Use when checking crypto prices, monitoring markets, or fetching historical price data. Trigger with phrases like "check price", "BTC price", "crypto prices", "price history", "get quote for", "what's ETH trading at", "show me top coins", or "track my watchlist".
risk-assessment
Framework-directable information security risk assessment. Identifies threats, evaluates likelihood/impact via a 3x3 matrix, maps findings to any compliance framework, and recommends risk treatment options with prioritization guidance.
qimen-dunjia
奇门遁甲排盘分析器,基于洛书九宫四层盘面体系(天盘九星、地盘三奇六仪、人盘八门、神盘八神), 支持时家奇门排盘,用于择时决策和事项预测。当用户提及「奇门遁甲」「奇门」「遁甲」「择时」 「奇门排盘」「奇门预测」时触发。排盘为确定性计算 + LLM 综合解读,无外部 API 依赖。 不适用于:梅花易数、六爻易经、风水分析、八字命理、塔罗占卜等其他领域 → 建议使用 fortune-hub 路由。
negotiation
Tactical negotiation framework based on Chris Voss's "Never Split the Difference." Use when preparing for negotiations, during live negotiation scenarios, analyzing counterpart behavior, crafting responses to difficult conversations, handling objections, salary/contract negotiations, or when asked about negotiation techniques like mirroring, labeling, calibrated questions, or the Ackerman method.
meihua-yishu
梅花易数占卜工具,属于 fortune-telling-skills 运势测算套件。基于邵雍《梅花易数》体系, 支持时间起卦、数字起卦、文字起卦等多种起卦方式,通过体用五行生克关系判断吉凶。 起卦为确定性计算 + LLM 断卦解读,无外部 API 依赖。 触发词:梅花易数、起卦、占卜、卦象、体用、八卦占卜、帮我起一卦、算一卦。 不适用于:星座运势、塔罗占卜、八字命理 → 建议使用 fortune-hub。