telegram-doctor
Diagnose Telegram configuration and connectivity issues. Use when user reports problems with Telegram sync, connection errors, or wants to troubleshoot.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
Telegram Doctor
Diagnose configuration and connectivity issues with Telegram integration.
When to Use
- User says "Telegram not working" or "diagnose Telegram"
- User reports connection or authentication errors
- User says "check Telegram setup" or "troubleshoot Telegram"
- Before asking for help with Telegram issues
- When sync or other Telegram commands fail unexpectedly
How to Execute
python ${CLAUDE_PLUGIN_ROOT}/tools/telegram_doctor.py
What It Checks
-
Environment file -
.envexists in cwd -
API ID -
TELEGRAM_API_IDis set and numeric -
API hash -
TELEGRAM_API_HASHis set -
Session string -
TELEGRAM_SESSIONis set and valid length - Authentication - Credentials can connect to Telegram API
-
Config file -
config/agents.yamlexists and is valid YAML - Group configured - A default group is selected
-
Data directory -
data/is writable
Output
Displays results with:
- ✓ for passed checks
- ✗ for failed checks
For each failure, provides a suggested fix that the user can run manually.
Important: This tool only diagnoses issues - it does not modify any files.
Example Output
telegram-doctor results:
✓ Environment file (.env found)
✓ API ID (12345678)
✓ API hash (abc123...xyz9)
✗ Session string (Session appears too short)
✗ Config file (config/agents.yaml not found)
✗ Group configured (No default group set)
✓ Data directory (./data)
Some checks failed. Suggested fixes:
• Session string:
Generate a fresh session: python scripts/generate_session.py
• Config file:
Run telegram-init to create the config file
• Group configured:
Run telegram-init to select a group
(Run these steps manually - doctor does not modify files)
Next Steps
After fixing issues:
- Run
telegram-initto reconfigure if needed - Run
telegram-syncto test connectivity
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-26
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!