home / skills / lycfyi / community-agent-plugin / telegram-doctor

This skill diagnoses Telegram configuration and connectivity issues, guiding you to fix Telegram sync, authentication, and group setup problems.

npx playbooks add skill lycfyi/community-agent-plugin --skill telegram-doctor

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.1 KB
---
name: telegram-doctor
description: "Diagnose Telegram configuration and connectivity issues. Use when user reports problems with Telegram sync, connection errors, or wants to troubleshoot."
---

# 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

```bash
python ${CLAUDE_PLUGIN_ROOT}/tools/telegram_doctor.py
```

## What It Checks

1. **Environment file** - `.env` exists in cwd
2. **API ID** - `TELEGRAM_API_ID` is set and numeric
3. **API hash** - `TELEGRAM_API_HASH` is set
4. **Session string** - `TELEGRAM_SESSION` is set and valid length
5. **Authentication** - Credentials can connect to Telegram API
6. **Config file** - `config/agents.yaml` exists and is valid YAML
7. **Group configured** - A default group is selected
8. **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:
1. Run `telegram-init` to reconfigure if needed
2. Run `telegram-sync` to test connectivity

Overview

This skill diagnoses Telegram configuration and connectivity issues for integrations that sync messages or use the Telegram API. It runs a series of non-destructive checks and reports which items pass or fail, with targeted suggested fixes. Use it as a first step before making changes or asking for support.

How this skill works

The tool inspects the local environment and configuration files: it checks for a .env file, validates TELEGRAM_API_ID and TELEGRAM_API_HASH, verifies the session string length, and confirms the app can authenticate with Telegram. It also validates config/agents.yaml, ensures a default group is configured, and checks that the data/ directory is present and writable. Results are shown with pass/fail marks and concise suggested remediation steps; the tool does not modify any files.

When to use it

  • User reports "Telegram not working" or sync failures
  • Connection or authentication errors appear in logs
  • Preparing to run telegram-sync or telegram-init
  • Before filing an issue or requesting help
  • After moving the project or changing environment variables

Best practices

  • Keep a copy of your .env before editing environment variables
  • Use numeric API ID and exact API hash from your Telegram app settings
  • Keep session strings secure and regenerate if they appear truncated
  • Run telegram-doctor immediately after changing config files or upgrading dependencies
  • Follow suggested fixes exactly and re-run the doctor to confirm fixes

Example use cases

  • Diagnose a failed telegram-sync that reports authentication errors
  • Confirm environment variables and file permissions on a fresh deployment
  • Validate that a default Telegram group is selected before starting a continuous sync
  • Check whether the session string was corrupted or truncated
  • Run quick preflight checks as part of a troubleshooting checklist

FAQ

Will this tool change my files or credentials?

No. The skill performs read-only checks and only prints suggested manual fixes; it never modifies files or credentials.

I fixed an issue. How do I verify it?

Re-run the telegram-doctor to confirm the relevant checks now pass, then run telegram-init or telegram-sync as applicable.