qiqi-cli

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

企企服务业ERP qiqi

Qiqi Service Industry ERP qiqi

适用边界

Applicable Scope

本 Skill 只处理已就绪的

qiqi

运行时。首次安装、更新、重装、CLI 缺失、OAuth 接入或 Agent Skills 接入由

qiqi-cli-installation

处理；安装完成后再回到本 Skill 执行身份、查询和业务请求。

This Skill only handles the ready-to-use

qiqi

runtime. Initial installation, update, reinstallation, missing CLI, OAuth access, or Agent Skills access are handled by

qiqi-cli-installation

; return to this Skill to perform identity verification, queries, and business requests after installation is completed.

权威边界

Authority Boundaries

把当前 qiqi 运行时作为能力和语法权威：

当前命令及参数以
```
qiqi --help
```
和目标叶子命令帮助为准。
当前企业下的对象、字段、候选值、视图和动作以
```
objects
```
、
```
describe
```
与实际返回为准。
本技能只定义通用能力选择、证据判断和安全执行规则，不预设用户必须加载其它技能，也不把示例当成完整命令契约。
用户意图决定要完成什么，运行时能力决定当前能否完成；二者不一致时停止操作并说明差异。

Treat the current qiqi runtime as the authority for capabilities and syntax:

Current commands and parameters are subject to
```
qiqi --help
```
and the help documentation of target leaf commands.
Objects, fields, candidate values, views, and actions under the current enterprise are subject to the actual returns of
```
objects
```
,
```
describe
```
, and related commands.
This Skill only defines general capability selection, evidence judgment, and secure execution rules. It does not presuppose that users must load other Skills, nor does it treat examples as complete command contracts.
User intent determines what needs to be accomplished; runtime capabilities determine whether it can be accomplished currently. Stop operations and explain the discrepancy when the two are inconsistent.

按需检查点

On-Demand Checkpoints

以下检查点按任务条件触发，不是每次都要完整执行的线性流程。目标和命令都明确的简单只读任务可以直接走最短路径，例如：确认 profile 后执行

records get

，再解释返回结果。

触发条件	必要检查
业务授权失败、profile 不明确或身份发生变化	用 `auth status` 在线核对当前企业和用户；优先为业务命令显式传递 `--profile`
命令、对象、字段、值、视图或动作不明确	读取对应 `--help` ，并按需使用 `objects` 、 `describe` 或 `find values`
名称、单号、人员或记录不唯一	先取得候选并消歧；写入必须使用稳定 `RecordRef` 、唯一编码或可验证关系
需要完整集合或统计	检查筛选口径、分页和大输出，不能用候选、样例或第一页代替全集
执行动作、删除或附件上传/删除	核对身份、稳定目标、用户意图和关键影响，只执行一次最小操作
写入超时、连接中断或返回不明确	标记“状态未知”，先读取业务事实核查，不直接重试

任何任务都应按返回证据报告已确认事实、推导、状态未知和能力缺口，但不需要为了形式而重复执行与当前任务无关的发现步骤。

The following checkpoints are triggered based on task conditions and are not a linear process that must be fully executed every time. Simple read-only tasks with clear objectives and commands can take the shortest path, for example: confirm the profile, execute

records get

, and then interpret the returned results.

Trigger Condition	Necessary Checks
Business authorization failure, unclear profile, or changed identity	Use `auth status` to verify the current enterprise and user online; explicitly pass `--profile` for business commands as a priority
Unclear commands, objects, fields, values, views, or actions	Read the corresponding `--help` , and use `objects` , `describe` , or `find values` as needed
Non-unique names, order numbers, personnel, or records	First obtain candidates and disambiguate; writes must use stable `RecordRef` , unique codes, or verifiable relationships
Need complete collections or statistics	Check filtering criteria, pagination, and large outputs; do not replace the full set with candidates, samples, or the first page
Execute actions, delete records, or upload/delete attachments	Verify identity, stable targets, user intent, and key impacts; only perform the minimal necessary operation once
Write timeout, connection interruption, or unclear return	Mark as "status unknown", first verify business facts by reading, do not retry directly

