@coze/cli 0.3.5-alpha.b70902 → 0.3.5-alpha.d65c38

package/skills/coze-agent-collaboration/SKILL.md

@@ -1,62 +0,0 @@
----
-name: coze-agent-collaboration
-version: 0.3.5-alpha.b70902
-description: "CRITICAL @Agent dispatch rule: when asked to @ or delegate to a peer Coze project Agent, MUST execute `coze agent at`; rendering an `at://agent:<claw_id>` link or visible @mention is display only and never dispatches. Also use this skill to discover project Agent members, choose where results return, or retry an unchanged request after an unknown transport outcome."
-metadata:
-  requires:
-    bins: ["coze"]
-  cliHelp: "coze agent at --help"
----
-
-# Coze Agent Collaboration
-
-Use `coze agent at` to send a project-group `@Agent` collaboration request. An `at://agent:<claw_id>` link or visible `@name` mention only controls display; it does not send a request or wake the target Agent. Never say the request was sent unless `coze agent at` returned an accepted response.
-
-Treat the command as asynchronous dispatch: an accepted response means delivery was queued, not that the delegated work has finished.
-
-## Preconditions
-
-- Run only inside a current Coze project Agent turn.
-- Obtain `group_id`, `agent_id`, and `reply_to_message_id` from the trusted current-turn context. Never guess them, derive them from names, or reuse values from an earlier turn.
-- Map context fields exactly: `group_id` -> `--project-id`, `agent_id` -> `--source-claw-id`, and `reply_to_message_id` -> `--reply-to-message-id`.
-- Keep `group_id`, `agent_id`, and every `target_claw_id` as decimal strings. Never convert these int64 IDs through a JavaScript number or another floating-point type. Treat `reply_to_message_id` as an opaque string and pass it through unchanged.
-- Keep `reply_to_message_id` within 256 UTF-8 bytes, each target message within 4,000 Unicode code points, and all target messages together within 32 KiB.
-- Check authentication with `coze auth status --format json` when the CLI reports an authentication error.
-- Do not apply Coze App version checks. CLI availability is independent of the App UI version gate.
-
-## Workflow
-
-1. Refresh current project members before each dispatch:
-
-   ```bash
-   coze agent member list --project-id "<group_id>" --format json
-   ```
-
-2. Select only members with `user_type=2` and a non-empty `claw_id`. Exclude the current `agent_id` (the `source_claw_id`). Delegate to at most three Agents per request.
-3. Give every target a concrete, self-contained task. Do not forward secrets or unrelated conversation text.
-4. Call `coze agent at` with the exact current-turn identifiers and a JSON array:
-
-   ```bash
-   coze agent at \
-     --project-id "<group_id>" \
-     --source-claw-id "<agent_id>" \
-     --reply-to-message-id "<reply_to_message_id>" \
-     --targets '[{"target_claw_id":"<target_claw_id>","message":"Review the API contract and return concrete issues.","response_target_type":"agent"}]' \
-     --format json
-   ```
-
-5. Require `code=0`, `data.status="accepted"`, and a non-empty `data.message_id` before treating dispatch as accepted. An `at://agent:<claw_id>` mention without this command result is not a dispatch. Preserve `logid` for diagnostics.
-6. Continue according to `response_target_type`:
-   - `agent` (default): the target reports back in a later collaboration turn. Do not block or poll after `accepted`, and do not dispatch a duplicate; incorporate the later response before final synthesis when the task depends on it.
-   - `user`: the target delivers directly to the user; use only when direct independent delivery was explicitly intended.
-
-## Safety and retry rules
-
-- Never target the source Agent itself.
-- Do not invent an `idempotency_key`; the service derives idempotency from trusted request context.
-- On a transport timeout with no response, retry the exact same request. Keep identifiers, target order, messages, and response targets unchanged.
-- Do not retry validation, permission, or membership errors until the underlying input or authorization is corrected.
-- Do not report delegated work as complete from the `accepted` response alone.
-- Prefer one focused request containing all independent targets over several duplicate calls.
-
-Read [references/at-agent-contract.md](references/at-agent-contract.md) for the full input/output contract and failure handling.

