telegram-connect
Skill293 starsChanged 11 days agoMITView on GitHub
Set up Telegram as a notification center for your Egregore — creates the group, links the bot, and stores the chat ID. Use for /telegram-connect, 'connect telegram', or 'set up telegram notifications'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tonydzi/telegram-mcp-kittheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tonydzi/telegram-mcp-kit★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Check for existing telegram_chat_id — it lives in .egregore-state.json (preferred) or egregore.json (legacy):
- Distinctive: line 30
If already set, show:
- Very specific: line 43
Read the org slug from egregore.json:
- Very specific: line 48
If slug is set, generate the deep link with it: https://t.me/Egregore_clbot?startgroup=org_{slug} If slug is empty, fall back to: …
- Very specific: line 49
If slug is empty, fall back to: https://t.me/Egregore_clbot?startgroup=true
- Very specific: line 78
Read .egregore-state.json, add telegram_chat_id and telegram_group_link fields, write it back.
- Very specific: line 80
Important: Write to .egregore-state.json, NOT egregore.json.
- Very specific: line 97
Use the printed values as {plan_id} and {digest}, respectively.
- Very specific: line 112
If cancelled, show Telegram connected — no test message sent.
- Distinctive: line 123
Never expose credentials in tool output
- Distinctive: line 125
Only store the group invite link and chat ID, not bot tokens (those live on the API server)
- Distinctive: line 127
No commit/push needed — state file is local and shared via symlinks
≈ “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.
Files
Set up Telegram as a notification center for your Egregore.
Arguments: $ARGUMENTS (none expected)
When to invoke
Trigger phrases:
- "set up telegram", "connect telegram", "add notifications", "telegram-connect"
- "telegram group", "add telegram", "enable telegram", "link telegram"
- "notification setup", "set up notifications"
Disambiguation:
- "send a message on telegram" → NOT this — use the separate notification
consent protocol in
.claude/context/notification-consent.md - "announce something" → NOT this — use
/announce
Step 1: Check current state
Check for existing telegram_chat_id — it lives in .egregore-state.json (preferred) or egregore.json (legacy):
jq -r '.telegram_chat_id // empty' .egregore-state.json 2>/dev/null || jq -r '.telegram_chat_id // empty' egregore.json 2>/dev/nullIf already set, show:
Telegram is already connected.
Chat ID: {chat_id}
Group link: {group_link}
To update it, remove `telegram_chat_id` from .egregore-state.json and run `/telegram-connect` again.And stop.
Step 2: Guide setup
Read the org slug from egregore.json:
jq -r '.slug // empty' egregore.json 2>/dev/nullIf slug is set, generate the deep link with it: https://t.me/Egregore_clbot?startgroup=org_{slug}
If slug is empty, fall back to: https://t.me/Egregore_clbot?startgroup=true
Show:
To set up Telegram notifications:
1. Create a Telegram group for your team
2. Add the bot: {deep_link}
3. The bot will respond with your Chat ID — copy it
4. Get the invite link: group name → Edit → Invite Links → Copy
5. Paste both belowThen ask for the chat ID with a structured question when available and permitted in this session; otherwise ask in plain text:
Chat ID (from the bot's message in your group):Validate: must be a negative number (e.g., -1001234567890) — reject anything else with "That doesn't look like a Telegram chat ID. It should be a negative number like -1001234567890."
Then ask for the group invite link with a structured question when available and permitted in this session; otherwise ask in plain text:
Group invite link:Validate: must start with https://t.me/ — reject anything else with "That doesn't look like a Telegram invite link."
Step 3: Store and test
Read .egregore-state.json, add telegram_chat_id and telegram_group_link fields, write it back.
Important: Write to .egregore-state.json, NOT egregore.json. The state file is symlinked across worktrees so the config propagates everywhere. No branch, commit, or push is needed — it's an untracked local file.
Offer an optional test through the separate exact notification consent flow in
.claude/context/notification-consent.md. Saving the Telegram configuration is
not consent to send. Prepare without sending:
mkdir -p tmpbash bin/notify.sh plan group "Telegram connected! 🎉" > tmp/telegram-connect-plan.jsonjq -r '.plan_id, .digest' tmp/telegram-connect-plan.jsonUse the printed values as {plan_id} and {digest}, respectively; quote
placeholders in single quotes when you use them in a command, and write any
single quote inside a value as '\''. Use them for the notification consent
flow. Read the exact preview fields:
jq -r '.org, .recipient, .channels, .deliveries, .message' tmp/telegram-connect-plan.jsonShow the organization, group/channel, and exact message in a dedicated Send / Edit / Cancel checkpoint. If approved and dispatched, show:
Telegram connected — test message sent to your group.If cancelled, show Telegram connected — no test message sent. If planning or
dispatch fails, show the error and suggest checking the chat ID.
Step 4: Telemetry
bash bin/telemetry.sh emit "command" '{"command":"telegram-connect"}' 2>/dev/null &Rules
- Never expose credentials in tool output
- The bot username is
@Egregore_clbot— NOT@egregore_bot - Only store the group invite link and chat ID, not bot tokens (those live on the API server)
- Store in
.egregore-state.json(symlinked, untracked) — NOTegregore.json(tracked, branch-specific) - No commit/push needed — state file is local and shared via symlinks
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
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.

