CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/nanoclaw-host

Skills and rules for the NanoClaw host agent (Claude Code on Mac). Tile promotion, container management, staging checks, repo chain safety, and public sync.

77

Quality

97%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

staging-diff-protocol.mdrules/

alwaysApply:
Yes

Staging Diff Protocol

The protocol

Before making ANY judgment about staging content:

  1. Diff the staging version against the current plugin version
  2. Read every change
  3. Reason about what the changes do: improvements? new features? bug fixes? different approaches to the same problem?
  4. Merge improvements into the plugin version when staging is better in some aspects and plugin is better in others
  5. Only then decide: promote as-is, merge and promote, or request changes

The diff command

ssh -n "$NAS_HOST" "cat <staging-path>" | diff - <local-tile-path>

What "stale" means

"Stale" means the diff is empty — literally zero changes. Everything else requires reasoning. A file with the same name may have significant improvements that the plugin version doesn't have. Never declare content "already promoted" based on the filename or timestamp.

rules

boyscout-host.md

copilot-nudge-after-10min.md

cross-tier-skill-state.md

dual-agent-coexistence.md

host-conventions.md

no-deferral.md

no-error-suppression.md

nuke-semantics.md

orchestrator-dep-refresh.md

overlay-tile-authoring.md

post-merge-publish-watch.md

repo-chain.md

staging-diff-protocol.md

tessl-version-floating.md

tile-content-pipeline.md

README.md

tile.json