telegram-topics-pipeline SKILL.md skillA
telegram-topics-pipeline from jpeetz/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jpeetz/agent-skills/telegram-topics-pipeline@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jpeetz/agent-skills
- Path
skills/development/telegram-topics-pipeline/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 13, 2026
- Size
- 9,128 bytes
- Repository stars
- 16
- License
- none declared
Use this skill when setting up Telegram forum topics to run multiple independent bot sessions or automated pipelines in one group with isolated context, per-topic skills, cron delivery, and no cross-contamination between workflows.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Telegram Topics Pipeline
Wire Telegram's forum topics into your agent infrastructure so each topic is its own isolated agent session with dedicated context, skills, and cron pipeline. No context bleed. No accidental cross-posting. One group, N independent workflows.
This is the single highest-impact operational change you can make to how your agent runs. A flat DM or group chat forces every topic into the same context window. Topics fix that.
---
## How It Works
Telegram forum topics (supergroups with Topics mode) each carry a unique `message_thread_id`. Hermes (and OpenClaw) use the pair `(chat_id, thread_id)` as a session key:
```
agent:main:telegram:dm:{chat_id}:{thread_id} # DM topics
agent:main:telegram:group:{chat_id}:{thread_id} # Group forum topics
```
Messages in Topic A never appear in Topic B's session history. They are independent conversations with their own scrollback, memory, and active context.
---
## Step 0: Enable Topics
**You must enable Topics on the Telegram side.** The bot cannot do this.
1. Create a Telegram group (or use an existing one)
2. Add your bot to the group
3. Go to **Group Settings → Edit → Enable Topics (Forum mode)**
…Read the whole file at its exact version.
How to install
mdr add jpeetz/agent-skills/telegram-topics-pipeline@sha256:caf13ba7367eb0edThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jvkbndqp5skrexcn)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 13, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9128 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jpeetz/agent-skills · 16 stars · license none declared · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jvkbndqp5skrexcn GET https://markdownregistry.com/api/v1/resolve?ref=jpeetz/agent-skills/telegram-topics-pipeline GET https://markdownregistry.com/api/v1/blob/caf13ba7367eb0ed5753a67340e5ca28a06814127febb371ed021b3b846f47da
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.