checkpointSave or resume session state. Use /checkpoint to save progress at session end, or /checkpoint resume to reload prior session state at session start. Triggers on "checkpoint", "save progress", "session state", "where did I leave off", "resume", "pick up where I left off".
chicoShortcut to dispatch the ChittyConnect concierge (agent: chittyagent-connect) — the canonical owner of credentials, connections, secret rotation, KV/D1 bindings, and ChittyConnect-side wiring. Triggers on "/chico", "/chico-keys", or when the user wants to invoke the concierge by its nickname. The co
chitty-cleanupFree disk space on macOS or Linux by clearing the current user's npm and pip caches (and uv's with --uv) through a guarded script that deletes nothing itself. Dry run by default. Reports, but never deletes, Homebrew, pnpm, yarn, browser caches, Trash and logs. Use when a host is low on disk.
chittyagent-canonAudits code and docs against ChittyCanon patterns: naming, P/L/T/E/A ontology, canonical URIs, frontmatter schema. Use after writing code or docs, or during review, to check canonical adherence.
chittyagent-claudeClaude-ecosystem integration: Skills, Marketplace, Desktop/web/mobile connectors, MCP servers. Use when designing or reviewing anything that connects to, through, or from Claude.
chittyagent-connectChittyConnect concierge: owns credentials, secrets, service tokens, connections, service bindings, Access/OAuth auth, MCP transports and ContextConsciousness. Use for any credential, connection, deploy-binding, deploy/publish, registry-mutation or infrastructure-change intent (sensitive-intent routi
chittyagent-olmecThe separated reviewer: judges code it did not write. Use for diff review before merge, or to run the gauntlet on a validator/gate/parser/router whose green suite you do not trust. Reports findings; never ships the fix.
chittyagent-registerGuides ChittyOS service registration: validates payloads before submission, troubleshoots registration failures, checks status, explains compliance requirements.
chittyagent-servUse this agent for the ongoing care of the chittyserv compute fleet — the portable tower of Mac Mini and Dell micro nodes plus chittyserv-vm and chittyclaw. It is the standing caretaker: it watches node reachability and address drift, Nomad raft and Serf convergence, client heartbeat health, OS and
chittyauth-token-opsChittyAuth token lifecycle operations and security audits for ChittyOS services. Use when a task involves bearer tokens, OAuth flows, token scopes, expiry/refresh/revocation behavior, service-to-service auth failures, 401/403 debugging, or validation of CHARTER/CHITTY auth contracts.
chittycontextChittyContext session persistence — capture, restore, and inspect conversation state across sessions via checkpoint/restore/status JSON files.
chittystorage-sasquatchUse this agent when working with document storage, file management, R2 buckets, content-addressing, document ingestion, classification, entity-document relationships, legal holds, file deduplication, Google Drive sync, or storage topology.
chittyxlChittyXL session manager — auto-checkpointing at token-budget intervals, Notion sync, persistent state across long sessions.
context-resumeGenerate a full accounting of the current context's accumulated knowledge, exposure, and emergent value. Synthesizes everything this context has touched into a resume-style one-sheet. Use at session end, before compaction, or when capturing context value. Triggers on "/resume", "context resume", "wh
create-actorScaffold, repair, or standardize ChittyOS Python actors under chittyentity/chittyactors/{name} using the canonical chittysdks/actor-base package and current Apify/Docker conventions. Use when creating a new ChittyActor, converting an ad hoc scraper/executor into a compliant actor, fixing actor struc
goal-creatorDrive ANY stated goal, plan, project, build, or "let's design X" intent through the ChittyOS discover→elicit→architect→adversarial→SoT→build→persist→handoff pipeline using the three-block format `[what to achieve], keep {conditions}, not met until [completion criteria]`. Use aggressively — trigger w
hygieneRepository hygiene and crash-safe work capture for any repo. Use when a session starts or ends, before or after risky git work, when a repo looks messy, when branches have piled up, or when uncommitted work needs protecting from a crash. Triggers on "hygiene", "capture my work", "wip", "is this repo
nb-development-defaultsGlobal development defaults for this operator. Use for almost all coding, debugging, ChittyOS integration, architecture, compliance, auth/token, branch-finalization, and workflow-automation tasks unless the operator explicitly overrides these defaults. Covers conditional execute-now posture, discove
reclaimClaim orphaned in-progress tasks left behind by dead Claude Code sessions. Lists unclaimed tasks from the orphan sweeper, lets you claim one, loads its context, and resumes. Triggers on "reclaim", "orphaned tasks", "dead session tasks", "/reclaim".
retrospectEvidence-grounded retrospection — reflect on a session or task, validate the reflection against ground truth (transcript, logs, artifacts), then distill to generalizable principles that travel beyond the specific context. Triggers on "retrospect", "reflect on this session", "what did we learn", "val
shipDevelopment wrap-up lifecycle — preflight, brainstorm, checkpoint, cleanup, branch Triggers on "/ship", "wrap up", "finish up", "ship it", "done for now", "close this out".
skill-creatorCreate, edit, optimize, or test Claude/Codex skills. ALWAYS use this skill — not the Anthropic `claude-plugins-official:skill-creator` — when the user asks to "create a skill", "make a skill", "build a skill", "new skill", "edit/improve/optimize a skill", "skill description", "skill eval", "test a s
skills-orchestratorUniversal skill and agent router. Searches, discovers, and executes any skill or agent in the ChittyOS ecosystem via the orchestrator MCP at orchestrator.agent.chitty.cc/mcp. Triggers on "/skills-orchestrator", "/skills", "/agents", "find skill", "find agent", "which skill", "which agent", "what can
startup-modeThe operator's standing cost-discipline posture for this self-funded phase, and the single written source for it. Load it before any decision that creates, keeps, or justifies recurring spend — provisioning or re-provisioning a database, adding a Neon project or branch, adding a metered binding or p