🧪 EXPERIMENTAL · Trial version / Preview — multi mode currently does not meet the stable standard. All dingtalk-* skills have passed the dispatch verifier, but interfaces, naming, and cross-skill references may be adjusted later; for production / shared environments, please prefer mono mode (
dws skill setup --mode mono). For issues, please file an issue for feedback.
PREREQUISITE: Read the
dws-sharedskill first for auth, global flags, product routing, URL preflight, error codes, and safety rules. Thedwsbinary must be on PATH.
⚠️ Command availability is subject to the current dws binary. Service discovery has been taken offline; this document is released along with the built-in skill; if
dws <cmd> --helpdoes not exist, it means the current version does not expose this command. If the command exists but the call fails, please confirm the static endpoint directory and backend tool registration according to the endpoint or tool hints in the error. Before the actual call, you can usedws <cmd> --helpor--dry-runto verify.
Command reference:agoal.md。
Intent table
| User says | Command |
|---|---|
| "Check strategy decoding / OGSM" | `dws agoal strategy list --scope-type <DEPT |
| "View strategy decoding details" | dws agoal strategy detail --profile-id <PROFILE_ID> |
| "Update strategy decoding" | First detail, then after modifying based on the complete data dws agoal strategy update ... |
| "Check business contract / KPI contract" | dws agoal contract list/detail/fields |
| "Update business contract" | First detail, then after modifying based on the complete dimensions dws agoal contract update ... |
| "Check scorecard" | dws agoal scorecard detail --selected-time <ISO> --dept-id <DEPT_ID> |
| "My goals / personal goals" | dws agoal user rules → dws agoal user objectives |
| "Weekly and monthly report submission statistics / follow-up reminders / late submission / not submitted" | dws agoal report list-statistics → dws agoal report submit-detail |
| "Goal template" | dws agoal obj-template list/create-or-update |
Hard constraints for write operations
strategy update/contract update/scorecard update/obj-template create-or-updateare all overwrite-style writes.- You must first read the existing details or template list, and modify based on the original data; it is forbidden to overwrite by passing only partial fields.
- Before execution, you must show the user the target object, modified fields, and a summary of the final command parameters, and wait for confirmation.