菜单
Turn the week's tally into a short review — what shipped, what slipped, what went quiet — plus proposals for next week. Propose-only — the review changes nothing by itself. Use as the closing step of the weekly review workflow.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AutomatedMarketer/agent-team-template --skill write-weekly-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Apply the week's learning to the team's written rules, raise everything that would rewire the team as a task card, and write the one-page tune-up report. Use as the closing step of the weekly tune-up.
Write the run-log entry that records what this run did. Use at the end of every agent run, scheduled or manual, before committing.
Turn the owner's reaction to a draft — shipped, edited, or binned — into a filed verdict and a written rule, so the same correction never has to be made twice. Use whenever the owner says what they did with a piece the team produced.
正在显示 SKILL.md
| name | write-weekly-review |
| description | Turn the week's tally into a short review — what shipped, what slipped, what went quiet — plus proposals for next week. Propose-only — the review changes nothing by itself. Use as the closing step of the weekly review workflow. |
| audience | team |
One page, read on a Friday afternoon or a Monday morning. It says what the team did, what it did not, and what to change — and then it stops. Propose-only: this review recommends; a person decides. Nothing gets edited, rescheduled, or disabled by this run.
Write one file to the workflow's output path:
# Weekly review — week ending <date>
**The week in one line:** <the single most important thing that happened or failed
to happen.>
## Shipped
<What got produced, per agent. Link each line to its artifact.>
## Slipped
<Runs that failed, blocked, or came back partial. The reason, quoted from the run
log, and the log's path.>
## Gone quiet
<Agents or workflows with no runs this week. This section leads if anything is in it —
a silent worker outranks a busy one.>
## Proposals for next week
<Two or three at most. Each one: what to change, why the week's evidence says so,
and what saying yes would involve. Numbered, so the owner can answer "do 1 and 3".>
## Nothing was changed.
That last line is the contract. The proposals sit there until a person picks one.
Follow .claude/skills/run-log/SKILL.md. The review and the run log go in the same
commit — yes, the review of the run logs gets a run log. It is a run.
If you were told not to commit, do not commit — leave the review and the run log uncommitted together. What matters is that they move as one.