---
name: pin-message
description: "Use when user wants to pin or unpin a message in a Telegram chat, group, or channel, or manage pinned messages."
allowed-tools: Bash, Read, Grep, Glob
---

# Pin/Unpin Telegram Messages

Pin or unpin messages in chats, groups, and channels.

> **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"

# Pin a message (with notification)
uv run --python 3.14 "$SCRIPT" pin <chat> <message_id>

# Pin silently (no notification)
uv run --python 3.14 "$SCRIPT" pin <chat> <message_id> --silent

# Unpin a specific message
uv run --python 3.14 "$SCRIPT" pin <chat> <message_id> --unpin

# Unpin all messages
uv run --python 3.14 "$SCRIPT" pin <chat> --unpin
EOF
```

## Parameters

| Parameter  | Type       | Description                                     |
| ---------- | ---------- | ----------------------------------------------- |
| chat       | string/int | Chat/group/channel                              |
| message_id | int        | Message to pin (omit with --unpin to unpin all) |
| `--unpin`  | flag       | Unpin instead of pin                            |
| `--silent` | flag       | Pin without sending notification                |

## 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.