CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/nanoclaw-core

Core behavioral rules and skills for NanoClaw personal assistant agents. Always-on rules for communication, verification, memory, and formatting.

70

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

jbaruch/nanoclaw-core

tessl

Core behavioral rules and skills for NanoClaw personal assistant agents. Always-on rules for communication, verification, memory, and formatting.

Installation

tessl install jbaruch/nanoclaw-core

Rules

RuleScopeSummary
core-behavioralways-onBaseline conversational behavior — concise replies, no trailing summaries
telegram-protocolalways-onTelegram-channel formatting and reply conventions
language-matchingalways-onMatch the user's language; don't volunteer translations
default-silencealways-onSilent-on-no-news as the default; surface only what's actionable
temporal-awarenessalways-onConvert relative dates, respect timezones, never schedule reminders for the past
ground-truthalways-onLive source > cached/recalled state; always verify before acting
read-full-contentalways-onRead full email/message bodies, never just snippets/previews
context-recoveryalways-onRecover from compaction by reading state, not by claiming lost context. Includes post-compaction skill-block disambiguation (history vs new tasks)
post-compaction-trustalways-onCompaction summaries are trusted state; do not re-derive what's already there
tone-matchingalways-onMirror the user's register; tone shifts signal mode shifts
query-size-limitsalways-onBounded SQL/API queries; never SELECT * on large tables
progress-updatesconditionalBrief updates at key moments; silence is not a failure

Skills

SkillDescription
statusOne-line status emit on a defined cadence
query-historySearch messages.db by keyword and/or sender; companion to context-recovery

Philosophy

  • Always on. Every rule is alwaysApply: true. The agent follows these conventions without being prompted.
  • One concern per rule. Each file covers one topic so projects can override surgically without throwing out the whole tile.
  • Behavior, not domain. These are conversational and verification baselines — anything domain-specific (CFPs, calendar, email) lives in nanoclaw-admin.
  • Hint, not authority for state. Cached state is a recall hint; verify against the live source before acting on it (see ground-truth).

See CHANGELOG.md for version history.

Workspace
jbaruch
Visibility
Public
Created
Last updated
Publish Source
GitHub
Badge
jbaruch/nanoclaw-core badge