Many Chinese companies run on DingTalk, and its log feature asks staff to submit a daily, weekly or monthly report into fixed fields. The fields are small and usually filled in on a phone, so a good log is short, specific and honest about what slipped. This skill turns rough notes into entries for each field.
Write in Simplified Chinese unless asked otherwise. For a long-form weekly report outside DingTalk, see cn-weekly-report.
What This Skill Produces
- The log, field by field, matching DingTalk's default templates:
- Daily report: Today's completed work / Unfinished work / Work needing coordination / Remarks
- Weekly report: Work completed this week / Weekly work summary / Next week's work plan / Coordination and help needed
- Monthly report: Work content this month / Monthly work summary / Next month's work plan / Help and support needed
- A one-line version to the team group (群消息)
- A carry-over note: items moved from Unfinished yesterday that still are not done
Required Inputs
Ask for these if not provided:
- Log type: daily report, weekly report or monthly report
- The notes: what was done, in any form
- Yesterday's or last period's log, if available, so carry-overs are tracked
- The company's own template fields, if they differ from the defaults; follow them
Framework
- One line per item. Each entry starts with a verb and ends with a result or status: "Completed joint debugging of the order export interface, submitted for testing", not "order export".
- Numbers where they exist. Counts, percentages, ticket numbers. Do not invent any.
- Unfinished is honest. Each unfinished item gets a reason and a new date: "Payment callback testing not completed: test environment certificate expired, have contacted ops, expected to be completed tomorrow morning".
- Needs Coordination names a person or team and what is needed from them by when. An empty field is fine; a vague one is not.
- Weekly and monthly summaries add judgement. Work Summary says what went well, what did not and what will change, in two or three lines, not a repeat of the list.
- Fit the phone. Keep each field to about five lines; put detail behind a doc link if needed.
Output Format
【今日完成工作】
1. [动词 + 事项 + 结果 / 状态]
2. ...
【未完成工作】
1. [事项]：[原因]，[新的完成时间]
【需协调工作】
1. [需要谁] [做什么] [何时之前]
【备注】
[可选：链接、明日重点]
Group message version：[one sentence: today's most important result + the coordination needed]
For weekly reports and monthly reports, use the matching field names listed above, with Work Summary written as two or three lines of reflection.
Quality Checks
- Every completed item starts with a verb and states a result or status
- Every unfinished item has a reason and a new date
- Every coordination request names who, what and by when
- Items carried over from the previous log are marked (Carried Over)
- No number, ticket or name appears that the person did not provide
- Each field is about five lines or fewer
Anti-Patterns
- "progressing normally". It says nothing. State the status or the next step.
- Copying yesterday's log. Managers notice. Carry-overs are marked, not repeated silently.
- Hiding blockers in Remarks. A blocker belongs in Unfinished or Needs Coordination, where it is seen.
- Padding. A short honest log reads better than a long one stuffed with routine tasks.
Example Trigger Phrases
- "Help me write today's DingTalk daily report, notes are here."
- "How do I write a DingTalk weekly report? Help me organize this week's work."
- "Fill in my DingTalk daily log from these notes."
- "Write the monthly report, and make next month's plan a bit more specific."