Third Brain V8.1 Skills

Third Brain V8.1 Skills

<p align="center"> <img src="assets/third-brain-v8.1-actual-system-architecture.png" alt="Third Brain V8.1 actual Codex OS architecture: Codex host, repository control plane, transactional worker runtime, live Obsidian Vault, verification evidence, and declared debt" width="900"> </p>

Verification-first Agent Skills for Codex OS, with optional compatibility adapters for Claude Code, Gemini, Cursor, and Windsurf. Build a persistent knowledge operating system with Obsidian provenance, scheduled loops, bounded static dependency graphs, context management, and multi-agent orchestration.

Install 21 reusable agent skills for ingesting sources, auditing workflows, compiling interlinked wikis, running daily knowledge loops, verifying claims before shipping, managing token costs, engineering bounded loops and static dependency graphs, and orchestrating multi-agent teams.

Use this if:

• Your AI agent keeps forgetting context between sessions

• You want to enforce verification gates before "done" claims

• You need to structure knowledge as linked pages (like Obsidian) instead of scattered chat history

• You're building agent workflows that should learn and compound over time

• You want Obsidian wiki knowledge to update skills, SOPs, schemas, and automation through supervised promotion gates

Image: GitHub stars Image: License: MIT Image: Codex OS Image: Claude Code Image: Cursor Image: PRs Welcome

Quick Start

1. Clone & Install

git clone https://github.com/Mark393295827/third-brain-v5-skills.git
cd third-brain-v5-skills
bash install.sh codex  # Codex is the primary host/kernel

Windows PowerShell uses .\install.ps1 codex. Compatibility adapters require an explicit non-Codex target.

2. Try a Skill

Paste this into Codex:

Use wiki-ingest on this source. Stage an immutable source, author a governed concept candidate, plan navigation updates, and return a verification summary. Treat entity authoring as a separate reviewed capability.

Then paste a URL, article, PDF text, or any source you want to capture.

3. Next Steps

See the 3-Minute Quickstart for a complete walkthrough.

Full guide: GUIDE.md

Command centre and distribution: V8.1 Codex Agentic OS command centre. Start it with python tools/agentic_os_server.py --state-root .agentic-os-state; the host is localhost-only by default and requires T02 runtime receipts. Claude/Gemini/Cursor/Windsurf remain compatibility adapters, not the primary runtime.

中文历史进阶手册：V7 最大潜力使用手册（参考）

🔥 V8.1 多智能体 Worker 流水线手册 & Worker Flows 规范：事务式流水线（Stage → Author → Graph Plan → Govern → Commit/Postcheck → optional Deliverable），归档只发生在验证提交之后。

The Problem

V8.1 Operating Model

V8.1 keeps the wiki as durable disk and governance, gives every skill a profile-aware execution contract, and makes python -m tools.worker_flow.cli the only canonical transactional runtime:

Input -> Source -> Wiki compile -> Daily loop -> Agent/Wiki flywheel -> Skill/SOP upgrade -> Verification

The upgrade adds seven hard defaults:

• Profiles match risk: one-shot, stateful, loop, and high-risk work load only the controls they need.

• Source provenance stays immutable: raw source notes and block refs remain the audit layer.

• Loops have contracts: Trigger -> Execute -> Verify -> State, with budgets and recovery.

• Context is zero-overhead by default: hot paths load only what the task needs.

• Automation is bounded: scans and queues can run unattended; semantic writes stay supervised.

• Teams need ownership: multi-agent work requires write scopes, IPC, join gates, cleanup, and evidence.

• Rules promote through evidence: wiki insights become schema or skill rules only after repeated support and a cheap check.

See the V8.1 Worker Flow, the Agent Skills standard, and the historical V7 release notes.

V8.1 keeps graph-engineering bounded to static DAGs; dynamic expansion and cyclic graphs remain out of scope.

Core Skills (Start Here)

🧠 Knowledge & Verification

📅 Daily Loop

🎯 Behavior & Creativity

🔬 Research & Quality

📊 Context & Engineering

Complete Skill List

📥 Ingestion & Knowledge

• wiki-ingest — Stage immutable sources, author governed concept candidates, plan graph updates, and hand off optional entity authoring for separate review

• knowledge-ops — Multi-layer knowledge management: classify, deduplicate, preserve evidence hierarchy, vector + Markdown retrieval

• wiki-lint — Health check: P0/P1 graph health, frontmatter, source refs, wikilink density, provenance debt

🔄 Daily Workflow

• daily-okr — 7-KR evidence cycle with minimum-day degradation and durable closeout

• cognitive-compile — 8-section framework: Question → Facts → Concepts → Pattern Recognition → Conflict Detection → Hypothesis Generation

🎨 Behavior & Creativity

• behavior-design — Outcome → minimum behavior → cue → SOP → evidence → review

• creativity-engine — Mechanism-diverse combinations, scoring, and falsifiable minimum tests

🔬 Research & Quality

• deep-research — STOW-compatible research harness, evidence trails, source/claim ledgers

• verify-before-claim — Fresh scope-matched evidence, independent checks, approval, rollback

🔄 Learning & Flow

• session-learn — 7 signal types: concepts, entities, corrections, patterns, ideas, decisions, gaps

