dream-num/dogfooding · Archived

univer-worklog-report-team

Use when the user wants an AI-written interactive HTML team daily, weekly, or monthly report from all active members' Univer worklogs.

First seen May 20, 2026

Installation

$ npx skills add dream-num/dogfooding --skill univer-worklog-report-team

Summary

  • 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, 生成团队日报, 生成团队周报, 生成团队月报.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from dream-num/dogfooding.

npx skills add dream-num/dogfooding

Browse all from dream-num/dogfooding

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,129 B
  • docs SUMMARY.md 440 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

univer-worklog-report-team

Use the core protocol in ../univer-team-standup/SKILL.md, route intent team report.

Default period is day. Resolve --period, --date, and natural-language date aliases through the core Report Date Resolution rules before reading logs. Generate .html by default. The report must read both active People rows and actual log__ / legacy log_ sheets so log-only contributors are not missed when a People row is absent or stale, filtering by normalized Personal Log 日期 values and warning on repairable numeric date displays. For periods overlapping 2026-05-21 through 2026-06-18, follow the core PMO OKR focus requirements as P1 presentation-layer behavior: include 业务目标追踪 — OKR 进度 for O1-O4 as the first sub-section of 晨会聚焦; do not render a separate generic 业务目标概览; do not change data collection or storage logic. Use the PMO morning-meeting format from the core protocol: team summary first, 晨会聚焦 with 业务目标追踪 — OKR 进度, objective-grouped 重大进展同步, 重要风险点, 需沟通事项, then 每人晨会要点, compact member cards with delay-risk tags, and detailed rows collapsed for after-meeting follow-up. In 重大进展同步, group strictly by O1 SpreadsheetBench, O2 Agent Builder, O3 Code as Spreadsheet, O4 SDK→CLI, and 基建 & 其他, omitting empty groups and sorting delivered outcomes before in-progress items. Include blockers/risks, evidence links, filters, copy summary, print mode, and the HTML interactions defined in the core protocol. Use Markdown only if the user explicitly requests it.