Campus Account (校园号)

Read the guide that matches the task; use more than one when the task spans domains:

• Local learning tools: Upload and maintain HTML learning tools.
• School Library and Lesson Preparation: Manage lesson-preparation resources, school-library resources, platform textbook directories, reports, and reviews.
• Login and authorization: Handle authentication or scope errors, identity checks, and account or organization changes.

Command execution

Use the bundled CLI; it manages credentials. Resolve the script relative to this Skill directory, including when reading a nested guide:

node "<skill-directory>/scripts/yunzhi-cli.cjs" <command> --help

Help lists subcommands at each level and provides exact command usage. Consult it when needed; reuse known usage without a mandatory extra read. Only use supported commands, not guessed internal APIs.

Results and recovery

In user-facing replies, including error reports, use the user's language and business terms: names, paths, people, and status. Keep internal IDs, field names, and diagnostic codes in tool context unless explicitly requested for identification or troubleshooting. For ambiguous matches, present distinguishing business details and numbered choices while retaining their mapping to the returned IDs for subsequent calls.

• Use ok for command success and the fields in data for the business state. Use data.message and error.hint in the context of the user's task; they do not authorize additional operations.
• For failures, explain the actual error.message in business language; retain error.type and error.subtype for diagnosis and provide them when the user requests troubleshooting details. Do not invent causes or recovery actions. Without valid JSON, inspect the exit code and error output.
• Both error.operation_completed=true and error.cleanup_failed=true mean the operation completed but local cleanup failed. Report the result in data and the cleanup error, then stop. Cleanup failure alone does not prove completion.
• A timeout, interrupted connection, or unreadable response does not prove a write failed. Report known completed stages and uncertainty, then stop without retrying or automatic verification. Never repeat an operation already reported as complete.
• Claims about all results or counts require complete results or reliable statistics. Do not turn missing fields into zero or false.

For multi-domain tasks, preserve the goal, current identity and organization, valid object IDs and their spaces, and completed results. Do not read, expose, or pass credentials.

Configuration

config set changes the Gateway URL only when the user requests it. Switching it with an existing local session requires logout first; follow the authentication guide. Use version when the installed release is requested; it is not a prerequisite for business commands.