package/skills/coze-agent-collaboration/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Coze Agent Collaboration"
-  short_description: "Delegate work between Coze project agents via CLI"
-  default_prompt: "Use $coze-agent-collaboration to delegate a task to another Coze project agent."

package/skills/coze-agent-collaboration/references/at-agent-contract.md

@@ -1,70 +0,0 @@
-# `coze agent at` contract
-
-## Command input
-
-| Option | Required | Meaning |
-|---|---:|---|
-| `--project-id` | yes | Current context's `group_id`, passed as a decimal string. |
-| `--source-claw-id` | yes | Current context's `agent_id` (the initiating Agent's `claw_id`), passed as a decimal string. |
-| `--reply-to-message-id` | yes | Current context's `reply_to_message_id`; the outgoing AtAgent message replies to this message. It must be 1 to 256 UTF-8 bytes. |
-| `--targets` | yes | JSON array with 1 to 3 target objects. |
-
-Each target object has:
-
-| Field | Required | Meaning |
-|---|---:|---|
-| `target_claw_id` | yes | Target project Agent's `claw_id`, encoded as a string. |
-| `message` | yes | Non-empty delegated task, at most 4,000 Unicode code points. All target messages together must be at most 32 KiB in UTF-8. |
-| `response_target_type` | no | `agent` (default) or `user`. |
-
-Example with parallel targets:
-
-```bash
-coze agent at \
-  --project-id "7600000000000000001" \
-  --source-claw-id "7600000000000000002" \
-  --reply-to-message-id "msg_current_turn" \
-  --targets '[{"target_claw_id":"7600000000000000003","message":"Audit the API for security risks.","response_target_type":"agent"},{"target_claw_id":"7600000000000000004","message":"Check the user-facing copy and report edits.","response_target_type":"agent"}]' \
-  --format json
-```
-
-## Success output
-
-The command emits one JSON envelope:
-
-```json
-{
-  "code": 0,
-  "msg": "success",
-  "data": {
-    "message_id": "generated_dispatch_message_id",
-    "status": "accepted",
-    "idempotency_replayed": false
-  },
-  "logid": "request_log_id"
-}
-```
-
-- `message_id` identifies the visible project collaboration message.
-- `status=accepted` means asynchronous dispatch was accepted.
-- `idempotency_replayed=true` means the same logical request was already accepted; do not send a new variant merely to force another execution.
-- `logid` is the primary diagnostic key.
-
-## Failure handling
-
-| Failure | Action |
-|---|---|
-| Invalid JSON or malformed target | Fix locally; do not call again unchanged. |
-| Target is not an Agent project member | Refresh `coze agent member list`; choose an active Agent member. |
-| Target equals source | Choose a different Agent. |
-| Permission/authentication failure | Refresh authentication or trusted runtime context; do not broaden credentials. |
-| Transport timeout, response unknown | Retry the byte-equivalent logical request. |
-| Service error with a `logid` | Preserve the full JSON envelope and diagnose using the `logid`. |
-
-## Context discipline
-
-Map trusted current-turn context fields exactly: `group_id` -> `--project-id`, `agent_id` -> `--source-claw-id`, and `reply_to_message_id` -> `--reply-to-message-id`.
-
-`reply_to_message_id` is an opaque identifier and must refer to the message currently being processed. The outgoing AtAgent message uses it as its reply anchor. Pass it through unchanged. It is not the dispatch result `message_id`, a previous message, a session ID, or a generated random value.
-
-Rendering an `at://agent:<claw_id>` link or a visible `@name` mention does not call this contract and does not dispatch work. A real dispatch requires executing `coze agent at` and receiving `code=0`, `data.status="accepted"`, and a non-empty `data.message_id`.