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
sqlite3 with URI file:/workspace/store/messages.db?mode=ro and uri=True for reads; the standalone sqlite3 CLI is absent./home/node/.claude/skills/tessl__system-status/references/messages-db-schema.md.PRAGMA table_info(<table>); never guess column names.trigger_pattern, not trigger_word or trigger.registered_groups uses jid, not chat_jid; trusted lives in container_config JSON.last_result belongs to scheduled_tasks; task_run_logs uses status, result, error.messages has composite PK (id, chat_jid).sessions has composite PK (group_folder, session_name). Scope session lookups by both host-supplied NANOCLAW_GROUP_FOLDER and NANOCLAW_SESSION_NAME; missing identity means unavailable, never an arbitrary row.tz_state is a singleton (id = 1); other PKs and lookup values are in the inventory.task_run_logs.run_at against matching ISO-8601 T/Z strings, never SQLite datetime(...) output.chat_status, inspect_gate_decisions, get_scheduled_tasks) over raw SQL.follow_me_tasks writes require BEGIN IMMEDIATE per nanoclaw-admin: follow-me-two-phase-lock..tessl-plugin
rules
skills