Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →awslabs/cao-session-management
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions.
Passed 15 of 20 test cases with the skill, and 4 of 20 without it.
and 13 more in the full report
12 fixed5 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
By default CAO launches sessions using `kiro_cli`. We want to run a session named 'refactor-job' with agent profile 'code_supervisor' using Anthropic's Claude Code backend instead. What flag specifies this alternative LLM provider during launch?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies using the --provider flag on cao launch to select an alternative backend. | Missed | Passed |
The instructions your model reads when the skill loads.
Run cao --skill for the CAO operating guide: preflight, launch, session commands,
statuses, delegation, and safety. Run cao <group> --help for exact syntax.
Two rules apply to every launch from an agent:
--auto-approve. It skips the confirmation prompt and leaves the profile's tool
policy unchanged; whether that policy is enforced depends on the provider (read the
Enforcement: line launch prints). --yolo also skips the prompt but removes all
tool restrictions, so the agent can run any command, including aws, rm and
curl. Use --yolo only when the user asks for it.cao command cannot reach the server, check it with
curl -sf http://localhost:9889/health.A reported status is inferred from the rendered terminal screen, so it can disagree with reality. Before reporting readiness, progress, or completion to a user, corroborate the status with an output read; see cao-session-liveness.
Profiles are CAO-level entities, installed with cao install regardless of which CLI
provider runs them. To find available profiles:
| Source | Command |
|---|---|
| All available profiles, with the source each one resolved from | cao profile list (no server needed), or curl -sf http://localhost:9889/agents/profiles |
| Profiles matching a keyword | cao profile find "<keywords>" |
| Custom/local profile files only | ls ~/.aws/cli-agent-orchestrator/agent-store/ |
Profiles installed via cao install <name> | ls ~/.aws/cli-agent-orchestrator/agent-context/ |
| Profile installation and keyword discovery | see Agent profile installation and profile discovery |
Provider-native list (kiro_cli only) | kiro-cli agent list, useful because CAO mirrors profiles into ~/.kiro/agents/ |
cao profile list and the HTTP endpoint return the same list. Discovery scans the
local store (agent-store/) first, then provider-specific directories (including
agent-context/), then extra directories from settings, and the built-in packaged
store last. The first match wins, so a local copy of a profile shadows the built-in
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.