weekly-report

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Weekly Report

Purpose

这个 skill 用于生成一份可直接发送的工作周报。

周报的核心目标是：

说明目标时间范围内的核心工作主题
说明每项工作对应的证据来源
区分完成、推进中、待排期、仅讨论
还原协作沟通重点
给出与事实一致的下周计划

This skill is used to generate a work weekly report that can be sent directly.

The core objectives of the weekly report are:

Explain the core work topics within the target time range
Explain the evidence source corresponding to each work
Distinguish between completed, in progress, to be scheduled, and only discussed
Restore the key points of collaborative communication
Provide next week's plans consistent with the facts

Success Criteria

一份合格周报必须满足：

时间范围明确且正确
周报主体按“工作主题”组织
每项核心工作有至少两类证据支撑，或明确标注证据不足
事实内容与推断内容分开表达
用户可以直接发送，不需要再手工补大段背景

如果做不到以上几点，这份周报就不算完成。

A qualified weekly report must meet the following requirements:

The time range is clear and correct
The main body of the weekly report is organized by "work topics"
Each core work has at least two types of evidence support, or is clearly marked as insufficient evidence
Factual content and inferred content are expressed separately
Users can send it directly without manually adding a large section of background

If the above points are not met, this weekly report is not considered complete.

Time Semantics

Default Rule

用户明确说“本周周报”：
- 取本周周一到当前日期
用户没有明确说“本周”：
- 默认取上周周一到周日

Users explicitly say "本周周报": take the period from this Monday to the current date
Users do not explicitly say "本周": the default is from last Monday to last Sunday

Explicit Rule

```
本周
```
：本周周一到当前日期
```
上周
```
：上周周一到周日
```
3月24日那周
```
：包含该日期的自然周，范围为周一到周日

```
本周
```
: Monday of the current week to the current date
```
上周
```
: Monday of last week to Sunday of last week
```
3月24日那周
```
: The natural week containing the specified date, ranging from Monday to Sunday

Required Behavior

开始采集前，必须先输出绝对日期范围，不能只说“本周”或“上周”。

示例：

text

本次周报范围：2026-03-16 00:00:00 +08:00 ~ 2026-03-22 23:59:59 +08:00
覆盖日期：2026-03-16 ~ 2026-03-22

Before starting collection, you must first output the absolute date range, not just "本周" or "上周".

Example:

text

本次周报范围：2026-03-16 00:00:00 +08:00 ~ 2026-03-22 23:59:59 +08:00
覆盖日期：2026-03-16 ~ 2026-03-22

Core Model

Channel

Channel

表示一个可独立接入的信息来源。

每个通道应归属于一个

channel_family

：

```
collab_platform
```
```
git
```
```
agent
```
```
local_docs
```

每个通道只声明自己提供哪些能力，不负责决定周报结构。

Channel

represents an independently accessible information source.

Each channel should belong to a

channel_family

```
collab_platform
```
```
git
```
```
agent
```
```
local_docs
```

Each channel only declares what capabilities it provides, and is not responsible for determining the structure of the weekly report.

Capability

Capability

表示一个通道能够提供的具体采集能力。

推荐使用这些能力名：

```
calendar
```
```
meeting_notes
```
```
docs_search
```
```
docs_fetch
```
```
message_search
```
```
git_history
```
```
agent_history
```
```
file_metadata
```

Capability

represents the specific collection capability that a channel can provide.

These capability names are recommended:

```
calendar
```
```
meeting_notes
```
```
docs_search
```
```
docs_fetch
```
```
message_search
```
```
git_history
```
```
agent_history
```
```
file_metadata
```

Evidence

Evidence

表示一条已归一化的证据对象。

每条证据至少应尽量包含：

```
source_family
```
```
source_channel
```
```
evidence_type
```
```
title
```
```
summary
```
```
timestamp
```
或时间范围
```
actors
```
```
project_or_topic
```
```
url_or_path
```
```
confidence
```

常用

evidence_type

：

```
meeting
```
```
meeting_notes
```
```
doc
```
```
message
```
```
commit
```
```
agent_session
```
```
file_metadata
```

Evidence

represents a normalized evidence object.

Each piece of evidence should try to include at least:

