Qiqi Service Industry ERP qiqi
Applicable Scope
This Skill only handles the ready-to-use
runtime. Initial installation, update, reinstallation, missing CLI, OAuth access, or Agent Skills access are handled by
; return to this Skill to perform identity verification, queries, and business requests after installation is completed.
Authority Boundaries
Treat the current qiqi runtime as the authority for capabilities and syntax:
- Current commands and parameters are subject to 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 , , 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
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
, and then interpret the returned results.
| Trigger Condition | Necessary Checks |
|---|
| Business authorization failure, unclear profile, or changed identity | Use to verify the current enterprise and user online; explicitly pass for business commands as a priority |
| Unclear commands, objects, fields, values, views, or actions | Read the corresponding , and use , , or as needed |
| Non-unique names, order numbers, personnel, or records | First obtain candidates and disambiguate; writes must use stable , 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
| Intent | Priority Usage |
|---|
| View or verify identity | , |
| Discover object types | |
| View field types and temporal semantics | |
| View general fields and small data samples | |
| Find candidates by cross-object text | |
| Query records by object and conditions | |
| Find enumeration or reference candidate values | |
| Query using preset workbench views | First use to understand available views, then execute after matching |
| Read, delete business records, or perform submission, approval, and other business actions on the record | , , , |
| Process attachments | records attachments list/url/upload/delete
|
| Execute dedicated business commands | Start from the "Business Commands" section in , discover leaf commands level by level using parent command before execution |
is the general query entry for constructing conditions by object. For preset workbench views (such as "My Documents", "Awaiting My Approval"), use
first then match and execute; do not guess
if no match is found, nor reproduce the same view by executing
for each object one by one.
Actions like submission, withdrawal, approval, rejection are actions on current business records, which go through
and
. 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
- 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 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 can be displayed. Do not translate titles or guess based on titles.
- For disambiguation, write confirmation, and result verification, still display unique business codes or as needed; do not delete information that proves record identity for the sake of simplifying output.
- Samples from and candidates from 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 , read the complete JSON pointed to by ; and 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
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 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
- 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.