之江微校校本库
Use zjer-cli for the user's task. Read the relevant guide before acting:
- Authorization: login, identity changes, additional permissions and logout.
- Resources: browse, search, read, transfer and organize resources, folders and textbooks; add references; open province pages.
- Reports: submit personal uploads to the school, inspect records or cancel a submission.
- Reviews: inspect school submissions and their originals, preview approval destinations, approve or reject.
Regional reporting, learning tools and questions are outside this Skill.
CLI setup
Prepare the CLI for the teacher. Use an existing zjer-cli version 0.1.5; if missing or a different version is installed, use Node.js 22+ and npm to install this version once:
npm install -g @zjer/zjer-cli@0.1.5 --registry=https://registry.npmjs.org/
Verify with zjer-cli version. If installation fails or the version differs, stop and report the specific problem.
Use the CLI's default Portal https://szyx.zjer.cn/yunzhi-api/portal, without a local-test ZJER_PORTAL_URL override. Keep TLS verification enabled. Follow the authorization guide for login.
Usage
Use zjer-cli <command> --help for parameters and required scopes; in Windows PowerShell/cmd use zjer-cli.cmd. Select the user's intended school or personal space and use IDs and paths returned by the CLI. Resolve ambiguous targets before writing. The CLI owns credential storage; never read or expose credentials or ask the user for tokens.
Execute clear, authorized requests directly. For deletion, make the target and impact clear; an explicit request needs no repeated confirmation. Review decisions follow the review guide.
Read the complete JSON response. Report success only when ok: true and the operation's result confirms completion. For batches, distinguish completed, failed and unexecuted items.
Handle errors by their cause:
- Parameter errors: consult Help and correct the call within the user's request.
- Missing scope: follow the authorization guide. Business permission refusals and dependency failures: report the returned reason and stop.
- Unknown write outcomes: inspect current state before considering another write; never automatically repeat a write that may have succeeded. Preserve earlier successes and any reported partial files.
Use returned error codes and diagnostic details when explaining failures; distinguish confirmed causes from guesses. Reply in the user's language using business names, keeping internal IDs and setup details out of ordinary teacher-facing answers.
