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
The runtime mount layout is authoritative. Follow container-trust-levels for EROFS and ground-truth-trusted for Google verification boundaries. This reference describes capabilities, not permission to bypass a skill's read-only contract.
/workspace/trusted/ shared memory.google-ops skill on both main and trusted. The OneCLI gateway injects Google authorization; no container credential fallback is permitted./workspace/store writable for main/trusted; mount writability does not authorize reader mutations. See messages-db-schema.md for the shipped reader contracts./workspace/trusted/ mount.access_restricted; no host scripts or auto-memory./tmp tmpfs.Evidence pinned to jbaruch/nanoclaw commit ef8cf4d6837427f8924deda83b7af00c215996fc:
buildVolumeMounts group/trusted/store mounts, skill materialization, auto-memory.selectTiles baseline plugins.IDLE_TIMEOUT is 1800000 ms (30 minutes). Inspect effective runtime configuration rather than assuming a tier-specific idle timeout.Check the running host revision and update this reference alongside changes to these sources.
.tessl-plugin
rules
skills