From tlg
Use when user wants to download, save, or extract media files such as photos, videos, and documents from Telegram messages.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tlg:download-mediaThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Download photos, videos, documents, and other media from Telegram messages.
Download photos, videos, documents, and other media from Telegram messages.
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.
~/.local/share/gramjs/<profile>.session
/tlg:setup first/usr/bin/env bash << 'EOF'
SCRIPT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/tlg}/scripts/tg-cli.ts"
# Step 1: Find message ID with media
bun "$SCRIPT" read <chat> -n 10
# Step 2: Download by message ID
bun "$SCRIPT" download <chat> <message_id>
# Download to specific directory
bun "$SCRIPT" download 2124832490 471931 -o ./downloads
EOF
| Parameter | Type | Description |
|---|---|---|
| chat | string/int | Chat containing the message |
| message_id | int | ID of message with media |
-o/--output | path | Output directory (default: current) |
read <chat> -n N to browse messages and find IDs[media/service] in textdownload <chat> <id> to save the file| Error | Cause | Fix |
|---|---|---|
message not found | Invalid message ID | Check with read first |
has no media | Text-only message | Choose a message with media |
After this skill completes, check before closing:
Only update if the issue is real and reproducible — not speculative.
npx claudepluginhub terrylica/cc-skills --plugin tlgGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.