How do I install the Pin Message skill?

Run npx skillmds add terrylica/pin-message in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pin Message safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pin Message?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pin Message free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pin Message?

terrylica (@terrylica) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pin Message by terrylica — Agent Skill

Name: Pin Message
Rating: 4.5 (4 reviews)
Author: terrylica

File contents

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

Session must exist: ~/.local/share/gramjs/<profile>.session
- If missing, run /tlg:setup first

Usage

/usr/bin/env bash << 'EOF'
ROOT="$(cc-plugin-root tlg)"
SCRIPT="$ROOT/scripts/tg-cli.ts"

# Pin a message (with notification)
bun "$SCRIPT" pin <chat> <message_id>

# Pin silently (no notification)
bun "$SCRIPT" pin <chat> <message_id> --silent

# Unpin a specific message
bun "$SCRIPT" pin <chat> <message_id> --unpin

# Unpin all messages
bun "$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:

Did the command succeed? — If not, fix the instruction or error table that caused the failure.
Did parameters or output change? — If tg-cli.ts's interface drifted, update Usage examples and Parameters table to match.
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.

---name: pin-messagedescription: Use when user wants to pin or unpin a message in a Telegram chat, group, or channel, or manage pinned messages.--- # 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/gramjs/<profile>.session` - If missing, run `/tlg:setup` first ## Usage ```bash /usr/bin/env bash << 'EOF' ROOT="$(cc-plugin-root tlg)" SCRIPT="$ROOT/scripts/tg-cli.ts" # Pin a message (with notification) bun "$SCRIPT" pin <chat> <message_id> # Pin silently (no notification) bun "$SCRIPT" pin <chat> <message_id> --silent # Unpin a specific message bun "$SCRIPT" pin <chat> <message_id> --unpin # Unpin all messages bun "$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.ts'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.

Frequently asked questions