Any task should report confirmed facts, deductions, unknown statuses, and capability gaps based on returned evidence, but it is not necessary to repeatedly execute discovery steps unrelated to the current task for formality.

能力路由

Capability Routing

意图	优先使用
查看或核对身份	`auth list` 、 `auth status`
发现对象类型	`objects`
查看字段类型和时间语义	`describe fields`
查看通用字段和少量数据样例	`describe list`
按跨对象文本寻找候选	`seek`
按对象和条件查询记录	`find list`
查找枚举或引用候选值	`find values`
使用工作台预置视图查询	先 `describe view` 了解当前有哪些视图，匹配后再 `find view`
读取、删除业务记录，或对该记录执行提交、审批及其它业务动作	`records get` 、 `records delete` 、 `describe actions` 、 `do-action`
处理附件	`records attachments list/url/upload/delete`
执行专用业务命令	从 `qiqi --help` 的「业务命令」起，按父命令 `--help` 逐级发现叶子命令后再执行

find list

是按对象构造条件的通用查询入口。工作台预置视图（如「我的单据」「待我审批」）先

describe view

再匹配执行；未匹配不要猜测

viewId

，也不要按对象逐个

find list

去复现同一视图。

提交、撤回、同意、驳回等是当前业务记录上的动作，走

describe actions

与

do-action

。当前 profile 未公开对应命令时，说明能力缺口，不构造替代请求。

Intent	Priority Usage
View or verify identity	`auth list` , `auth status`
Discover object types	`objects`
View field types and temporal semantics	`describe fields`
View general fields and small data samples	`describe list`
Find candidates by cross-object text	`seek`
Query records by object and conditions	`find list`
Find enumeration or reference candidate values	`find values`
Query using preset workbench views	First use `describe view` to understand available views, then execute `find view` after matching
Read, delete business records, or perform submission, approval, and other business actions on the record	`records get` , `records delete` , `describe actions` , `do-action`
Process attachments	`records attachments list/url/upload/delete`
Execute dedicated business commands	Start from the "Business Commands" section in `qiqi --help` , discover leaf commands level by level using parent command `--help` before execution

find list

is the general query entry for constructing conditions by object. For preset workbench views (such as "My Documents", "Awaiting My Approval"), use

describe view

first then match and execute; do not guess

viewId

if no match is found, nor reproduce the same view by executing

find list

for each object one by one.

Actions like submission, withdrawal, approval, rejection are actions on current business records, which go through

describe actions

and

do-action

. If the corresponding command is not exposed in the current profile, indicate the capability gap and do not construct alternative requests.

读取与输出纪律

Reading and Output Discipline

qiqi 的文本输入、输出重定向和本地 JSON 文件统一使用 UTF-8。终端出现乱码时先将宿主终端的输入输出编码切换为 UTF-8，再重新执行只读操作；不得通过丢弃、替换或猜测字符掩盖编码问题。
内部查询、字段选择和结果核对保留对象与字段的
```
apiName
```
；面向用户说明时优先使用当前元数据返回的对象标题和字段标题，减少无必要的技术名称。
标题缺失或不唯一、需要复现命令或排查错误、用户明确询问技术名称时，可以同时展示标题与
```
apiName
```
。不得自行翻译标题或根据标题猜测
```
apiName
```
。
消歧、写入确认和结果核查仍应按需展示唯一业务编码或
```
RecordRef
```
，不能为了简化输出而删除证明记录身份的信息。
```
describe list
```
的样例和
```
seek
```
的候选都不是全集或唯一性证明。
需要完整集合时持续读取分页，直到返回明确表示没有下一页；不能用第一页推断总量。
收到
```
77hub.large-output
```
时，读取
```
path
```
指向的完整 JSON；
```
summary
```
和
```
sample
```
只是局部说明，不能用于完整分析。
没有查到可能来自筛选、权限、对象未接入或数据不存在。没有额外证据时只报告“当前范围未查到”。