• project-flow-ops — Execution flow: triage, plan, track, review across projects

📊 Context

• context-manager — Runtime budgets, checkpoint replay, compaction, retrieval, capability routing

Utility command: commands/token-cost-tracker.md estimates, logs, and reports token usage; it is not one of the 21 Agent Skills.

🏗️ Engineering

• loop-engineering — Temporal depth through bounded loop contracts, independent verification, finite budgets, and stop/recovery rules

• graph-engineering — Dependency width through bounded static DAGs, explicit branches, typed joins, and node-local recovery

• agentic-engineering — Spec-driven macro actions, quality ceilings, verification gates, state checks

• harness-engineering — Runtime scheduler, permissions, system-call tools, delegated gates, provenance, observability

• agent-teams-command — Multi-agent process ownership, IPC, integration, async budgets, and evidence gates

💼 Strategy & Operations

• startup-evaluation — Startup health: entrepreneurship, VC 5T, PMF, runway, team, unit economics

• anthropic-os — Governed operating-system experiments: Four-C, 3B, prediction errors, permission ladder

• ai-six-sigma-property-os — AI + Ontology + DMAIC for property work orders, dispatch, quotes, evidence

How These Skills Fit Together

                        LLM (CPU) + Context (RAM) + Wiki (Disk)

External Sources ──→ wiki-ingest + knowledge-ops ──→ Knowledge Layers
                            ↓
                    Daily Loop (daily-okr)
                    /    /    \    \    \
               Input  Cognition  Wiki  Behavior  Creativity
                            |
                        Output → Feedback
                            ↓
                    session-learn (extract patterns)
                            ↓
                    verify-before-claim (quality gate)
                             ↓
             Loop depth / Graph dependency width
                             ↓
                Multi-agent teams (agent-teams-command)

The system is a closed loop: ingest sources → process daily → extract learning → verify claims → promote rules → scale to teams.

Architecture & Design

Third Brain V8.1 treats agents as LLM OS processes:

• LLM = CPU

• Context = RAM

• Wiki/Obsidian = Disk

• Tools = System calls

• Skills = Executable programs

• Harness = Kernel

• Agent teams = Processes

Design Layers

Engineering boundaries are deliberate: Loop Engineering controls temporal depth; Graph Engineering controls dependency width; Agent Teams Command controls process ownership, IPC, and integration; Harness Engineering supplies the runtime scheduler, permissions, and observability. A graph node may contain a Loop or Agent Team, but V8.1 does not support dynamic or cyclic graphs.

Skill Adoption Path

Start small. Add skills as you need them.

Installation

For Codex CLI (Primary host/kernel)

# Personal skills (available across all projects)
bash install.sh codex

For Cursor

bash install.sh cursor

For Windsurf

bash install.sh windsurf

Compatibility adapters: Claude Code / Gemini CLI

bash install.sh claude
bash install.sh gemini

Full guide: GUIDE.md

Example Workflows

Each workflow is copyable into your agent. See examples/ for complete, verified examples:

• 3-minute quickstart — Fastest path to useful output

• Research PDF to wiki — Turn a source into linked pages

• Verified code session — Use verification gates before claiming a fix

• Daily knowledge loop — Run a compact daily OKR workflow

• Startup evaluation sprint — Turn an idea into validated assumptions

Wiki Structure

Skills default to STOW paths (configurable via system/config.md):

sources/          ← Immutable source notes (articles, PDFs, transcripts)
wiki/
├── concepts/     ← 13 contracted domains
├── entities/     ← people, companies, funds-investors, products, orgs
└── outputs/      ← gmail-digests, evaluations, compilations
maps/
├── domain-mocs/
├── system-indexes/
├── project-maps/
└── canvases/
system/           ← Deployed contracts, config, schema, templates, runs

Tools & References

What This Is NOT

• Not a chat wrapper. Skills are executable prompts that agents follow; they're not productivity theater.

• Not a productivity tool with 100 metrics. Daily OKR has seven causally linked KRs with evidence.

• Not an all-in-one framework. Pick skills incrementally. You don't need all 20 to start.

• Not prescriptive. Adapt paths, frontmatter, and skill triggers to your workflow.

Philosophy

Three core principles:

1. Verification first: No "done" without proof. No claims without evidence. Expected value over confidence.

2. Knowledge compounds: Every session should improve the wiki, not scatter across chat history.

3. Closed loops: Ingest → Process → Learn → Scale → Verify. No loose ends.

Related Work

• Agent Skills Format — Open specification for agent skills

• llm-wiki-agent — Original STOW pattern implementation by SamurAIGPT

• Karpathy LLM OS — Conceptual framework

Contributing

Bug reports, skill improvements, and PRs are welcome. See CONTRIBUTING.md and CHANGELOG.md.

License

MIT — see LICENSE.

Transparency Note

This project includes growth and outreach tools (in tools/ and outreach/) designed to help the repository reach users via GitHub search and Awesome lists. These tools are optional, dry-run-by-default, and separate from the core skills. If you're installing skills for your own workflow, you don't need them.

The skill frameworks and philosophy are genuine. Use what works for you; ignore what doesn't.