kweaver-admin

KWeaver Admin CLI

Overview

kweaver-admin covers platform administration: authentication, org/user/role, model config, audit, and raw API passthrough.

This skill uses progressive disclosure:

Read this file for command-group selection.
Read references/*.md for exact command/parameter details.
Read routing/fallback reference when debugging deployment differences.

references/ is the source of truth for this skill. When answering detailed questions (flags, payload shape, fallback behavior), read the corresponding reference first, then execute.

Installation

npm install -g @kweaver-ai/kweaver-admin
# or
npx -y @kweaver-ai/kweaver-admin --help

Usage

kweaver-admin [--json] [--base-url <url>] [-k] <group> <subcommand> [options]

Command Group Overview

Group	Description	Detailed Parameters
`auth`	Login, status, whoami, change password, token	references/auth.md
`user`	User CRUD, role binding, reset password	references/user.md
`org` + `role`	Department management, role and member management	references/org-role.md
`llm` + `small-model`	Model configuration management and connectivity testing	references/models.md
`audit` + `config` + `call`	Audit, configuration, raw request passthrough	references/audit-config-call.md
Routing and fallback	REST/ShareMgnt fallback and known exceptions	references/routing-and-fallbacks.md

References Usage Rules (Key)

references/ is the detail layer of this skill, read in the following order:

First read this file to determine the command group and execution order.
Then read the corresponding references/*.mdto get parameters and examples.
When encountering deployment differences (404/501/errID), additionally read routing-and-fallbacks.md。

When the user asks about parameter semantics, command details, or implementation logic, you must first read the corresponding reference, then execute.

Execution Strategy

First run read-only commands (list/get/tree/status/whoami) to confirm the environment.
Before write operations, record key IDs, and prefer using --json。
After each write operation, immediately verify with a read command.
When encountering 404/501/errID errors, refer to the routing reference to determine whether it is a backend availability difference.

Trigger Examples

/kweaver-admin 列出所有用户并按关键词过滤
/kweaver-admin 给用户分配角色并验证结果
/kweaver-admin 创建部门并查看组织树
/kweaver-admin 重置 testcli1 密码到默认值
/kweaver-admin 用 call 检查某个 REST 接口是否可达