---
name: grix-admin
description: Use the typed `grix_admin` tool to manage agents and categories on the Grix platform — create agents, list/create/update categories, assign an agent to a category, and rotate an agent's API key. Trigger when the user asks to create a new agent, organize agents into categories, or rotate an agent key.
trigger: 当用户要在 Grix 平台创建 Agent、管理分类、给 Agent 分配分类、或轮换 Agent 的 API key 时
---

# Grix Admin

Use the `grix_admin` tool for agent and category management on the Grix
platform. This skill covers only platform-side management — it does not touch
any local connector configuration or binding.

## Tool contract

Call `grix_admin` with one `action`:

- `create_agent` — create an agent. Requires `agentName`; optional
  `introduction`, `isMain`, `categoryId`.
- `list_categories` — list all categories. No extra fields.
- `create_category` — requires `name`; optional `parentId`, `sortOrder`.
- `update_category` — requires `categoryId`; optional `name`, `parentId`,
  `sortOrder`.
- `assign_category` — assign an agent to a category. Requires `agentId` and
  `categoryId`.
- `rotate_api_key` — rotate an agent's API key. Requires `agentId`.

## Rules

1. Pick exactly one `action` per call and supply only the fields that action
   needs.
2. For `assign_category` / `rotate_api_key` you need the target `agentId`; for
   category edits you need the `categoryId`. Resolve unknown IDs first
   (`list_categories`, or `grix_query` for agents) rather than guessing.
3. `rotate_api_key` invalidates the old key. Confirm the target agent with the
   user before rotating, and report the new key handling per platform policy.