Write a 3P update for the Mobile team, week of Sept 29 to Oct 3. Progress: shipped order export (CSV), first-day usage 320 times; fixed the duplicate payment callback bug; cold start time 2.8s -> 1.9s. Plans: Excel export and pagination for large datasets; unit tests for the permission service. Problems: crash rate on low-end Android is 0.8% and we lack an engineer to investigate; settings page redesign is delayed by late design files.
📱 Mobile Team (Sept 29 – Oct 3)
Progress: Shipped CSV order export, which was used 320 times on its first day. Fixed the duplicate payment callback bug and cut cold start time from 2.8s to 1.9s.
Plans: Build Excel export and pagination for large datasets. Write unit tests for the permission service.
Problems: The crash rate on low-end Android is 0.8% and we have no engineer available to investigate. The settings page redesign is delayed because the design files arrived late.
Real run, output shown verbatim. The skill read examples/3p-updates.md and followed its fixed format.
它做什麼
幫助模型按統一格式撰寫內部溝通內容。它先判斷溝通類型，載入對應的指引檔，再遵循該檔案規定的格式、語氣與內容要求。
包含的格式
- 3P 週報：Progress、Plans、Problems。固定的簡短格式，30 到 60 秒即可讀完。
- 公司簡報：約 20 到 25 條簡短要點，依板塊分組，採用「我們」的口吻。
- FAQ 回覆：彙整許多員工都在問的問題，並簡潔作答。
- 一般溝通：先問清楚讀者、目的與語氣。
如果你沒有提供內容，它會向你詢問。如果你的代理連接了 Slack、Google Drive、電子郵件或行事曆，這個 Skill 會讓模型從這些來源蒐集背景資訊。
純指令檔，沒有腳本。可選擇性依賴外部服務：如果你的代理連接了 Slack、Google Drive、電子郵件或行事曆，這個 Skill 會讓模型讀取它們來蒐集背景資訊。請只連接你放心讓它讀取的來源；沒有權限時，它只會向你索取內容。