agentic-os
OfficialBuild persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.
What this skill does
When applied, it prepends a system prompt before your request is sent — no extra calls and no change to how you are billed beyond the added tokens.
--- name: agentic-os description: Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. origin: ECC --- # Agentic OS Treat Claude Code as a persistent runtime / operating system rather than a chat session. This skill codifies the architecture used by production agentic setups: a kernel config that routes tasks to specialist agents, persistent file-based memory, scheduled automation, and a JSON/markdown data layer. ## When to Activate - Building a multi-agent workflow inside Claude Code - Setting up persistent Claude Code automation that survives session restarts - Creating a "personal OS" or "agentic OS" for recurring tasks - User says "agentic OS", "personal OS", "multi-agent", "agent coordinator", "persistent agent" - Structuring long-running projects where context must survive across sessions ## Architecture Overview The Agentic OS has four layers. Each layer is a directory in your project root. ``` project-root/ ├── CLAUDE.md # Kernel: identity, routing rules, agent registry ├── agents/ # Specialist agent definitions (markdown prompts) ├── .claude/commands/ # Slash commands: user-facing CLI ├── scripts/ # Daemon scripts: scheduled or event-driven tasks └── data/ # State: JSON/markdown filesystem, no external DB ``` ### Layer Responsibilities | Layer | Purpose | Persistence | |---|---|---| | Kernel (`CLAUDE.md`) | Identity, routing, model policies, agent registry | Git-tracked | | Agents (`agents/`) | Specialist identities with scoped tools and memory | Git-tracked | | Commands (`.claude/commands/`) | User-facing slash commands (`/daily-sync`, `/outreach`) | Git-tracked | | Scripts (`scripts/`) | Python/JS daemons triggered by cron or webhooks | Git-tracked | | State (`data/`) | Append-only logs, project state, decision records | Git-ignored or tracked
Use this skill
Add a "skill" field with the skill’s ID to your chat completion request. It is applied server-side before your prompt is sent — no extra calls.
{
"model": "gpt-4o-mini",
"skill": "imp-00781a12-648d-4737-bb5f-cf3680e1e1bb",
"messages": [{ "role": "user", "content": "…" }]
}Install the skill, enable it in your dashboard and (optionally) limit it to specific models. It then applies automatically to every matching request — with no "skill" field to send each time.
Set it up in your dashboardMore skills
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search and analyze your own session logs (older/parent conversations) using jq.
Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.
List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.
Create, search, and manage Bear notes via grizzly CLI.