القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 completed handoffs from prior sessions. Triggers: harvest HANDOFFs, process HANDOFFs, incremental, consolidation, handoff recovery.
Agent Teams interaction protocol for PACT specialist agents. Auto-loaded via agent frontmatter. Defines how teammates start work, communicate, report completion, and handle blockers.
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.
Persistent memory for PACT agents. Save context, goals, lessons learned, decisions, and entities. Semantic search across sessions. Use when: saving session context, recalling past decisions, searching lessons. Triggers: memory, save memory, search memory, lessons learned, remember, recall
Command-style teachback protocol for PACT teammates. Invoking this skill directly instructs you to store your teachback in task metadata and idle on awaiting_lead_completion before any implementation work.
Remove a git worktree and its branch after PACT workflow completes. Use when: PR is merged, sub-scope work is consolidated, or manual cleanup is needed. Triggers on: worktree cleanup, remove worktree, delete worktree, branch cleanup.
| name | telegram-guide |
| description | 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. |
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):
When to use telegram_ask:
When to check replies (telegram_check_replies):
Multi-session behavior:
[ProjectName] for session identification