Telegram Connect
Apps & Automationtelegram-connectTelegram Connect is an Agent Skill for apps & automation published in the egregore-labs/egregore repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Fallback Codex adapter for the Egregore telegram-connect workflow.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/egregore-labs/egregore/blob/HEAD/.codex/skills/telegram-connect/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/telegram-connect, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Egregore telegram-connect Adapter
This is fallback coverage for a long-tail Egregore workflow that has not been ported to a hand-written Codex-native skill yet.
Use the project shell and filesystem directly. Do not invoke Claude Code
commands. Translate interactive choices to structured Codex question tooling
when it is available; otherwise render compact numbered choices with an
Other: option and wait for the user.
- Read
.claude/skills/telegram-connect/SKILL.mdfor the workflow details. - Run the referenced
bin/scripts directly from Codex. - Treat graph, publish, and notify steps as best-effort unless that workflow explicitly says they are required.
- Keep local-mode behavior filesystem-first and avoid graph or notification
calls when
egregore.jsondeclares"mode": "local". - Never call the deprecated
egregore-handoffCLI for Egregore project handoffs.