FelixKruger

Always On Agent Playbook — AI skill for Claude Code

AI community

A skill for Claude Code (or any agent that reads skills) that teaches how to build a personal AI agent that’s always on and still trustworthy.

How to install Always On Agent Playbook

This entry records only its repository, not the path inside it, so there is no exact command to give. Open FelixKruger/Always-On-Agent-Playbook and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Always On Agent Playbook does

A skill for Claude Code (or any agent that reads skills) that teaches how to build a personal AI agent that’s always on and still trustworthy. Something that runs 24/7, remembers what matters, works in the background, and doesn’t spam you or make things up.

Alternatives in AI

  • Iai Personal Memory Engine — A cyber brain for your AI 866 ★
  • Daymon — Daymon puts your favorite AI to work 24/7. It schedules, remembers, and orchestrates your own virtual team 372 ★
  • Unofficial Claude Code Prompt Playbook — Unofficial playbook for production-grade LLM system prompt architecture, derived from local analysis of Claude 258 ★

README

always-on-agent-playbook

A skill for Claude Code (or any agent that reads skills) that teaches how to build a personal AI agent that’s always on and still trustworthy. Something that runs 24/7, remembers what matters, works in the background, and doesn’t spam you or make things up.

It comes from two places. The first is the architecture Lee Robinson laid out in his Stanford CS146S lecture on always-on agents (October 2026). His ideas are restated here, not copied. The second is METI, my own agent. METI runs on one Windows PC with zero dependencies, talks to me on Telegram, and routes real work into coding sessions I can watch. When the lecture and METI’s real failures disagreed, the failures won.

What it covers:

  • Seven laws to write before any code: nothing fails silently, no invented facts in your notes, one unprompted message a day, never report a step that didn’t happen.
  • The shape: a server-side loop, state kept in plain files, a thin chat front door, and “hands” behind a deterministic guard.
  • Memory in layers, the cheapest first: a profile in your own words, a dated log, what’s in flight right now, and search for everything else.
  • A context budget you can measure, plus safety rules that block things outright instead of asking a second model for an opinion.
  • The eval flywheel: every real miss becomes a failing test before the fix.
  • Visible work: tasks dropped into your own sessions, so you watch it happen.
  • A gatekeeper for partner agents from other vendors: answer, don’t dump.

There’s also a 10-stage build order, and a list of what killed my five earlier attempts.

Install

Copy this folder into your skills directory, for example `~/.claude/skills/always-on-agent-playbook/`. The skill triggers when you're designing or building an always-on or proactive personal agent, deciding what it should remember or when it should speak, or wiring two agents together.

Contents