菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Publish @agentos-software/* registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.
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.
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.
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.
| 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. |
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.registry/agent/. Prefer current upstream source over README claims:
opencode acp and its internal harness APIs.@agentclientprotocol/claude-agent-acp.@agentclientprotocol/codex-acp.svkozak/pi-acp.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.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.