Memory

TinkerClaw Agent Sensei

Try it

Reference reading, not a runtime policy: a field guide of 40 lessons from running AI agents 24/7 on real tasks — ethics, messaging security, context and memory layout, configuration safety, scheduled jobs, multi-model routing, budget, bot collaboration, epistemic hygiene, and how to improve checklists over time through human-reviewed proposals. Use when the user explicitly asks to read, teach from, or compare their setup against this guide. It installs nothing, schedules nothing and writes nothing. The crons it describes are ones the human creates, and the durable memory and instruction changes they produce are drafts the human reviews before they are applied.

What it does

Agent Sensei — The Field Guide for New AI Agents

The skill document

Agent Sensei — The Field Guide for New AI Agents

A comprehensive operational manual compiled from ~6 weeks of running AI agents 24/7.

How to Use

  • New agent? Read the full guide: references/field-guide.md
  • Quick refresher? Search for the compact reference (28 rules at the bottom)
  • Specific topic? The guide is organized in 12 parts:
PartTopicSections
IEthics & Safety1–5
IIOperating Principles6–9
IIIMessaging Security10–13
IVContext & Memory14–16
VConfiguration Safety17–18
VICron Stack & Evolution19–23
VIIMulti-Model Strategy24–27
VIIIBudget & Tokens28–30
IXBot Collaboration31–32
XFork vs Vanillacomparison
XIEpistemic Hygiene33–37
XIIFractal Thinking & Self-Evolution38–40

The Core Idea

Parts I–X teach you how to operate. Part XI teaches you how to think about what you know. Part XII teaches you how to get better at everything else — automatically, across sessions, forever.

The secret: every blueprint is a META file. Read it before the task. Update it after. The next session reads the better version. Day 1: mediocre. Day 30: expert. That's not a metaphor — it's the same mechanism that makes self-improving crons work (Part VI), applied to everything.

Key Principles

  1. Access ≠ Permission. Having data doesn't mean sharing it.
  2. Read is free, send is not. When in doubt, don't send.
  3. Never be 100% sure. Hypothesis ≠ fact. Hedge when you haven't verified.
  4. Every blueprint is a META file. After using it, update it.
  5. If you're not faster after 30 days, the system isn't working. Find out why.

→ Full guide: references/field-guide.md


Credits

Created by Oscar Serra with the help of Claude (Anthropic).

The sensei your agent never had. 40 lessons. 28 rules. Because nobody else teaches an agent how to grow up.

Related skills

Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.

by Iván555 installs18 stars

Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.

by johnpatternai21 installs8 stars

Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.

by nssa.io1.0k installs47 stars

Trade crypto, manage a multi-chain wallet, and query an AI analyst from one CLI.

by lowesyang162 installs109 stars

Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.

by Iván854 installs69 stars

More from globalcaos

Browse all skills

Give your OpenClaw agent a JARVIS-style British voice with matching dry humor, audio plus a purple chat bubble in one call.

by globalcaos190 installs4 stars

Native WhatsApp channel for OpenClaw with 22 messaging/group actions plus Protocol v2 multi-agent coordination.

by globalcaos116 installs3 stars

One dashboard tracking Anthropic, Gemini, OpenAI, and Manus token usage with budget alerts and a local REST API.

by globalcaos59 installs

Stop sending 'format this JSON' to Opus. Stop sending 'cron job' to GPT. Billing-aware routing guide for choosing among the models already configured in your OpenClaw setup when assigning an agent, sub-agent or cron task — flat-rate first, metered only when justified, budget pressure respected. Not for picking models outside your configuration, and not a runtime proxy.

by globalcaos16 installs

Your agent says 'done' — but did it check? Superpowers turns any OpenClaw agent into a disciplined engineer. Verification iron law (evidence before claims), three-agent code review (build → verify spec → verify quality), systematic debugging (4-phase root cause, three-strike rule), brainstorming gates (design before code), and anti-over-engineering rules. Use when: (1) coding tasks of any complexity, (2) debugging failures, (3) about to claim work is complete, (4) spawning sub-agents, (5) planning features, (6) reviewing code. Inspired by top coding agent methodologies, adapted for OpenClaw multi-agent architecture.

by globalcaos14 installs

Read and search Outlook, inspect attachments, and create or edit drafts without any send endpoint. Uses one short-lived Microsoft Graph access token supplied on stdin for one run; it never stores credentials. Bulk mailbox export is opt-in.

by globalcaos23 installs