Claude Guardian is an all-in-one Claude account safety and risk prevention skill. It intelligently assesses your device, account history, network environment, and payment options, then provides person
Agent Skills that teach coding agents to write, review, and port idiomatic Rust, plus a tested clippy config. Works with Claude Code, Codex, Copilot, Cursor, and Gemini CLI.
video-talkcraft 口播視頻動效庫：108 張動效配方卡線上預覽——動態字卡、資料鏡頭、證據巡遊、運動承接轉場。108 motion recipe cards for voiceover-driven explainer videos — an agent skill for Claude Code / Codex, rendered with Remotion.
A starter kit for running Claude Code as a second brain + working assistant, from
Palo Alto AI Research Lab.
This is the system we run ourselves every day — stripped of personal data and cut down to a
portable core: the method, not the data.
Why take the whole thing, not one skill
A second brain and persistent memory for Claude Code and Codex: 234 skills shipped as a
plugin marketplace, a memory server you can attach with one manifest, a working CRM engine and
vault templates. It is the system Palo Alto AI Research Lab runs
every day, stripped of personal data and cut down to a portable core: the method, not the data.
Pick your door:
New to this? Start with the light onboarding guide. Download a folder,
open it in Claude Code or Codex, and try one useful task. No terminal, GitHub account, shared
vault, sync service, or background updater is needed; your work stays in a separate local folder.
Already have an Obsidian vault? Take the habits that keep it from rotting without the rest:
the concept template with a maintained_by: human flag so agents
never rewrite your notes, three read-only subagents that review and propose,
and the contract for unattended runs.
Already running agents across machines? Read HANDOVER.md: a snapshot of the
whole system and a map of our repos, written for you and your model.
Later: the full kit after your first useful task
This is an optional next stage. First-time users should finish the light route
before installing the full kit below.
A single skill is a trick. What makes an agent useful over months is the set of habits around it:
a gate that refuses to say "done" without evidence, a retrospective that files what you learned
where the next session will actually find it, a registry of decisions you already rejected so
nobody re-pitches them, a handoff that survives a crash. Those only work together, which is why
they ship as one kit rather than as 234 separate downloads.
Install it whole and you get a working second brain on day one:
Want the agent to remember across sessions? Memory is a separate, opt-in plugin in the same
marketplace, because its embeddings stack downloads about 2 GB on first start:
/plugin install second-brain-memory@second-brain
It registers the sqlite-graph-memory MCP
server (sgm-mcp) and asks for one setting, the index folder (BRAIN_INDEX_DIR) you built with
uvx --from 'sqlite-graph-memory[embeddings]' sgm-index <your notes folder>.
It is MIT, it costs nothing, and nothing here phones home. Take what you need, delete the rest,
and open an issue if a skill breaks on your machine. Paths are documented in
docs/PATHS.md.
Onboarding a whole machine
Setting up a brand-new computer, not just adding skills? There is a full runbook a fresh
Claude Code session can execute end to end, the human says one sentence, the agent does the rest:
joining an existing fleet as a trusted family node (sync, shared memory, message bus) →
ONBOARDING-FAMILY.md, method only; fleet coordinates travel over the
encrypted sync channel after the owner approves the device, never through this repo.
Start here: 25 skills worth your first hour
Every one of them ran in production before it was published. One command each.
The opening message for your FIRST Claude Code session (English / Russian), everything starts here
BOOTSTRAP-CLAUDE.md
Instructions for Claude itself: how to install and adapt the kit
CLAUDE-EXTERNAL.md
Our working principles (assistant behavior), the base for your own CLAUDE.md
skills/
All 234 skill commands the system runs on every day, map: skills/INDEX.md. Personal data in examples is replaced with fictional stand-ins (how exactly)
Or via skills.sh (works for Claude Code, Codex, Cursor, Gemini CLI and any other agent that speaks the Agent Skills format):
npx skills add tonydzi/second-brain-starter-kit
Quick start (10 minutes)
A Claude Pro or Max subscription → install Claude Code:
npm install -g @anthropic-ai/claude-code (no npm? Mac: brew install node, Windows: nodejs.org).
Run claude and log in with your subscription.
Install Obsidian, to look at your second brain with your own eyes.
Open SEED.en.md, put your name in, and paste the text as the first message to Claude Code.
Claude takes it from there, following BOOTSTRAP-CLAUDE.md. (Russian version: SEED.md.)
A second brain = stop losing what's useful. Every decision, agreement and idea → a note in
the vault, linked into the graph.
AK-47 rule: the simplest solution the owner can repair themselves.
Receipts: the assistant proves it saved something ("recorded X → note Y") instead of saying
"understood".
A routine repeated twice becomes a skill, a /name command.
Privacy: everything lives locally on your machine; money, deletion and anything leaving the
house happen only on your explicit OK.
Roadmap
Now: v0.9.0.
234 skills, 247 engine scripts under engines/, note templates, a CRM engine with warmth
scoring and safe outbound, SEED.md + BOOTSTRAP-CLAUDE.md for the first session, and
HANDOVER.md for people who already run their own agent fleet.
Next, in the order we would take it ourselves:
Try the 30-minute onboarding route through the shipped rules,
skills, engines, templates and CRM demo; report any step that does not work on your machine.
A "clone it and it works" check on someone else's machine. Right now the only proof is that we
use this ourselves every day. That is usage, not a test: no third-party machine has ever been seen.
Localized READMEs for non-English venues (Chinese, Japanese, Korean, Spanish), the skill
bodies stay English, the docs get localized.
Every notable change ships as a release, so the
releases feed is an honest record of
what is actually in the kit, unlike a commit history.
Which AI worked here
This project is built by a human + AI team, and the commit history shows it: Claude writes most of
the code, Codex and Grok review it, Gemini brings research. A model is credited in a commit only
if its output actually changed that commit's content, no decorative signatures. Lab-wide rule:
AI-CONTRIBUTORS.md.
License and provenance
The method is open, take it, adapt it, share it. There are no secrets and no personal data in the
kit (it goes through an automated secret scanner). Questions and ideas → Issues.
Get in touch
Questions, war stories, or you want to run this yourself:
Issues labelled accepted are scoped, free to take, and nobody is on them.
Comment "claiming this", no permission needed, and it is yours for 7 days.
New here? Start with good first issue.
You keep the copyright to your code. No CLA, no assignment, ever, your contribution goes
in under this repo's existing license, the same terms as ours. We answer every issue and PR
within 48 hours, including "no, and here is why"; our silence is our bug, so ping the thread.
Live on a platform we do not use daily (Codex, Cursor, Gemini CLI, Windows and others)? Own it:
PLATFORMS.md lists who owns what, and the pinned issue
#10 "Own a platform" is where you
claim one. How we review and credit contributions in this repo: CONTRIBUTING.md.
🧩 One piece of a working system
This repository is one piece lifted out of a live operation: one engineer running a fleet of
machines, built with Claude as implementation collaborator; the machines reach consensus with
each other and wake the human only for money or the irreversible. It was extracted after it
survived production, not written as a demo, and it runs on its own: nothing here phones home
to the rest.
Built and battle-tested at Palo Alto AI Research Lab, a fleet of Claude Code machines
running 24/7 as a second brain and synthetic cofounder. Every skill here survived real
production use before publication.
🧪 Engineers: want to test-drive this setup? Message me, I hand out free starter seeds to engineers who test and report back. Custom skill requests welcome.
READ THIS WITH AI
One click and an agent reads the repo, pulls out the patterns and helps you apply them to your own work.
Read this repo: https://github.com/tonydzi/second-brain-starter-kit (“second-brain-starter-kit” - Claude Code as a second brain: 234 battle-tested skills, a working CRM engine, vault templates and the handover map. Method, not data. MIT). Work out what problem it actually solves, pull out the reusable patterns and help me apply them to my own setup. Start by asking what I am working on.
, TonyDzi, Palo Alto AI Research Lab · second brain, agent coordination, persistent memory: github.com/tonydzi