```
source_family
```
```
source_channel
```
```
evidence_type
```
```
title
```
```
summary
```
```
timestamp
```
or time range
```
actors
```
```
project_or_topic
```
```
url_or_path
```
```
confidence
```

Common

evidence_type

```
meeting
```
```
meeting_notes
```
```
doc
```
```
message
```
```
commit
```
```
agent_session
```
```
file_metadata
```

Work Topic

Work Topic

表示一组围绕同一项目、功能、专项或目标归并后的工作主题。

每个工作主题至少要回答：

这项工作是什么
当前状态是什么
有哪些关键结论
由哪些证据支撑
下周是否继续推进

Work Topic

represents a group of work topics merged around the same project, function, special project or goal.

Each work topic should answer at least:

What is this work
What is the current status
What are the key conclusions
What evidence supports it
Whether to continue to promote it next week

Pipeline

Step 1: Resolve Time Range

先解析时间范围，再开始采集。

如需稳定计算周范围，优先使用：

```
scripts/resolve_week_range.py
```

脚本说明见：

```
references/time.md
```

Parse the time range first, then start collection.

If you need to calculate the week range stably, use first:

```
scripts/resolve_week_range.py
```

For script instructions, see:

```
references/time.md
```

Step 2: Discover Channels

检查当前环境有哪些通道可用：

协作平台通道
Git 通道
Agent 通道
本地文档通道

只对已发现的通道继续采集。

Check which channels are available in the current environment:

Collaboration platform channel
Git channel
Agent channel
Local document channel

Only continue to collect data for discovered channels.

Step 3: Inspect Capabilities

对每个已发现通道，确认其可用能力。

例如：

协作平台可能支持
```
calendar
```
、
```
docs_search
```
、
```
message_search
```
Git 通道可能支持
```
git_history
```
Agent 通道可能支持
```
agent_history
```

通道只具备部分能力时，也允许继续执行。

For each discovered channel, confirm its available capabilities.

For example:

Collaboration platform may support
```
calendar
```
,
```
docs_search
```
,
```
message_search
```
Git channel may support
```
git_history
```
Agent channel may support
```
agent_history
```

When the channel only has partial capabilities, execution is still allowed to continue.

Step 4: Collect Raw Facts

按通道并行采集原始信息，优先采集：

协作平台中的会议、纪要、文档、消息
Git 历史
Agent 历史
本地文档与导出文件

Collect original information in parallel by channel, priority collection:

Meetings, minutes, documents, messages in the collaboration platform
Git history
Agent history
Local documents and exported files

Step 5: Normalize Evidence

把原始结果整理为统一的

Evidence

。

归一化后，至少应支持按以下维度聚合：

时间
项目 / 主题
人
证据类型
来源通道

Organize the original results into unified

Evidence

After normalization, it should support aggregation at least by the following dimensions:

Time
Project / Topic
Person
Evidence type
Source channel

Step 6: Extract Candidate Topics

优先从高信号内容提取候选工作主题：

Git 提交主题
文档标题与摘要
会议标题与会议纪要总结
消息中的高频关键词
Agent 任务目标

Extract candidate work topics from high-signal content first:

Git commit topics
Document titles and abstracts
Meeting titles and meeting minute summaries
High-frequency keywords in messages
Agent task objectives

Step 7: Merge Into Work Topics

按主题将证据归并成

Work Topic

，并判断：

这些证据是否指向同一项工作
当前状态是已完成、推进中、待排期还是仅讨论
哪些结论可以进入周报正文

Merge evidence into

Work Topic

by theme, and judge:

Whether these evidence point to the same work
Whether the current status is completed, in progress, to be scheduled or only discussed
Which conclusions can be included in the main body of the weekly report

Step 8: Validate Topics

每个工作主题都应尽量完成跨证据验证。

优先验证的组合：

```
meeting
```
+
```
doc
```
```
doc
```
+
```
commit
```
```
commit
```
+
```
agent_session
```
```
message
```
+
```
meeting
```
/
```
doc
```

若某项工作仅命中单一证据来源：

先尝试补证
若无法补证，则降低置信度
在结果中明确说明证据不足

Each work topic should try to complete cross-evidence verification.

Priority verification combinations:

