← 返回 Skills 市场

F5 Telegram Notify

Name: F5 Telegram Notify
Author: pbseiya

作者 pbseiya · GitHub ↗ · v1.0.0

cross-platform ⚠ suspicious

380

总下载

当前安装

版本数

在 OpenClaw 中安装

/install f5-telegram-notify

功能描述

ส่งการแจ้งเตือน Telegram เมื่อ F5-TTS training เสร็จหรือล้มเหลว ใช้สำหรับ Docker environment

使用说明 (SKILL.md)

F5-Telegram-Notify Skill

สคริปต์สำหรับส่งการแจ้งเตือน Telegram เมื่อ F5-TTS training process เสร็จสิ้นหรือล้มเหลว

การใช้งาน

1. ส่งแจ้งเตือนสำเร็จ

node /home/seiya/projects/openclaw/workspace/skills/f5-telegram-notify/scripts/notify.mjs success "Training เสร็จแล้ว!" "model_name" "/path/to/checkpoint"

2. ส่งแจ้งเตือนล้มเหลว

node /home/seiya/projects/openclaw/workspace/skills/f5-telegram-notify/scripts/notify.mjs error "Training ล้มเหลว: CUDA out of memory" "model_name"

3. ส่งแจ้งเตือนเริ่ม training

node /home/seiya/projects/openclaw/workspace/skills/f5-telegram-notify/scripts/notify.mjs start "เริ่ม training แล้ว" "model_name"

พารามิเตอร์

status: success | error | start
message: ข้อความที่ต้องการส่ง
model_name: ชื่อโมเดล (optional)
checkpoint_path: Path ไปยัง checkpoint (optional, สำหรับ success)

Config Required

ต้องมีไฟล์ .env ที่มี:

TELEGRAM_BOT_TOKEN=your_bot_token
TELEGRAM_CHAT_ID=your_chat_id

โครงสร้างไฟล์

f5-telegram-notify/
├── SKILL.md
├── scripts/
│   └── notify.mjs
└── README.md

安全使用建议

Do not run these scripts without reviewing and editing them. Specific recommendations: - Remove or replace the hard-coded TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in docker_notify.sh and notify.sh before use; supply your own token/chat via environment variables or a local .env under your control. - Assume failure notifications may include snippets of training logs and the command used; inspect docker_train.sh and train_with_notify.sh and remove or sanitize any log or command text you do not want sent externally. - Modify notify.mjs's loadEnv paths so it only reads .env from an explicit, expected location (and not an absolute path to someone else's project). Prefer to rely on environment variables rather than auto-loading arbitrary files. - Rotate any Telegram token that may have been exposed in repositories or CI, and verify ownership of the bot/chat before trusting notifications. - Test in an isolated environment with no sensitive data to confirm behavior, and consider implementing an explicit opt-in configuration (no defaults that point to a third-party account). Given the embedded credentials and log-sending behavior, treat this skill as potentially leaking data until you sanitize and reconfigure it.

功能分析

Type: OpenClaw Skill Name: f5-telegram-notify Version: 1.0.0 The skill contains hardcoded Telegram Bot credentials and a specific Chat ID (6729022410) in scripts/notify.sh and scripts/docker_notify.sh, which causes training status, model names, and log snippets to be sent to an external party by default if environment variables are not set. Additionally, scripts/notify.mjs and SKILL.md reference hardcoded absolute paths to a specific user's home directory (/home/seiya/...), and scripts/docker_train.sh is designed to exfiltrate the last 50 lines of training logs to Telegram upon failure. While these behaviors may be due to poor development practices rather than overt malice, they present a high risk of data exfiltration and privacy leaks.

能力评估

⚠ Purpose & Capability

Name/description match the code (notification around F5-TTS training). However the registry metadata declares no required env vars/credentials while the SKILL.md and scripts clearly require TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID — a mismatch. Also SKILL.md and scripts reference absolute developer paths (e.g. /home/seiya/...), which are environment-specific and surprising for a generic skill.

⚠ Instruction Scope

Runtime instructions and scripts will read .env files from multiple locations (including an absolute project path) and, on failure, collect and send the last ~50 lines of training logs ($LAST_LOG) in docker_train.sh and command/exit info in train_with_notify.sh. That means runtime behavior can transmit local log contents and command-line context to the Telegram account controlled by the token — which is broader than a simple 'notify success/failure' if those logs/commands contain sensitive data.

✓ Install Mechanism

No install spec and no downloads; this is an instruction + script bundle only, which reduces installation risk. The code runs local shell and Node.js but does not install external packages automatically.

⚠ Credentials

The skill legitimately needs TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID, but the registry metadata did not declare them (incoherent). More importantly, the scripts include hard-coded default values for these variables (e.g. TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID embedded in docker_notify.sh and notify.sh). If a user does not supply their own env vars, notifications (including potentially large log excerpts) will be sent to the embedded bot/chat controlled by whoever published the skill, which risks leaking local information.

✓ Persistence & Privilege

The skill does not request always:true, does not modify other skills, and does not require elevated system privileges. It runs only when invoked via the provided scripts.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install f5-telegram-notify
安装完成后，直接呼叫该 Skill 的名称或使用 /f5-telegram-notify 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

v1.0.0

Initial release of f5-telegram-notify. - Sends Telegram notifications when F5-TTS training completes or fails. - Supports notification for start, success, and error events. - Designed for use in Docker environments. - Requires TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in a .env file. - Includes a command-line script for customizable message sending.

元数据

Slug f5-telegram-notify

版本 1.0.0

许可证 —

累计安装 1

当前安装数 1

历史版本数 1

常见问题