UTF-8 is uniformly used for text input, output redirection, and local JSON files of qiqi. When garbled characters appear in the terminal, first switch the input/output encoding of the host terminal to UTF-8, then re-execute read-only operations; do not cover up encoding issues by discarding, replacing, or guessing characters.
Retain the
```
apiName
```
of objects and fields for internal queries, field selection, and result verification; when explaining to users, prioritize using object titles and field titles returned by current metadata to reduce unnecessary technical names.
When titles are missing or non-unique, when commands need to be reproduced or errors need to be troubleshooted, or when users explicitly ask for technical names, both the title and
```
apiName
```
can be displayed. Do not translate titles or guess
```
apiName
```
based on titles.
For disambiguation, write confirmation, and result verification, still display unique business codes or
```
RecordRef
```
as needed; do not delete information that proves record identity for the sake of simplifying output.
Samples from
```
describe list
```
and candidates from
```
seek
```
are not proof of full sets or uniqueness.
When a complete collection is needed, continuously read pagination until an explicit indication of no next page is returned; do not infer the total amount from the first page.
When receiving
```
77hub.large-output
```
, read the complete JSON pointed to by
```
path
```
;
```
summary
```
and
```
sample
```
are only partial explanations and cannot be used for complete analysis.
No results found may be due to filtering, permissions, unconnected objects, or non-existent data. Only report "No results found in the current scope" without additional evidence.

写入纪律

Writing Discipline

执行前确认当前企业、用户、稳定目标、动作和关键影响。用户已经明确授权同一目标与动作时不重复提问；目标不唯一、范围扩大或破坏性影响不清楚时先消歧。

qiqi 已提供专用业务命令时，不用名称相近的通用动作代替。
删除必须先理解预检查结果；只有用户明确要求删除且目标已确认时才使用
```
--yes
```
。
命令或动作定义过期时，重新读取当前帮助或动作描述，重新检查参数和影响；不得静默重放旧请求。
写调用超时、连接中断或返回不明确时标记为“状态未知”，优先按稳定引用、唯一编码或用户给出的业务事实核查；没有确认前不得盲目重试。
同一意图若用新记录替代，仍有效的旧记录必须处理或向用户声明遗留，不得只追加新记录。

Confirm the current enterprise, user, stable target, action, and key impacts before execution. Do not re-ask when the user has explicitly authorized the same target and action; disambiguate first when the target is non-unique, the scope is expanded, or the destructive impact is unclear.

When qiqi provides dedicated business commands, do not replace them with general actions with similar names.
For deletion, first understand the pre-check results; only use
```
--yes
```
when the user explicitly requests deletion and the target has been confirmed.
When commands or action definitions are outdated, re-read current help or action descriptions, re-check parameters and impacts; do not silently replay old requests.
Mark as "status unknown" when write calls time out, connections are interrupted, or returns are unclear; prioritize verification using stable references, unique codes, or business facts provided by the user; do not blindly retry without confirmation.
If a new record is used to replace the same intent, still valid old records must be processed or declared to the user as leftovers; do not only append new records.

按需读取

On-Demand Reading

需要确认 qiqi、profile 或解释错误时，读取 runtime-context.md。
需要发现对象、字段、候选值、视图或单记录时，读取 object-discovery.md。
需要查询记录列表、构造过滤条件、排序分页或判断查询完整性时，读取 list-query.md。
需要解释或传递时间值时，读取 temporal-values.md。
需要提交、撤回、删除或处理未知写入结果时，读取 actions-and-recovery.md。
需要处理待审批事项或附件时，读取 approvals-and-attachments.md。

只读取当前任务需要的引用文件。

Read runtime-context.md when needing to confirm qiqi, profile, or explain errors.
Read object-discovery.md when needing to discover objects, fields, candidate values, views, or single records.
Read list-query.md when needing to query record lists, construct filter conditions, sort and paginate, or judge query completeness.
Read temporal-values.md when needing to interpret or pass time values.
Read actions-and-recovery.md when needing to submit, withdraw, delete, or handle unknown write results.
Read approvals-and-attachments.md when needing to handle pending approvals or attachments.

Only read reference files required for the current task.