grix-connector 3.1.13 → 3.1.14

package/openclaw-plugin/skills/grix-group/SKILL.md

@@ -1,164 +1,164 @@
----
-name: grix-group
-description: Use the typed `grix_group` tool for Grix group lifecycle and membership operations. Trigger when users ask to create, inspect, leave, update, or dissolve groups, or when these operations fail with scope or permission errors.
----
-
-# Grix Group Governance
-
-Operate group-governance actions through the `grix_group` tool.  
-This skill is about tool selection and guardrails, not protocol bridging.
-
-## Workflow
-
-1. Parse the user request into one action:
-   `create`, `detail`, `leave`, `add_members`, `remove_members`, `update_member_role`, `update_all_members_muted`, `update_member_speaking`, or `dissolve`.
-2. Validate required fields before any call.
-3. Call `grix_group` exactly once per business action.
-4. Classify failures by HTTP/BizCode and return exact remediation.
-5. Avoid duplicate side effects:
-   never auto-retry `create` or `dissolve` without explicit user confirmation.
-
-## Tool Contract
-
-For Grix group governance, always call:
-
-1. Tool: `grix_group`
-2. `action`: one of `create`, `detail`, `leave`, `add_members`, `remove_members`, `update_member_role`, `update_all_members_muted`, `update_member_speaking`, `dissolve`
-3. `accountId`: always pass `{{AccountId}}` from the current conversation context for every action, including `leave`.
-
-Rules:
-
-1. Pass business parameters with their exact typed field names.
-2. Use `sessionId`, `memberIds`, `memberTypes`, `memberId`, `memberType`, `role`, `allMembersMuted`, `isSpeakMuted`, and `canSpeakWhenAllMuted` explicitly.
-3. Do not invent aliases or fallback fields.
-4. Keep one tool call per action for audit clarity.
-
-## Action Contracts
-
-### create
-
-Purpose: create a new group session.
-
-Required input:
-
-1. `name` (non-empty string)
-2. `memberIds` (optional string array; each item numeric text)
-3. `memberTypes` (optional int array; align with `memberIds`)
-
-Guardrails:
-
-1. Ask for clarification if group name is missing.
-2. Ask for explicit confirmation before repeating the same create request.
-3. Treat this action as non-idempotent.
-
-### add_members
-
-Purpose: add members into an existing group.
-
-Required input:
-
-1. `sessionId` (non-empty string)
-2. `memberIds` (non-empty string array; each item numeric text)
-3. `memberTypes` (optional int array; align with `memberIds`)
-
-Guardrails:
-
-1. Reject empty `sessionId` before calling the tool.
-2. Reject non-numeric `memberIds` before calling the tool.
-3. If `sessionId` is ambiguous, ask the user to confirm the target group first.
-
-### leave
-
-Purpose: let the current Agent leave a group by itself.
-
-Required input:
-
-1. `sessionId`
-
-Guardrails:
-
-1. Only execute this when the requester is clearly the current Agent owner, or an already-established authorized operator in the current context.
-2. If the requester identity is unclear, ask for confirmation first; if it is clearly unauthorized, reject directly and do not call `grix_group`.
-3. This action is only for the current Agent leaving its own group membership.
-4. Never translate a request to remove other members into `leave`; use `remove_members` for that.
-5. Do not send `memberId`, `memberIds`, or `memberTypes` with this action.
-6. This action does not require scope and should not be described as a scope-grant workflow.
-7. Execute `leave` silently: do not send any pre-leave or farewell message to the group before leaving.
-
-### remove_members
-
-Required input:
-
-1. `sessionId`
-2. `memberIds`
-
-### update_member_role
-
-Required input:
-
-1. `sessionId`
-2. `memberId`
-3. `role`
-
-Guardrails:
-
-1. Only use `memberType=1` for role updates.
-2. Never guess a role value; confirm when unclear.
-
-### update_all_members_muted
-
-Required input:
-
-1. `sessionId`
-2. `allMembersMuted`
-
-Guardrails:
-
-1. Only use this for group-wide mute state changes.
-2. Never guess the desired mute state from vague wording; confirm whether the user wants to enable or disable all-member mute.
-
-### update_member_speaking
-
-Required input:
-
-1. `sessionId`
-2. `memberId`
-3. At least one of `isSpeakMuted` or `canSpeakWhenAllMuted`
-
-Guardrails:
-
-1. Only use `memberType=1` or `memberType=2`.
-2. Do not send an empty speaking update; at least one speaking field must be explicit.
-3. If the target member is ambiguous, ask the user to confirm the exact member first.
-
-### detail / dissolve
-
-Required input:
-
-1. `sessionId`
-
-## Error Handling Rules
-
-1. `403/20011`:
-   report missing scope and ask owner to grant the scope in Aibot Agent permission page.
-   Do not use this remediation for `leave`, because `leave` is scope-free.
-2. `401/10001`:
-   report invalid key/auth and suggest checking agent config or rotating API key.
-3. `403/10002`:
-   report agent is not active or invalid provider type.
-4. `400/10003`:
-   report invalid/missing parameters and ask user for corrected values.
-5. Other errors:
-   return backend `msg` and stop automatic retries.
-
-## Response Style
-
-1. State action result first.
-2. Include key identifiers (`session_id`, member count, mute state) when successful.
-3. Include exact remediation when failed.
-4. Never hide scope or auth errors behind generic wording.
-5. For `leave`, report result to the requester only; do not post extra messages into the group session.
-
-## References
-
-1. Load [references/api-contract.md](references/api-contract.md) when you need exact tool mapping, payload examples, and scope matrix.
+---
+name: grix-group
+description: Use the typed `grix_group` tool for Grix group lifecycle and membership operations. Trigger when users ask to create, inspect, leave, update, or dissolve groups, or when these operations fail with scope or permission errors.
+---
+
+# Grix Group Governance
+
+Operate group-governance actions through the `grix_group` tool.  
+This skill is about tool selection and guardrails, not protocol bridging.
+
+## Workflow
+
+1. Parse the user request into one action:
+   `create`, `detail`, `leave`, `add_members`, `remove_members`, `update_member_role`, `update_all_members_muted`, `update_member_speaking`, or `dissolve`.
+2. Validate required fields before any call.
+3. Call `grix_group` exactly once per business action.
+4. Classify failures by HTTP/BizCode and return exact remediation.
+5. Avoid duplicate side effects:
+   never auto-retry `create` or `dissolve` without explicit user confirmation.
+
+## Tool Contract
+
+For Grix group governance, always call:
+
+1. Tool: `grix_group`
+2. `action`: one of `create`, `detail`, `leave`, `add_members`, `remove_members`, `update_member_role`, `update_all_members_muted`, `update_member_speaking`, `dissolve`
+3. `accountId`: always pass `{{AccountId}}` from the current conversation context for every action, including `leave`.
+
+Rules:
+
+1. Pass business parameters with their exact typed field names.
+2. Use `sessionId`, `memberIds`, `memberTypes`, `memberId`, `memberType`, `role`, `allMembersMuted`, `isSpeakMuted`, and `canSpeakWhenAllMuted` explicitly.
+3. Do not invent aliases or fallback fields.
+4. Keep one tool call per action for audit clarity.
+
+## Action Contracts
+
+### create
+
+Purpose: create a new group session.
+
+Required input:
+
+1. `name` (non-empty string)
+2. `memberIds` (optional string array; each item numeric text)
+3. `memberTypes` (optional int array; align with `memberIds`)
+
+Guardrails:
+
+1. Ask for clarification if group name is missing.
+2. Ask for explicit confirmation before repeating the same create request.
+3. Treat this action as non-idempotent.
+
+### add_members
+
+Purpose: add members into an existing group.
+
+Required input:
+
+1. `sessionId` (non-empty string)
+2. `memberIds` (non-empty string array; each item numeric text)
+3. `memberTypes` (optional int array; align with `memberIds`)
+
+Guardrails:
+
+1. Reject empty `sessionId` before calling the tool.
+2. Reject non-numeric `memberIds` before calling the tool.
+3. If `sessionId` is ambiguous, ask the user to confirm the target group first.
+
+### leave
+
+Purpose: let the current Agent leave a group by itself.
+
+Required input:
+
+1. `sessionId`
+
+Guardrails:
+
+1. Only execute this when the requester is clearly the current Agent owner, or an already-established authorized operator in the current context.
+2. If the requester identity is unclear, ask for confirmation first; if it is clearly unauthorized, reject directly and do not call `grix_group`.
+3. This action is only for the current Agent leaving its own group membership.
+4. Never translate a request to remove other members into `leave`; use `remove_members` for that.
+5. Do not send `memberId`, `memberIds`, or `memberTypes` with this action.
+6. This action does not require scope and should not be described as a scope-grant workflow.
+7. Execute `leave` silently: do not send any pre-leave or farewell message to the group before leaving.
+
+### remove_members
+
+Required input:
+
+1. `sessionId`
+2. `memberIds`
+
+### update_member_role
+
+Required input:
+
+1. `sessionId`
+2. `memberId`
+3. `role`
+
+Guardrails:
+
+1. Only use `memberType=1` for role updates.
+2. Never guess a role value; confirm when unclear.
+
+### update_all_members_muted
+
+Required input:
+
+1. `sessionId`
+2. `allMembersMuted`
+
+Guardrails:
+
+1. Only use this for group-wide mute state changes.
+2. Never guess the desired mute state from vague wording; confirm whether the user wants to enable or disable all-member mute.
+
+### update_member_speaking
+
+Required input:
+
+1. `sessionId`
+2. `memberId`
+3. At least one of `isSpeakMuted` or `canSpeakWhenAllMuted`
+
+Guardrails:
+
+1. Only use `memberType=1` or `memberType=2`.
+2. Do not send an empty speaking update; at least one speaking field must be explicit.
+3. If the target member is ambiguous, ask the user to confirm the exact member first.
+
+### detail / dissolve
+
+Required input:
+
+1. `sessionId`
+
+## Error Handling Rules
+
+1. `403/20011`:
+   report missing scope and ask owner to grant the scope in Aibot Agent permission page.
+   Do not use this remediation for `leave`, because `leave` is scope-free.
+2. `401/10001`:
+   report invalid key/auth and suggest checking agent config or rotating API key.
+3. `403/10002`:
+   report agent is not active or invalid provider type.
+4. `400/10003`:
+   report invalid/missing parameters and ask user for corrected values.
+5. Other errors:
+   return backend `msg` and stop automatic retries.
+
+## Response Style
+
+1. State action result first.
+2. Include key identifiers (`session_id`, member count, mute state) when successful.
+3. Include exact remediation when failed.
+4. Never hide scope or auth errors behind generic wording.
+5. For `leave`, report result to the requester only; do not post extra messages into the group session.
+
+## References
+
+1. Load [references/api-contract.md](references/api-contract.md) when you need exact tool mapping, payload examples, and scope matrix.

