CAO Session Liveness

CAO Session Liveness is an AI Engineering skill for Claude Code, published by awslabs in cli-agent-orchestrator.

1.1K stars226 forkson awslabs/cli-agent-orchestratorAdded 2026/08/21+1% in starsRepository updated 2026/08/21

agent-orchestrationai-agentsai-coding-assistantantigravityclaude-codecodexcopilot-clicursor-clideveloper-toolshermeskimi-clikiromcpmodel-context-protocolmulti-agent-systemsopencodeorchestrationpythontmux

Install in seconds

Install CAO Session Liveness

Copy CAO Session Liveness into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/awslabs/cli-agent-orchestrator/tree/main/skills/cao-session-liveness ~/.claude/skills/cao-session-liveness

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/awslabs/cli-agent-orchestrator.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/cao-session-liveness/SKILL.md in awslabs/cli-agent-orchestrator
Installs to: ~/.claude/skills/cao-session-liveness
Collection: One of 18 skills cataloged from this repository
Category: AI Engineering — 2451 skills

What CAO Session Liveness does

CAO Session Liveness verifies whether a CAO session is truly running by comparing terminal status with the latest output. Use it when a session may have exited, stalled, or been misreported as active.

CAO Session Liveness is cataloged under AI Engineering on DirSkills. CAO Session Liveness comes from a repository tagged agent-orchestration, ai-agents, ai-coding-assistant, antigravity and claude-code.

Documentation

README

Excerpt

CAO Session Liveness

Companion to cao-session-management, which covers the mechanics of launching and messaging sessions. This skill covers a single question that mechanics alone cannot answer: is the session actually alive, and is the status telling me the truth?

Why this matters

Every CAO provider infers agent state by pattern-matching the rendered terminal screen. There is no structured protocol between CAO and the provider CLI. A provider that has exited, crashed, or stalled on an unanswerable dialog can leave a screen that still matches an idle or processing pattern.

The consequence is specific and it is the failure this skill exists to prevent: reporting progress on a session that is already dead.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about CAO Session Liveness

What else does awslabs publish alongside CAO Session Liveness?
CAO Session Liveness is one of 18 skills that DirSkills catalogs from awslabs/cli-agent-orchestrator, the repository it ships in. Its siblings there include AG-UI Author, AI-DLC Portfolio and Add UI To MCP Server. Each one is a separate skill with its own page in this directory, installs the same way CAO Session Liveness does, and is maintained by awslabs in that same repository. The rest of the collection is listed on the awslabs/cli-agent-orchestrator page.
How does CAO Session Liveness compare to other AI Engineering skills?
CAO Session Liveness ranks #1268 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of CAO Session Liveness against them. Open each page to compare what they document and how they install.