telegram-feature-scoutlisted
Install: claude install-skill soc1almemory/tg-feature-scout-skill
# Telegram Feature Scout
Find Telegram changes with a concrete use in the user's project. Keep discovery and planning read-only. If the user has already requested a specific implementation, verify it and proceed within that request.
## 1. Establish scope and project fit
- For a broad feature review, start with the last 30 days. Expand to 90 days if the first pass yields too few useful findings. Follow the user's requested window when given.
- For a named capability, start with the exact method, field, event, or client feature and its official docs. Read channel posts when they help establish timing or context, or when the user asks for them.
- Identify the bot, Mini App, or both, and the user flows that could benefit. Use manifests and lockfiles for dependency versions and the relevant handlers, frontend code, and configuration for current behavior. Distinguish installed or locked versions from declared ranges.
- If project files are unavailable, state your assumptions and mark recommendations as general. Use targeted checks for specific implementation requests and routine fixes.
## 2. Gather and verify evidence
1. Read [references/sources.md](references/sources.md). For a broad review, attempt all four listed channels and check the official changelog or change history for each Telegram surface in scope. Respect any sources the user selects. Use web search, a browser, or the optional [Python 3 scanner](scripts/scan_channels.py) from this skill's directory.
2. Verify each