mcpbeat

Update Acp

rivet-dev/update-acp

Audit AgentOS ACP feature coverage across the stable ACP v1 specification, each underlying agent harness and control interface, its upstream ACP adapter, and AgentOS public API/types. Use for ACP upgrades, adapter parity checks, or missing-feature audits.

604 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4293
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/rivet-dev/agentos --skill update-acp

The instruction itself

1 sections, as written by the author

Update ACP

  • Pin the latest schema-v1.* ACP tag and the exact local harness and adapter versions. Keep the schema release, SDK/package release, and wire protocolVersion distinct. Ignore draft/v2 features unless clearly labeled.
  • Enumerate every stable ACP method, capability, content type, update, and lifecycle behavior. Include AgentOS-required extensions separately; do not present them as ACP requirements.
  • Audit every agent registered under registry/agent/. Prefer current upstream source over README claims:
  • OpenCode: native opencode acp and its internal harness APIs.
  • Claude: Claude Agent SDK/CLI and @agentclientprotocol/claude-agent-acp.
  • Codex: Codex App Server/CLI and @agentclientprotocol/codex-acp.
  • Pi: Pi core, the pinned Pi RPC contract, and svkozak/pi-acp.
  • Produce one table per agent. For every feature report: ACP requirement (must, optional, or extension), harness support, harness control-interface support (RPC/App Server/SDK/CLI), upstream adapter support, AgentOS sidecar support, AgentOS public API/type support, confidence, and source evidence. Use yes, partial, no, or n/a. Group rows only when every status matches, and name every grouped feature. Name equivalent harness primitives such as switch_session; do not require them to share the ACP method name, and never infer harness support only from adapter behavior.
  • Inspect AgentOS at minimum in crates/agentos-sidecar/src/acp_extension.rs, packages/core/src/agent-session-types.ts, packages/core/src/agent-os.ts, registry manifests, and relevant tests. Verify both runtime forwarding and public exposure; preserved unknown JSON alone is not typed API support.
  • After the matrix, list prioritized action items grouped by owner: upstream adapter, harness/control interface, AgentOS sidecar/runtime, AgentOS API/types, or packaging/tests. State when no action is justified because the harness lacks the feature or ACP makes it optional.
  • Do not change code during the audit. End by asking: Do you want me to fix these? If so, which priorities or agents should I include?

How to use it

Copy the folder

Take rivet-dev/update-acp from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.