F5tts Monitor

v1.0.0

Monitor F5-TTS distributed training on the 9-GPU mining rig (Local-LLM) without interfering with the process.

0· 270·1 current·1 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name and description match the commands in SKILL.md (ssh to Local-LLM, run nvidia-smi, tail training logs, check free/uptime). However the skill assumes existing SSH access to a host named 'Local-LLM' and access to /mnt/toshiba/projects/F5-TTS/, neither of which are declared in the metadata as required credentials or paths.
!
Instruction Scope
Runtime instructions tell the agent to SSH into a specific host and to read a specific disk path and log file — appropriate for monitoring, but the SKILL.md also instructs the agent to 'update your HEARTBEAT.md files locally' (location and destination for these updates is unspecified) and to report to 'Master Seiya' (unclear channel). It also insists on using 'uv' for Python interaction although 'uv' is not declared or explained. These ambiguities could cause the agent to read, modify, or transmit files unexpectedly.
Install Mechanism
Instruction-only skill with no install spec or code to write to disk; low installation risk.
Credentials
The skill declares no required env vars or credentials, yet operation requires SSH access to a named host and read permissions on /mnt/toshiba/… . The absence of declared credentials is not necessarily malicious but is a gap: the agent will need SSH keys/agent or other auth, which are not described or scoped.
Persistence & Privilege
The skill is not always-enabled and does not request persistent privileges. It does instruct writing to local HEARTBEAT.md files, which is within normal monitoring behavior but should be clarified (which files, where).
What to consider before installing
This skill appears to be a simple monitoring guide, but it assumes SSH access to a host called 'Local-LLM' and write access to unspecified HEARTBEAT.md files without declaring credentials or file locations. Before installing: (1) verify you trust the Local-LLM host and that the agent's SSH identity is correctly scoped (use a dedicated key or jump host if possible); (2) confirm the intended location and recipient for HEARTBEAT.md updates and whether overwriting files is allowed; (3) check whether the 'uv' tool exists on the target and what it means in your environment; (4) run the listed commands manually once to confirm behavior and outputs. If these questions aren't answered by the skill author, treat the skill as potentially risky and avoid granting it access to your SSH keys or production hosts.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📦 Clawdis
latestvk978ejk3mp8kvn2ypackc69j8x82ajbp
270downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

F5-TTS Mining Rig Monitor Skill

This skill provides instructions for ADA to safely monitor the ongoing F5-TTS training process on the 9-GPU mining rig (Local-LLM), without interfering with the data or environment.

IMPORTANT:

  1. The training dataset and checkpoints are strictly located on the HDD of the mining rig at /mnt/toshiba/projects/F5-TTS/.
  2. Do not attempt to run training locally on asus-z170k.
  3. Use uv exclusively when interacting with the Python environment on the mining rig.

Steps to Monitor Training

1. Check GPU Utilization

To ensure all 9 GPUs are actively training and not bottlenecked or OOMed, run the following command via SSH (remember to use pseudo-terminal if using watch):

ssh Local-LLM "nvidia-smi"

You should see 9 python3 processes consistently consuming ~11GB of VRAM each.

2. Check Training Epoch Progress

Check the Accelerate training logs to see the current epoch and global step:

ssh Local-LLM "tail -n 100 /mnt/toshiba/projects/F5-TTS/outputs/training_mining_rig.log"

Look for Epoch: and Step: progression.

3. Check System RAM and CPU Load

The mining rig only has a 2-core Pentium CPU and 16GB of RAM. Make sure the system isn't buckling under the DDP overhead:

ssh Local-LLM "free -h && uptime"

4. Update the Heartbeat

After successfully probing the status, update your HEARTBEAT.md files locally to report the current Epoch, Step, GPU temperature, and estimated time remaining to Master Seiya.

Comments

Loading comments...