Rules for trusted NanoClaw groups. Shared memory, session bootstrap, cross-group memory updates. Loaded for trusted and main containers only.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Process steps in order. Do not skip ahead.
Read-only counterpart to admin's tessl__heartbeat's system-health probe. Trusted tier sees the orchestrator's SQLite directly but does not have admin's filesystem / IPC / container mounts and does not manage the dismiss file at /workspace/group/system-health-dismissed.json.
For direct messages.db queries or column references, first read /home/node/.claude/skills/tessl__system-status/references/messages-db-schema.md in this installed plugin. It carries table shapes and reader fields; rules/messages-db-schema.md owns query, mutation, and schema-drift requirements.
python3 /home/node/.claude/skills/tessl__system-status/scripts/system-status-checks.pyOutput is a single JSON object on stdout: {checked_at, db_path, stuck_tasks, stuck_count, row_counts, db_size_mb, recent_failures, alerts}. Exit 0 = checks ran (alerts may or may not be populated). Exit 1 = DB unreachable or every check raised; the JSON still emits with alerts describing what failed.
Parse the JSON.
alerts is empty → silent success. Output nothing.alerts is non-empty → report via mcp__nanoclaw__send_message. Include the items the alert refers to: stuck_tasks IDs + prompt previews, recent_failures task IDs + error summaries, the offending row counts or DB size.This skill is read-only and must not auto-fix the database. The orchestrator's scheduler retries stuck tasks on the next poll; if alerts persist across cycles, flag for the operator.
/workspace/group/system-health-dismissed.json. That file is admin's domain (per tessl__heartbeat's system-health step). Trusted reports verbatim; the operator decides what to do.heartbeat-checks.py..tessl-plugin
rules
skills