search-messages
Use when user wants to search for messages across all Telegram chats or within a specific chat, find old messages by text, or look up Telegram message history filtered by sender.
Best use case
search-messages is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when user wants to search for messages across all Telegram chats or within a specific chat, find old messages by text, or look up Telegram message history filtered by sender.
Teams using search-messages should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/search-messages/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How search-messages Compares
| Feature / Agent | search-messages | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when user wants to search for messages across all Telegram chats or within a specific chat, find old messages by text, or look up Telegram message history filtered by sender.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Search Telegram Messages
Search messages globally across all chats or within a specific chat.
> **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
## Preflight
1. Session must exist: `~/.local/share/telethon/<profile>.session`
- If missing, run `/tlg:setup` first
## Usage
```bash
/usr/bin/env bash << 'EOF'
SCRIPT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/tlg}/scripts/tg-cli.py"
# Global search (all chats)
uv run --python 3.13 "$SCRIPT" search "search term" -n 20
# Search in specific chat
uv run --python 3.13 "$SCRIPT" search "keyword" --chat 2124832490
# Filter by sender
uv run --python 3.13 "$SCRIPT" search "topic" --from @username
# Combined: search in chat from specific sender
uv run --python 3.13 "$SCRIPT" search "query" --chat @groupname --from @sender -n 10
EOF
```
## Parameters
| Parameter | Type | Description |
| ------------ | ---------- | ------------------------------------------------------------------------ |
| query | string | Search text (required) |
| `--chat` | string/int | Limit to specific chat (omit for global) |
| `--from` | string/int | Filter by sender |
| `-n/--limit` | int | Max results (default: 20) |
| `--preview` | int | Truncate each body to N chars (default: full text, multi-line indented). |
## Output Format
Default (full text, multi-line indented):
```
[YYYY-MM-DD HH:MM] [Chat Name] (id:12345) Sender: First line of body
continuation line 1 (indented under header)
continuation line 2
```
With `--preview 100`:
```
[YYYY-MM-DD HH:MM] [Chat Name] (id:12345) Sender: First line of body ⏎ continuation collapsed onto…
```
Use `--preview N` only for high-volume scans where you want one row per
message. Default = full text — long bodies are no longer silently
truncated at 150 chars (the prior default forced direct-Telethon escape
hatches when content actually mattered).
## Anti-Patterns
- **Flood risk**: Global search with common terms may hit rate limits (~30s wait per 10 requests)
- **Empty results**: Global search requires non-empty query string
## Post-Execution Reflection
After this skill completes, check before closing:
1. **Did the command succeed?** — If not, fix the instruction or error table that caused the failure.
2. **Did parameters or output change?** — If tg-cli.py's interface drifted, update Usage examples and Parameters table to match.
3. **Was a workaround needed?** — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.
Only update if the issue is real and reproducible — not speculative.Related Skills
delete-messages
Use when user wants to delete, remove, or unsend Telegram messages from a chat, either for everyone or just for themselves.
research-archival
Scrape AI research URLs, archive with frontmatter, create GitHub Issues with identity verification. TRIGGERS - scrape research, archive findings, save ChatGPT share, save Gemini research, research to issue.
gemini-deep-research
Run Gemini Deep Research via browser automation. Persistent Chrome on CDP port 9222. Use when user asks to research a topic with Gemini, run deep research, or wants comprehensive AI-powered research reports. TRIGGERS - Gemini research, deep research, research report, Gemini Deep Research
firecrawl-research-patterns
Programmatic Firecrawl usage, self-hosted operations, academic paper routing, recursive deep research, and raw corpus persistence. TRIGGERS - firecrawl search, firecrawl scrape, academic paper, arxiv, deep research, recursive search, research pattern, corpus persistence, firecrawl, self-hosted scraping, web scrape, scraper wrapper, littleblack, Tailscale scraping.
voice-quality-audition
Audition Kokoro TTS voices to compare quality and grade. TRIGGERS - audition voices, kokoro voices, voice comparison, tts voice, voice quality, compare voices.
settings-and-tuning
Configure TTS voices, speed, timeouts, queue depth, and bot settings. TRIGGERS - configure tts, change voice, tts speed, queue depth, tts timeout, bot config, tune settings, adjust parameters.
full-stack-bootstrap
One-time bootstrap for Kokoro TTS engine, Telegram bot, and BotFather setup. TRIGGERS - setup tts, install kokoro, botfather, bootstrap tts-tg-sync, configure telegram bot, full stack setup.
diagnostic-issue-resolver
Diagnose and resolve TTS and Telegram bot issues. TRIGGERS - tts not working, bot not responding, kokoro error, audio not playing, lock stuck, telegram bot troubleshoot, diagnose issue.
component-version-upgrade
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
clean-component-removal
Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro, clean tts, teardown, component removal.
send-message
Use when user wants to send a text message on Telegram as their personal account via MTProto, text someone, or message a contact by username, phone, or chat ID.
send-media
Use when user wants to send or upload a file, photo, video, voice note, or document on Telegram via their personal account.