```
meeting
```
+
```
doc
```
```
doc
```
+
```
commit
```
```
commit
```
+
```
agent_session
```
```
message
```
+
```
meeting
```
/
```
doc
```

If a work only hits a single evidence source:

Try to supplement evidence first
If evidence cannot be supplemented, reduce the confidence
Clearly indicate insufficient evidence in the results

Step 9: Write The Report

按工作主题组织最终周报，不按平台或通道罗列原始数据。

Organize the final weekly report by work topics, do not list raw data by platform or channel.

Implementation References

平台或通道实现细节不要堆在本文件中，按需读取：

协作平台 Lark / 飞书：
```
references/lark.md
```
Git 通道：
```
references/git.md
```
Agent 通道：
```
references/agent.md
```
本地文档通道：
```
references/local-docs.md
```

Do not pile up platform or channel implementation details in this file, read as needed:

Collaboration platform Lark / Feishu:
```
references/lark.md
```
Git channel:
```
references/git.md
```
Agent channel:
```
references/agent.md
```
Local document channel:
```
references/local-docs.md
```

Channel Contract

Channel Contract

用来规范一个新平台如何接入本 skill。

主文档只保留契约入口，具体字段要求与降级行为见：

```
references/channel-contract.md
```

Channel Contract

is used to standardize how a new platform accesses this skill.

The main document only retains the contract entry, and the specific field requirements and degradation behavior see:

```
references/channel-contract.md
```

Evidence Rules

Evidence 规则用于定义证据优先级、置信度判断和写作边界。

具体规则见：

```
references/evidence.md
```

Evidence rules are used to define evidence priority, confidence judgment and writing boundaries.

For specific rules see:

```
references/evidence.md
```

Degrade And Stop Rules

Degrade

以下情况允许降级执行：

缺少消息能力
缺少 Agent 通道
缺少部分文档元数据
某个通道只支持部分能力

降级执行时必须明确说明：

缺了哪些能力
可能丢失哪类信息

The following situations allow degraded execution:

Lack of message capability
Lack of Agent channel
Lack of part of document metadata
A channel only supports partial capabilities

When performing degraded execution, you must clearly explain:

What capabilities are missing
What type of information may be lost

Stop

只有在无法支撑基本事实判断时才停止执行。

例如：

没有有效时间范围
没有任何可用通道
所有通道都无法提供可读证据

停止时必须明确说明：

当前缺少哪些通道或能力
为什么结果不可靠
若要继续，需要补什么环境或权限

Execution is stopped only when basic fact judgment cannot be supported.

For example:

No valid time range
No available channels
All channels cannot provide readable evidence

When stopping, you must clearly explain:

What channels or capabilities are currently missing
Why the result is unreliable
What environment or permissions need to be supplemented to continue

Output Spec

输出结构与模板见：

```
references/output.md
```
```
assets/report-template.md
```

For output structure and template see:

```
references/output.md
```
```
assets/report-template.md
```

weekly-report

Original

Translation

Weekly Report

Weekly Report

Purpose

Purpose

Success Criteria

Success Criteria

Time Semantics

Time Semantics

Default Rule

Default Rule

Explicit Rule

Explicit Rule

Required Behavior

Required Behavior

Core Model

Core Model

Channel

Channel

Capability

Capability

Evidence

Evidence

Work Topic

Work Topic

Pipeline

Pipeline

Step 1: Resolve Time Range

Step 1: Resolve Time Range

Step 2: Discover Channels

Step 2: Discover Channels

Step 3: Inspect Capabilities

Step 3: Inspect Capabilities

Step 4: Collect Raw Facts

Step 4: Collect Raw Facts

Step 5: Normalize Evidence

Step 5: Normalize Evidence

Step 6: Extract Candidate Topics

Step 6: Extract Candidate Topics

Step 7: Merge Into Work Topics

Step 7: Merge Into Work Topics

Step 8: Validate Topics

Step 8: Validate Topics

Step 9: Write The Report

Step 9: Write The Report

Implementation References

Implementation References

Channel Contract

Channel Contract

Evidence Rules

Evidence Rules

Degrade And Stop Rules

Degrade And Stop Rules

Degrade

Degrade

Stop

Stop

Output Spec

Output Spec

Completion Checklist

Completion Checklist