Agent skill
telegram-guide
Telegram notification integration guide for PACT. Use when telegram_notify is available in your tools — covers when to notify, when to ask, when to check replies, and multi-session behavior.
Install this agent skill to your Project
npx add-skill https://github.com/Synaptic-Labs-AI/PACT-Plugin/tree/main/pact-plugin/skills/telegram-guide
SKILL.md
Telegram Notifications
Telegram is an optional add-on. Not all PACT users have it installed. Before using any telegram tool, check if it exists in your available tools. If telegram_notify is not listed, do NOT attempt to call it — skip all Telegram functionality silently with no errors or warnings to the user.
How to check: If telegram_notify appears in your tool list, the bridge is active. If not, ignore this entire section.
Available tools (only when bridge is active):
| Tool | Purpose | Blocking? |
|---|---|---|
telegram_notify |
Send one-way notification (completions, deployments, alerts) | No |
telegram_ask |
Ask a blocking question with optional buttons; supports text/voice replies | Yes |
telegram_check_replies |
Poll for queued replies to notifications | No |
telegram_status |
Health check (connection, mode, queue depth) | No |
When to notify (target ~3-5 per session):
- Task or phase completions
- Blockers found or algedonic signals
- PR ready for review or merged
- Deployments pushed
When to use telegram_ask:
- Blocking decisions where user may be away from terminal
- Scope clarifications that can't proceed without input
When to check replies (telegram_check_replies):
- Between tasks or phases — check if user reacted to any notification
- After sending important notifications — user may reply with corrections or new instructions
- Replies include context snippet of the original notification
Multi-session behavior:
- Messages are prefixed with
[ProjectName]for session identification - Multiple sessions coordinate via file-based polling — replies route to the correct session
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
n8n-code-javascript
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
n8n-node-configuration
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type.
pact-coding-standards
Clean code principles, error handling patterns, and coding standards for PACT Code phase. Use when: implementing features, refactoring code, reviewing code quality, establishing coding conventions, or handling errors and exceptions. Triggers on: code quality, clean code, refactoring, error handling, logging patterns, naming conventions, code review, code phase.
pact-handoff-harvest
HANDOFF discovery, review, save, and cleanup workflow for the PACT secretary. Use when: processing agent HANDOFFs after workflow phases, running session consolidation, or recovering orphaned breadcrumbs from prior sessions. Triggers: harvest HANDOFFs, process HANDOFFs, incremental, consolidation, breadcrumb recovery.
n8n-code-python
Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.
n8n-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.
Didn't find tool you were looking for?