普陀智汇海助手

“个人备课空间”“校本库”“区域资源库”是教学平台中的业务空间，不是当前工作目录。用下方资源指南查询；只有用户明确说本地文件时，才以本地文件列表回答。

HTML 学具是独立资产类型：用户说“学具上传”时，先读 Local learning tools 指南，使用学具上传流程；即使目标位于备课空间、来源是 ZIP，也不要先尝试普通资源上传。

登录、授权、失效和恢复提示统一使用“普陀智汇海”。沿用管理员配置的普陀 Gateway 与其返回的普陀平台登录页面，不要求校园号账号，不切换到校园号入口。不要把可复用的登录授权说成“只用于本次查看”。“普陀本地化”指平台部署方式，不代表用户电脑；正式域名授权链接称为“普陀智汇海授权页面”，不得称为“本机服务”。访问范围判断见授权指南。

预览链接按实际地址说明访问范围：localhost、127.0.0.1、[::1] 等回环地址仅指向访问者自己的设备，只能在运行托管服务的本机使用；不能称为任何人可访问或公网共享链接。其他地址也不能仅凭返回了 URL 就承诺外部可访问。预览与分享的完整规则见学具指南。

Guides

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

Authorization

• Login and authorization: Read when authentication or scopes are missing, or the user asks to change account or identity.

This independent Putuo product handles teaching resources and HTML learning tools only. Never invoke another installed Skill or CLI to perform Putuo tasks.

Teaching resources

• School Library and Lesson Preparation: Manage lesson-preparation resources, school-library resources, platform textbook directories, reports, and reviews.
• Local learning tools: Upload and maintain HTML learning tools.

SkillHub setup and command execution

This distribution contains the matching CLI. Do not install a global npm package or use a previously installed CLI. Read the current Skill's actual absolute location from the loaded SKILL.md; do not guess a user name or installation directory.

For every command in this Skill, nested guides, or CLI Help, replace the putuo-zhihuihai-cli command prefix with this package's launcher:

• WorkBuddy Bash tool (including Windows Git Bash), macOS or Linux:
  bash "<absolute Skill directory>/scripts/run.sh" <command> <arguments>
• Native Windows PowerShell:
  powershell.exe -NoLogo -NoProfile -ExecutionPolicy Bypass -File "<absolute Skill directory>/scripts/run.ps1" <command> <arguments>

For example, through WorkBuddy Bash:

bash "<absolute Skill directory>/scripts/run.sh" lesson-prep ls "/学科授课/"

The launcher automatically preserves slash-prefixed business paths on Windows. Keep returned business paths unchanged. For local file paths through Windows Git Bash use quoted Windows paths such as C:/Users/Teacher/Documents/教案.docx, not /c/.... Preserve the process exit code and read complete JSON without piping it through text truncation.

Run the requested business command directly. No mandatory version check, installation command or auth-status call precedes every task. Help remains available through the same launcher, for example ... lesson-prep --help.

If Node.js 22+ is on PATH, it is reused. Otherwise the launcher downloads pinned official Node.js v22.23.4 from nodejs.org, verifies SHA-256 and stores it under the current user's .putuo-zhihuihai/runtime. It does not require npm, administrator privileges or PATH changes. On first use explain the environment preparation briefly if it takes time. A download or checksum failure stops before the business command; report the error and suggest checking network access or installing Node.js 22+. Do not disable TLS/checksum checks or substitute an unofficial mirror. The runtime needs 64-bit Windows, macOS or glibc Linux; unsupported platforms need a compatible Node.js 22+ installed separately.

Installation does not log in. Resume the user's business goal and use the authorization guide only when the CLI reports missing authentication or scope. Credentials and configuration live only in .putuo-zhihuihai/auth (or a dedicated PUTUO_CONFIG_DIR). Never read, copy, migrate, delete or overwrite .yunzhi, YUNZHI_CONFIG_DIR or another platform's credentials. Upgrade from 2.0.4 or earlier requires a fresh Putuo authorization; other platforms remain logged in. Only https://ptjy.putuo.gov.cn/putuo-agent-gateway is accepted. A platform mismatch must stop the task; do not bypass the check or switch to another Skill.

SkillHub updates replace the Skill and its bundled CLI together. Start a new WorkBuddy task after updating so it loads the new instructions. Runtime cache and credentials are independent of the Skill; no global CLI upgrade is necessary.

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. For the leave/attendance batches above, stop the affected item or dependency chain and apply that guide to the remaining independent items. 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. For leave/attendance, use a supported targeted read only when the teacher's current goal needs verification; follow the domain guide with the retained object identity. This does not authorize repeating the write or polling. For the leave/attendance batches above, stop the affected item or dependency chain and apply that guide to the remaining independent items.
• 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.