Campus Account (校园号)
Business routing
Read the guide relevant to the user's task. Load other guides only when the task or a command result requires them.
| Business domain | Reference |
|---|---|
| School Library (校本库) and Lesson Preparation (备课空间) | references/school-library/SKILL.md |
Command execution
1. Run commands
Run scripts/yunzhi-cli.cjs with Node. Resolve script paths relative to this Skill directory. For example, list the Lesson Preparation root:
node scripts/yunzhi-cli.cjs lesson-prep ls / --limit 100
For complete command usage, follow the selected guide's command index or consult the command's --help. Existing knowledge can be reused; neither is a mandatory extra read.
2. Interpret results
Business commands return JSON on stdout or stderr. Use ok to determine success or failure.
| Result | Meaning and next step |
|---|---|
ok=true |
Success. Use the business fields in data to determine the completed state, and data.message for the next step relevant to the user’s task. |
ok=false |
Failure. Read error.message for the explanation and use error.hint, error.type, error.subtype, and other returned fields with the relevant guide to determine the next step. |
For login or authorization errors, or requests to check identity or switch accounts or organizations, read references/auth/SKILL.md. For other errors, follow the business guide and report the actual message; do not invent a cause or recovery action. If no valid JSON is returned, use the exit code and error output to assess execution. Do not repeat an operation that the result says has already completed.
3. Boundaries and precautions
- Use the CLI for Campus Account operations; the CLI manages login credentials.
General commands
- Version: report the installed release version.
- Configuration: change the business service address only when requested.
Only route supported domains listed above; explain unsupported requests instead of guessing internal APIs. For multi-domain tasks, preserve the user goal, current identity and organization, and valid object IDs between steps. Do not pass credentials.
A timeout or unreadable response does not prove a write failed. Report uncertainty and stop; do not retry or start automatic verification. Counts and claims about all results require complete results or reliable statistics; otherwise describe the known range.