package/openclaw-plugin/skills/grix-group/references/api-contract.md

@@ -1,97 +1,97 @@
-# API Contract
-
-## Purpose
-
-Map high-level governance actions to Aibot Agent API HTTP routes.
-
-## Base Rules
-
-1. Base path: `/v1/agent-api`
-2. Auth: `Authorization: Bearer <agent_api_key>`
-3. Only `provider_type=3` and `status=active` agent can access.
-4. Scope middleware executes before service business checks.
-
-## Action Mapping (v1)
-
-| Action | Method | Route | Required Scope |
-|---|---|---|---|
-| `group_detail_read` | `GET` | `/sessions/group/detail` | `group.detail.read` |
-| `group_create` | `POST` | `/sessions/create_group` | `group.create` |
-| `group_leave_self` | `POST` | `/sessions/leave` | - |
-| `group_member_add` | `POST` | `/sessions/members/add` | `group.member.add` |
-| `group_member_remove` | `POST` | `/sessions/members/remove` | `group.member.remove` |
-| `group_member_role_update` | `POST` | `/sessions/members/role` | `group.member.role.update` |
-| `group_all_members_muted_update` | `POST` | `/sessions/speaking/all_muted` | `group.speaking.update` |
-| `group_member_speaking_update` | `POST` | `/sessions/members/speaking` | `group.speaking.update` |
-| `group_dissolve` | `POST` | `/sessions/dissolve` | `group.dissolve` |
-
-## OpenClaw Tool Mapping
-
-Use the native `grix_group` tool with typed fields:
-
-| Tool action | HTTP action | Required fields |
-|---|---|---|
-| `create` | `group_create` | `accountId`, `name` |
-| `detail` | `group_detail_read` | `accountId`, `sessionId` |
-| `leave` | `group_leave_self` | `accountId`, `sessionId` |
-| `add_members` | `group_member_add` | `accountId`, `sessionId`, `memberIds` |
-| `remove_members` | `group_member_remove` | `accountId`, `sessionId`, `memberIds` |
-| `update_member_role` | `group_member_role_update` | `accountId`, `sessionId`, `memberId`, `role` |
-| `update_all_members_muted` | `group_all_members_muted_update` | `accountId`, `sessionId`, `allMembersMuted` |
-| `update_member_speaking` | `group_member_speaking_update` | `accountId`, `sessionId`, `memberId`, `isSpeakMuted` or `canSpeakWhenAllMuted` |
-| `dissolve` | `group_dissolve` | `accountId`, `sessionId` |
-
-## Payload Templates
-
-### create
-
-```json
-{
-  "action": "create",
-  "accountId": "primary",
-  "name": "Project Collaboration Group",
-  "memberIds": ["1002", "9991"],
-  "memberTypes": [1, 2]
-}
-```
-
-### add_members
-
-```json
-{
-  "action": "add_members",
-  "accountId": "primary",
-  "sessionId": "task_room_9083",
-  "memberIds": ["1003"],
-  "memberTypes": [1]
-}
-```
-
-### leave
-
-```json
-{
-  "action": "leave",
-  "accountId": "primary",
-  "sessionId": "task_room_9083"
-}
-```
-
-## Error Matrix
-
-| HTTP/BizCode | Meaning | Skill Response |
-|---|---|---|
-| `403/20011` | agent scope forbidden | Tell owner to grant corresponding scope |
-| `400/10003` | invalid request payload | Ask for missing or corrected parameters |
-| `401/10001` | invalid or missing auth | Check api_key and account config |
-| `403/10002` | agent not active / invalid provider | Ask owner to activate the agent |
-
-Notes:
-
-1. `leave` does not require scope and should not route `403/20011` into scope remediation.
-
-## Retry Policy
-
-1. Never auto-retry `group_create` unless user confirms.
-2. Allow one retry for transient network failure only.
-3. Do not retry auth/scope/parameter failures automatically.
+# API Contract
+
+## Purpose
+
+Map high-level governance actions to Aibot Agent API HTTP routes.
+
+## Base Rules
+
+1. Base path: `/v1/agent-api`
+2. Auth: `Authorization: Bearer <agent_api_key>`
+3. Only `provider_type=3` and `status=active` agent can access.
+4. Scope middleware executes before service business checks.
+
+## Action Mapping (v1)
+
+| Action | Method | Route | Required Scope |
+|---|---|---|---|
+| `group_detail_read` | `GET` | `/sessions/group/detail` | `group.detail.read` |
+| `group_create` | `POST` | `/sessions/create_group` | `group.create` |
+| `group_leave_self` | `POST` | `/sessions/leave` | - |
+| `group_member_add` | `POST` | `/sessions/members/add` | `group.member.add` |
+| `group_member_remove` | `POST` | `/sessions/members/remove` | `group.member.remove` |
+| `group_member_role_update` | `POST` | `/sessions/members/role` | `group.member.role.update` |
+| `group_all_members_muted_update` | `POST` | `/sessions/speaking/all_muted` | `group.speaking.update` |
+| `group_member_speaking_update` | `POST` | `/sessions/members/speaking` | `group.speaking.update` |
+| `group_dissolve` | `POST` | `/sessions/dissolve` | `group.dissolve` |
+
+## OpenClaw Tool Mapping
+
+Use the native `grix_group` tool with typed fields:
+
+| Tool action | HTTP action | Required fields |
+|---|---|---|
+| `create` | `group_create` | `accountId`, `name` |
+| `detail` | `group_detail_read` | `accountId`, `sessionId` |
+| `leave` | `group_leave_self` | `accountId`, `sessionId` |
+| `add_members` | `group_member_add` | `accountId`, `sessionId`, `memberIds` |
+| `remove_members` | `group_member_remove` | `accountId`, `sessionId`, `memberIds` |
+| `update_member_role` | `group_member_role_update` | `accountId`, `sessionId`, `memberId`, `role` |
+| `update_all_members_muted` | `group_all_members_muted_update` | `accountId`, `sessionId`, `allMembersMuted` |
+| `update_member_speaking` | `group_member_speaking_update` | `accountId`, `sessionId`, `memberId`, `isSpeakMuted` or `canSpeakWhenAllMuted` |
+| `dissolve` | `group_dissolve` | `accountId`, `sessionId` |
+
+## Payload Templates
+
+### create
+
+```json
+{
+  "action": "create",
+  "accountId": "primary",
+  "name": "Project Collaboration Group",
+  "memberIds": ["1002", "9991"],
+  "memberTypes": [1, 2]
+}
+```
+
+### add_members
+
+```json
+{
+  "action": "add_members",
+  "accountId": "primary",
+  "sessionId": "task_room_9083",
+  "memberIds": ["1003"],
+  "memberTypes": [1]
+}
+```
+
+### leave
+
+```json
+{
+  "action": "leave",
+  "accountId": "primary",
+  "sessionId": "task_room_9083"
+}
+```
+
+## Error Matrix
+
+| HTTP/BizCode | Meaning | Skill Response |
+|---|---|---|
+| `403/20011` | agent scope forbidden | Tell owner to grant corresponding scope |
+| `400/10003` | invalid request payload | Ask for missing or corrected parameters |
+| `401/10001` | invalid or missing auth | Check api_key and account config |
+| `403/10002` | agent not active / invalid provider | Ask owner to activate the agent |
+
+Notes:
+
+1. `leave` does not require scope and should not route `403/20011` into scope remediation.
+
+## Retry Policy
+
+1. Never auto-retry `group_create` unless user confirms.
+2. Allow one retry for transient network failure only.
+3. Do not retry auth/scope/parameter failures automatically.