Weekly report standard
Skill VioletScar-Hui/Build_Great_Loop/skill-craft/examples/weekly-report-standard
A composable Loop Engineering skill group for Codex and Claude Code - interview your task and emit a top-tier, paste-ready agentic loop (harness). 4 skills: spec, engineering, eval, review.
npx -y skills add VioletScar-Hui/Build_Great_Loop --skill weekly-report-standardAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
在撰写或审阅团队周报时提供格式与内容规范。当用户说"写周报"、"检查周报格式"、 "周报该怎么写"时调用。覆盖结构、量化表达和禁忌项。不适用于日报、月度总结或 绩效自评（各有其模板）。
SKILL.md
1.7 KB, as published. Nobody here has run it
团队周报规范
<!-- 示例说明：这是 skill-craft 方法论产出的完整小示例（骨架 C 规范型 + 评测 先行）。写新 skill 时对照它的"完成形态"：description 四原则齐备、原则统帅规则、 规则带原因、有检查清单、有排除边界、evals 与 SKILL.md 同在。 -->核心原则
规则未覆盖的情况从这里推导。
- 读者是跨组同事：不写只有本组懂的黑话。
- 量化优先：能给数字不给形容词。
- 风险先说：坏消息放最前，不埋在末尾。
规范详情
| 规则 | 正确 ✅ | 错误 ❌ | 原因 |
|---|---|---|---|
| 三段结构 | 进展 / 风险 / 下周计划 | 流水账混排 | 读者 30 秒定位所需信息 |
| 进展量化 | "完成迁移 340/500 表" | "迁移进展顺利" | 形容词无法对齐预期 |
| 风险给动作 | "延期风险：需 DBA 本周三前批权限" | "有一些风险" | 没有动作的风险=没说 |
| 计划可验收 | "下周五前出压测报告" | "继续推进压测" | 可验收才能被跟进 |
检查清单（交周报前逐项确认）
- 三段齐全且顺序正确
- 每条进展有数字或可验证事实
- 每条风险配了负责人与时限
- 无内部黑话（陌生同事读得懂）
本规范不覆盖
- 日报 / 月度总结 / 绩效自评（另有模板）