Agent skill
notify-telegram
Enable Telegram notifications for this Claude Code session. Use when the user runs /notify-telegram or wants to be notified on their phone when Claude finishes tasks.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/notify-telegram
SKILL.md
Enable Telegram Notifications
Register this session for Telegram notifications when tasks complete.
Quick Start
Run the registration script with your label:
~/.claude/skills/notify-telegram/register.sh "$ARGUMENTS"
Replace $ARGUMENTS with the label (e.g., "myproject"). If empty, uses current directory name.
What This Does
- Finds current session ID from transcript file
- Registers session with webhook daemon (
/session-start) - Enables notifications (
/sessions/enable-notify) - Creates
~/.claude/runtime/sessions/<id>/notify_labelfor hooks - Registers with nvim if running in nvim terminal
Prerequisites
The webhook daemon must be running on port 4731:
curl -s http://localhost:4731/health
If not running, start it (on devbox):
cd ~/projects/claude-code-remote && node start-telegram-webhook.js
Verification
After registration, confirm:
curl -s http://localhost:4731/sessions | jq '.sessions[] | {label, session_id}'
Troubleshooting
"Session not found": The daemon needs the session registered first. The script handles this, but if it fails, manually register:
curl -s -X POST http://localhost:4731/session-start \
-H "Content-Type: application/json" \
-d '{"session_id": "<ID>", "cwd": "'$PWD'"}'
Daemon not running: Check lsof -i :4731. Start it if needed.
Can't find session ID: Look for most recent transcript:
ls -lt ~/.claude/projects/-$(pwd | tr '/' '-')/*.jsonl | head -1
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?