telegram-watch SKILL.md skillA
telegram-watch from tonydzi/second-brain-starter-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tonydzi/second-brain-starter-kit/telegram-watch@git:20260908.2ec1bf8Pins git:20260908.2ec1bf8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tonydzi/second-brain-starter-kit
- Path
skills/telegram-watch/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260908.2ec1bf8, committed Sep 8, 2026
- First version recorded
- Aug 14, 2026
- Size
- 10,788 bytes
- Repository stars
- 14
- License
- MIT
Run an always-on Telegram watch loop under a separate assistant account using MCP push tools. Mode 1 answers when the assistant account is mentioned in team chats, with actionable vault-grounded advice; mode 2 ambiently watches designated chats and pings on salient events. Triggers: "/telegram-watch", "start the telegram watch".
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-watch — the watch shift (@corp_acct) > Decided by the operator 2026-06-11: **no BotFather bots.** The assistant lives on their > own second user-account **@corp_acct** (label `corp_acct`, id 7303193973, > Premium, on its own real SIM). The operator himself = @work_acct_a (label `default`, > id 226258979). Separate StringSession per account → no AUTH_KEY_DUPLICATED > (see memory `telegram-eventloop-listener`). > ⚙️ **LIVE ENGINE (2026-06-15): standalone daemon, not this in-session loop.** > The production watch now runs as `<TG_WATCH_DIR>\tg_watch_daemon.py` — a thin > always-on Telethon daemon that is the SOLE owner of the daemon's OWN minted > @corp_acct authorization (NOT the MCP's session → no AUTH_KEY_DUPLICATED), with > a **singleton lock** (port 47921) so it can never double-run. It catches the operator's > task event in seconds, **reads the n8n transcript** (bot "Personal Audio Summary" > id 5305064675 replies to their voice — we do NOT run our own whisper, the operator > 2026-06-15), grounds via `brain_ask`, makes ONE `claude -p` (subscription path), > and DMs the operator a DRAFT. Canon = `02-Decisions\decision-always-on-telegram-assistant-daemon`. …
Read the whole file at its exact version.
How to install
mdr add tonydzi/second-brain-starter-kit/telegram-watch@sha256:fc1e4f6f41faf013The line at the top of this page pins the label git:20260908.2ec1bf8, 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_q5u7ksqjvrfkzvmg)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 14, 2026 and Sep 8, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260908.2ec1bf8 latest | 2026-09-08 | 2ec1bf8 | 10,788 B | A | view · diff |
| git:20260814.fb32560 | 2026-08-14 | fb32560 | 10,406 B | A | view · diff |
| git:20260814.06fa906 | 2026-08-14 | 06fa906 | 10,330 B | A | view · diff |
| git:20260814.5023d8c | 2026-08-14 | 5023d8c | 9,635 B | A | view · diff |
| git:20260814.44e61cf | 2026-08-14 | 44e61cf | 10,170 B | A | view |
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 (10788 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
tonydzi/second-brain-starter-kit · 14 stars · license MIT · pushed 2026-11-06 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_q5u7ksqjvrfkzvmg GET https://markdownregistry.com/api/v1/resolve?ref=tonydzi/second-brain-starter-kit/telegram-watch GET https://markdownregistry.com/api/v1/blob/fc1e4f6f41faf013fa7010466f4e66f9ec8c3f2657973387616d0383626d2b2b
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.