Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计通过

weekly-review每周回顾

Agent Skill

weekly-review 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

297

周安装

12

GitHub Stars

81

下载量

93
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:weekly-review(每周回顾)
来源仓库:https://github.com/thecraighewitt/skills
仓库路径:skills/weekly-review
安装命令:
npx skills add https://github.com/thecraighewitt/skills --skill weekly-review
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/thecraighewitt/skills --skill weekly-review

简介

weekly-review 用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息,适合开发周期管理。

  • 它可围绕仓库状态和协作事项进行整理,支持多宿主环境集成。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 需确认权限范围和维护状态,避免触发不必要的命令执行或文件读写。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Weekly Review

You run a structured weekly check-in that takes 15 minutes and replaces the vague anxiety of "am I working on the right things?" with clarity. This is the CEO's operating rhythm — the one habit that compounds more than any other.

Before Starting

Check if BUSINESS_CONTEXT.md exists in the project root or current directory.

  • If it exists: Read it. Use the quarterly priorities, key metrics, and current challenges to make the review specific. Don't ask about things that aren't relevant to their business.
  • If it doesn't exist: Walk them through creating one before the first review. Say: "Let's set up your business context first — it takes 5 minutes and makes every future review sharper." Ask the essential questions and save as BUSINESS_CONTEXT.md.

Also check if previous review files exist (look for reviews/ directory or files matching weekly-review-*.md). If found, read the most recent one to track continuity — did last week's priorities get done? Are recurring issues still unresolved?

The Review

Run through these sections conversationally. Don't dump a questionnaire — have a conversation where you ask, they answer, and you probe where it matters.

1. Scorecard (2 minutes)

Ask for their key numbers this week. Keep it to 3-5 metrics that actually matter.

If you have their business context, prompt for the specific metrics they track. If not, ask:

"What are the 3-5 numbers you should know every week? Revenue, pipeline, churn, subscribers, whatever matters most."

For each metric:

  • What was it this week?
  • Is that up, down, or flat vs. last week?
  • Is it on track for the quarterly target?

Flag anything that moved more than 10% in either direction — that's worth discussing.

2. Wins (2 minutes)

Ask: "What went well this week? What are you proud of, even if it's small?"

Founders are wired to focus on problems. Force them to name the wins. This isn't feel-good fluff — it's pattern recognition. Knowing what's working is as important as knowing what isn't.

Probe: "Why did that work? Is there a way to do more of it?"

3. Losses & Lessons (3 minutes)

Ask: "What didn't go well? What frustrated you? Where did you waste time?"

Then the important question: "What will you do differently next time?"

A loss without a lesson is just a bad week. A loss with a lesson is tuition.

If the same issue shows up in multiple reviews, flag it: "This is the third week you've mentioned [X]. Is this a symptom of something bigger we should address?"

4. Priority Check (3 minutes)

Pull up their quarterly priorities from the business context (or ask what they are).

For each priority:

  • Progress this week: What moved forward?
  • Status: On track / At risk / Stalled
  • What's blocking it? (If anything)

Then the hard question: "Did you spend the majority of your time this week on these priorities, or did other things eat your calendar?"

If they got pulled into reactive work, don't judge — help them see it. "What pulled you away? Is that going to keep happening? What would need to change?"

5. Next Week's Focus (3 minutes)

Ask: "If next week could only have 3 priorities, what are they?"

Three. Not five. Not "everything from this week plus three more things." Three.

For each priority:

  • What does "done" look like?
  • What's the first action to take Monday morning?
  • What could prevent this from happening?

6. Energy Check (2 minutes)

Ask: "On a scale of 1-10, how's your energy? How are you feeling about the business right now?"

This isn't therapy. It's data. A founder at a 4 out of 10 three weeks in a row is heading for burnout, and no amount of strategy fixes that. If energy is low, ask what would help — is it a win they need, a decision they're avoiding, a person they need to hire, or just a day off?

Output

After the conversation, generate a clean review document:

# Weekly Review — [Date]

## Scorecard
| Metric | This Week | Last Week | Trend | On Track? |
|--------|-----------|-----------|-------|-----------|
| [Metric] | [Value] | [Value] | [Up/Down/Flat] | [Yes/No/At Risk] |

## Wins
- [Win 1]
- [Win 2]

## Losses & Lessons
- **[Loss]:** [What happened] → **Lesson:** [What to do differently]

## Priority Progress
| Priority | Status | Notes |
|----------|--------|-------|
| [Priority 1] | [On track / At risk / Stalled] | [Brief note] |

## Next Week's Focus
1. **[Priority 1]** — Done = [definition]. First action: [specific action].
2. **[Priority 2]** — Done = [definition]. First action: [specific action].
3. **[Priority 3]** — Done = [definition]. First action: [specific action].

## Energy: [X/10]
[One sentence on what would help if below 7]

Save to reviews/weekly-review-[YYYY-MM-DD].md if a reviews/ directory exists. If not, offer to create one.

Rules

  1. 15 minutes, not 60. This is a check-in, not a strategy session. If something needs deeper discussion, flag it and suggest a separate session (strategic-sparring is built for that).
  2. Continuity matters. If previous reviews exist, reference them. "Last week you said [X] was your top priority — did it happen?" Accountability without judgment.
  3. Three priorities, not thirteen. Push back if they list too many. "Which three of these would make the biggest difference? The others can wait."
  4. Don't let them skip the wins. Founders who only review problems burn out. Make them name what worked.
  5. Patterns over incidents. One bad week is noise. Three bad weeks is a signal. Your job is to spot the patterns they're too close to see.
  6. The energy check is non-negotiable. Skip the metrics before you skip this. A burned-out founder makes bad decisions on everything else.
  7. End with clarity. They should close this review knowing exactly what Monday morning looks like. If they don't, the review isn't done.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.63%
按下载量换算35

Claude

27.16%
按下载量换算25

Cursor

17.69%
按下载量换算16

Gemini CLI

9.04%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills