Martin-HausleitnerMartin-Hausleitner/martins-awesome-skills/skills/telegram-approval-gate/SKILL.md

telegram-approval-gate

Skill3 starsChanged 6 months agoMITView on GitHub

Use when Hermes is about to send, publish, forward, reply, post, email, DM, or otherwise deliver text/media to another person, group, channel, or external service and the operator expects Telegram confirmation buttons.

In this repository34 other files it gives its agents.
- tool-comparison-heatmapSkill
- ascii-artSkill
- excalidrawSkill
- p5jsSkill
- songwriting-and-ai-musicSkill
- webhook-subscriptionsSkill
- himalayaSkill
- github-authSkill
- github-code-reviewSkill
- github-issuesSkill
- github-pr-workflowSkill
- find-nearbySkill
- native-mcpSkill
- songseeSkill
- youtube-contentSkill
- ai-research-output-publisherSkill
- notionSkill
- ocr-and-documentsSkill
- arxivSkill
- blogwatcherSkill
- comparison-deep-researchSkill
- polymarketSkill
- multi-search-engineSkill
- ai-research-browser-cliSkill
- ai-research-browserSkill
- cross-agent-skill-syncSkill
- oracle-ai-research-e2eSkill
- planSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- writing-plansSkill
- telegram-channel-posterSkill

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Before Hermes sends external communication, route the final draft through the operator's Telegram approval gate.
line 8
Distinctive:
Never send user-facing or public content directly when this skill applies.
line 12
Distinctive:
Use the bundled helper when a real Telegram approval round is needed:
line 22
Very specific:
Do not reuse the live Hermes/OpenClaw Telegram bot token while another gateway is polling it.
line 35
Distinctive:
Run the approval helper or use the active messaging gateway's native inline-button approval mechanism.
line 48
Very specific:
If the decision is send, deliver exactly the approved content.
line 49
Very specific:
If the decision is edit, ask the operator for changes, revise, and repeat approval.
line 50
Very specific:
If the decision is cancel or timeout, do not send.
line 51
Distinctive:
Run the local end-to-end fake Telegram test before relying on changes:
line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Approval Gate

Before Hermes sends external communication, route the final draft through the operator's Telegram approval gate.

Rule

Never send user-facing or public content directly when this skill applies. First send a Telegram approval card with:

Senden - send the draft exactly as approved.
Bearbeiten - ask the operator for edits, revise the draft, then submit a new approval card.
Abbrechen - stop without sending.

This applies to Telegram, WhatsApp, Signal, email, social posts, channels, group messages, support replies, public comments, and any automation that sends on the operator's behalf.

Helper

Use the bundled helper when a real Telegram approval round is needed:

python3 ~/.hermes/skills/messaging/telegram-approval-gate/scripts/telegram_approval_gate.py \
  --title "Freigabe" \
  --draft-file /path/to/draft.txt

Required environment:

HERMES_APPROVAL_BOT_TOKEN - a dedicated approval bot token.
HERMES_APPROVAL_CHAT_ID - the operator's approval DM/chat id.

Do not reuse the live Hermes/OpenClaw Telegram bot token while another gateway is polling it. A dedicated approval bot avoids getUpdates conflicts.

For dry runs:

python3 ~/.hermes/skills/messaging/telegram-approval-gate/scripts/telegram_approval_gate.py \
  --dry-run \
  --draft "Hallo"

Workflow

Draft the exact outgoing message locally.
Run the approval helper or use the active messaging gateway's native inline-button approval mechanism.
If the decision is send, deliver exactly the approved content.
If the decision is edit, ask the operator for changes, revise, and repeat approval.
If the decision is cancel or timeout, do not send.
Record the approval result in the task summary.

Testing

Run the local end-to-end fake Telegram test before relying on changes:

python3 ~/.hermes/skills/messaging/telegram-approval-gate/tests/test_telegram_approval_gate.py

Optional live smoke test requires HERMES_APPROVAL_BOT_TOKEN and HERMES_APPROVAL_CHAT_ID; do not run it with the same token currently owned by OpenClaw/Hermes gateway polling.

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.

Check your setup, free