How do I install the Update Acp skill?

Run npx skillmds@latest add rivet-dev/update-acp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Acp safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Acp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Acp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Acp?

rivet-dev (@rivet-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Acp by rivet-dev — Agent Skill

Name: Update Acp
Author: 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.

rivet-dev a650bab 2.4 KB Updated Sep 17, 2026

File contents

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?

---name: update-acpdescription: 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.---# Update ACP1. 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.2. Enumerate every stable ACP method, capability, content type, update, and lifecycle behavior. Include AgentOS-required extensions separately; do not present them as ACP requirements.3. 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`.4. 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.5. 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.6. 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.7. 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?**

Frequently asked questions