agentleFS
salto-agancysalto-agancy/telegram-mcp-ai-deploy/skills/telegram-reply/SKILL.md

telegram-reply

Skill0 starsChanged 2 months agoMITView on GitHub

Draft and, only after explicit human confirmation, send or edit a Telegram message. Use when the user asks to reply, send, edit, or post through Telegram.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the smallest relevant conversation/thread and verify chat ID and reply target.

    line 8
  2. Very specific:

    After approval, prefer send_message.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Telegram reply

  1. Read the smallest relevant conversation/thread and verify chat ID and reply target.
  2. Draft the exact message first. Preserve source facts; do not invent dates, sums, or IDs.
  3. Show destination, reply/message ID, attachments, and full final text. Ask for explicit confirmation immediately before the tool call.
  4. Without confirmation, stop at the draft. Approval for one message does not authorize another destination, edit, attachment, or follow-up.
  5. After approval, prefer send_message; use send_rich_message only for native tables or structured layouts and only in chats shared with that bot. Use edit_message only when the exact existing message ID was verified.
  6. Report the returned message ID. Never enable raw MTProto to bypass a denied write.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.