Weekly Report Automation

Writing a weekly report every Friday is one of the most common repetitive tasks. With a scheduled task, LanMate automatically pulls the week’s Lansenger messages and generates a weekly report draft — you just need to confirm and fine-tune it.

Skills Used

Built-in skills (installed with LanMate, ready out of the box): Lansenger integration (lanmate-lansenger), Word documents (lanmate-docx); automatic runs rely on the Scheduled Tasks feature (see the “Scheduled Tasks” guide)
Skill Store: Summary Writer — condense a week of chat material into weekly-report points

Pain Points

Reports rely on memory, missing important items handled during the week
Digging through group chat records for material is time-consuming and error-prone
Inconsistent formatting means re-formatting every time
Repeating the same process every week drains energy

Recommended Workflow

Step	Description
1 Create a scheduled task	Set frequency to “Every Friday 17:00” and execution mode to “Fixed conversation”
2 Set the task instruction	Describe what to do: pull this week’s Lansenger messages → summarize → generate in weekly report format
3 Automatic execution	Runs automatically at the scheduled time, generating a weekly report draft in the fixed conversation
4 Confirm and finalize	Return to the conversation to review the draft, ask follow-up questions, and output as Word

Prompt Examples

Scheduled Task Creation Instruction

Describe your needs and schedule in the conversation:

Every Friday at 5:00 PM, help me generate this week's work report.
Requirements:
1. Pull my Lansenger chat records for this week as source material
2. Organize the report with the following structure:
   - Main work completed this week
   - Work in progress and its status
   - Work plan for next week
   - Issues and risks needing coordination
3. Summarize each item in one sentence, with key results or data attached
4. Output a Word document

LanMate parses your description, generates a scheduled task card, and enables it once you confirm.

Weekly Report Generation Instruction (for Manual Triggering)

Please pull my Lansenger chat records for this week and organize them into a work report.
Structure: completed this week, in progress, next week's plan, risks and coordination.
Summarize each item in one sentence, with key results attached.
Do not fabricate content that cannot be confirmed from the records — mark it "to be supplemented."
Output a Word document.

Cross-Conversation Follow-Up

Add an item under "Completed this week": completed testing of the skills module for version V0.3.0,
found 3 issues and submitted them to the development team.
Add under "Risks and coordination": API integration depends on third-party progress,
which may affect next week's testing plan.

Acceptance Criteria

The report covers the week’s key work items, with data traceable to chat records
Consistent format (completed this week / in progress / next week’s plan / risks and coordination)
Content that cannot be confirmed from records is marked “to be supplemented” — no fabrication
Outputs a Word document ready for submission

Common Mistakes

Common Mistake	Why It Happens	Better Practice
Scheduled task fails because the client isn’t running	Shutting down the computer after work	Keep your computer on and LanMate running; or use “Run now” for manual triggering
Task instruction too vague (“help me write a report”)	Source material and structure not specified	Specify the source material (Lansenger messages), output structure, and format
Output format not specified	The model defaults to plain text	State explicitly in the instruction: “Output a Word document”
Report content doesn’t match actual work	The AI infers from fragmentary information	Manually confirm and fill in the parts marked “to be supplemented”