Run any Skill in Manus with one click

update-acp

Stars3,986

Forks198

UpdatedJuly 21, 2026 at 08:57

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rivet-dev

rivet-dev/agentos

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	update-acp
description	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 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?

More from this repository

same repository

gigacode-api-sanity

rivet-dev/agentos

Compare GigaCode's OpenCode-compatible HTTP/SSE API with native OpenCode in isolated temporary workspaces. Use when asked to sanity-check, re-test, or manually validate Claude Sonnet streaming, multi-turn sessions, tool calls, permissions, file edits, cancellation, or post-cancel reuse.

2026-07-214.0k

publish-registry

rivet-dev/agentos

Publish @agentos-software/* registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.

2026-07-064.0k

release-preview

rivet-dev/agentos

Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.

2026-07-064.0k

release

rivet-dev/agentos

Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.

2026-07-064.0k

sanity-check

rivet-dev/agentos

Run the deferred AgentOS E2E smoke test from public npm packages. Use when the user asks to sanity check, smoke test, or verify a release works.

2026-07-064.0k

browse

rivet-dev/agentos

Use the browse CLI for Browserbase browser automation, Browserbase cloud APIs, Browserbase Functions, templates, web fetch/search, diagnostics, and Browse.sh skill discovery/installation. Use when the user asks to navigate pages, inspect browser state, run local or remote browser sessions, manage Browserbase resources, call Browserbase Functions, browse or scaffold Browserbase templates, fetch or search web content, diagnose browse setup, find or install a skill for a website task, discover site-specific Browse.sh skills, or install/refresh this browse skill.

2026-07-064.0k

name	update-acp
description	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 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?