How do I install the Forward Message skill?

Run npx skillmds add terrylica/forward-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 Forward 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 Forward 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 Forward Message free to use?

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

Who published Forward Message?

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

Forward Message by terrylica — Agent Skill

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

File contents

Forward Telegram Messages

Forward one or multiple messages between chats.

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"

# Forward single message
bun "$SCRIPT" forward <from_chat> <message_id> <to_chat>

# Forward multiple messages (comma-separated IDs)
bun "$SCRIPT" forward 2124832490 471920,471921 90417581

# Get message IDs first with read command
bun "$SCRIPT" read <chat> -n 5
EOF

Workflow

Use read to find message IDs: read <chat> -n 10
Forward by ID: forward <from> <id> <to>

Parameters

Parameter	Type	Description
from_chat	string/int	Source chat
message_ids	string	Message ID(s), comma-separated
to_chat	string/int	Destination chat

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: forward-messagedescription: Use when user wants to forward, relay, or copy Telegram messages from one chat to another, supporting both single and batch forwarding.--- # Forward Telegram Messages Forward one or multiple messages between chats. > **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" # Forward single message bun "$SCRIPT" forward <from_chat> <message_id> <to_chat> # Forward multiple messages (comma-separated IDs) bun "$SCRIPT" forward 2124832490 471920,471921 90417581 # Get message IDs first with read command bun "$SCRIPT" read <chat> -n 5 EOF ``` ## Workflow 1. Use `read` to find message IDs: `read <chat> -n 10` 2. Forward by ID: `forward <from> <id> <to>` ## Parameters | Parameter | Type | Description | | ----------- | ---------- | ------------------------------ | | from_chat | string/int | Source chat | | message_ids | string | Message ID(s), comma-separated | | to_chat | string/int | Destination chat | ## 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