القائمة
Use when the user wants to manually append their own worklog or daily report row into the Univer workbook. Triggers include worklog-append, dogfooding-append, append, 记录进展, 手动写日报.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Internal core protocol for Univer worklog skills. Do not invoke directly from the skill menu; use univer-worklog-append, univer-worklog-auto, univer-worklog-report, univer-worklog-report-team, or univer-worklog-help instead.
Use when the user wants to automatically collect Codex/workbuddy/git/GitHub evidence, summarize work, dedupe it, and write or dry-run Univer worklog rows. Supports --dry-run, --confirm, --no-submit, and --period day|week|month.
Use when the user wants an AI-written interactive HTML team daily, weekly, or monthly report from all active members' Univer worklogs. Supports day, week, month, --period day|week|month, --date anchors, and natural-language dates such as 今天, 昨天, 本周, 上周, 本月, 上月. Triggers include worklog-report-team, dogfooding-report-all, 生成团队日报, 生成团队周报, 生成团队月报.
Use when the user wants an AI-written interactive HTML personal work report from their own Univer worklog. Supports day, week, month, --period day|week|month, --date anchors, and natural-language dates such as 今天, 昨天, 本周, 上周, 本月, 上月. Triggers include worklog-report, dogfooding-report, 生成我的日报, 生成我的周报, 生成我的月报.
Use when the user asks what Univer worklog commands are available or how to use them. Triggers include worklog-help, dogfooding-help, 查看 worklog 命令.
| name | univer-worklog-append |
| description | Use when the user wants to manually append their own worklog or daily report row into the Univer workbook. Triggers include worklog-append, dogfooding-append, append, 记录进展, 手动写日报. |
Use the core protocol in ../univer-team-standup/SKILL.md, route intent append.
Follow the core rules for profile onboarding, workbook reads/writes, priority resolution, dedupe key generation, audit logging, preview, and no default commit/sync. Always follow the core Team Remote policy: append writes and any requested publish/sync must target only fYmh0HRyTUO6YECQGFScnA0 on https://univer.ai/; re-check the bound unit id before pull, before writing, before commit/sync, and after sync. Always follow the core Personal Log Date Field Policy: write 日期 as the local work date, apply yyyy-mm-dd display formatting, and verify the date display is not a naked spreadsheet serial number. Always follow the core Progress And Risk Prompting Policy: before writing, remind the user to confirm or fill progress, risk, blocker, plan, and next-action fields.
During 2026-05-21 through 2026-06-18, apply the core Business Goal Tracking rules when the manual note clearly maps to an O1-O4 KR. Do not force a goal mapping for vague notes.
