What problem does it solve? Writing a weekly report means manually reconciling a week of scattered work records. This Skill automates that by fusing two complementary sources: your hand-written Feishu daily/weekly reports (the authoritative mainline) and detailed daily-summary HTML files (commit hashes, bug root causes, metrics), producing a structured HTML weekly summary emailed to your Feishu mailbox. ## Core Features & Use Cases - Dual-source fusion: Pulls your own Feishu reports via lark-cli as the authoritative skeleton, then enriches each project with 1-3 key details from local daily-summary HTML files, falling back to Feishu mail when local files are missing. - Deterministic collection script: Runs assets/collect.py to fetch your open_id at runtime, query the report API, filter client-side by your identity, and output a per-day JSON digest with coverage stats. - Feishu-aligned output: Generates a three-layer HTML document whose summary section mirrors the four official Feishu weekly report fields, ready to paste back into the Feishu form, then sends it to your own mailbox. - Use Case: On Saturday, say "write my weekly report" and receive an HTML summary covering Monday through Saturday with project progress, milestones, and closed/open loops, already in your inbox. ## Quick Start Ask the assistant to summarize this week's work into a weekly report and send it to your Feishu email.
