Agent skill

Weekly Review

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should…

MITAuto-check passedKnowledge Management

Install Weekly Review

skills CLI
$ npx skills add TheCraigHewitt/skills --skill weekly-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills weekly-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ceo/weekly-review .claude/skills/weekly-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
weekly-review
GitHub stars
159
Token cost
~1.6k tokens
SKILL.md length
831 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should…

  • Works in 6 steps: Scorecard (2 minutes) → Wins (2 minutes) → Losses & Lessons (3 minutes) → …
  • Wants to do a weekly review
  • SKILL.md covers Before Starting, The Review, Output and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Weekly Review is an agent skill from TheCraigHewitt/skills. When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should I focus on next week,' 'end of week check-in,' 'Sunday review,' 'weekly retro.' A structured CEO operating rhythm in 15 minutes.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Journaling and reflection. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to do a weekly review
  • Check in on business progress
  • Reflect on the week
  • Plan next weeks priorities

Example prompts

  • “s priorities, or says things like”
  • “how did this week go,”
  • “what should I focus on next week,”
  • “/weekly-review”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Scorecard (2 minutes)
  2. Wins (2 minutes)
  3. Losses & Lessons (3 minutes)
  4. Priority Check (3 minutes)
  5. Next Week's Focus (3 minutes)
  6. Energy Check (2 minutes)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Weekly Review loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 831 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 831 words, ~1,566 tokens.

Download SKILL.mdSave it as .claude/skills/weekly-review/SKILL.md (or your agent's skills folder).
name
weekly-review
description
When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should I focus on next week,' 'end of week check-in,' 'Sunday review,' 'weekly retro.' A structured CEO operating rhythm in 15 minutes.

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?"

Show full SKILL.md (328 more words)Show less
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:

markdown
# 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.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ceo/weekly-review of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Weekly Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Weekly Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weekly Review this skillTheCraigHewitt/skills159—~1.6kAutomated safety check: PassMIT
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
Munger Perspectivealchaincyf/munger-skill3791 repos~3.7kAutomated safety check: PassMIT
Daily Journalhuytieu/COG-second-brain1.3k—~1.3kAutomated safety check: PassMIT
Letterboxd Diaryjoe-bell/skills211—~4.2kAutomated safety check: PassMIT
Em Grid Scorermanager-dot-dev/manager-skills114—~5.8kAutomated safety check: PassMIT

Similar skills

  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed
  • Munger Perspective

    alchaincyf/munger-skill

    查理·芒格的思维框架与表达方式。基于《穷查理宝典》、伯克希尔/Daily Journal股东会、 USC/哈佛演讲、访谈记录、外部批评等50+来源的深度调研, 提炼5个核心心智模型、8条决策启发式和完整的表达DNA。

    379 GitHub starsUsed in 1 repo~3.7k tokens
    Knowledge ManagementAuto-check passed
  • Daily Journal

    huytieu/COG-second-brain

    A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.

    1.3k GitHub stars~1.3k tokensUpdated 8 days ago
    Knowledge ManagementAuto-check passed
  • Letterboxd Diary

    joe-bell/skills

    Fetch recently watched films from a Letterboxd member's diary RSS feed and render them as a compact markdown list, with first-run setup for the username.

    211 GitHub stars~4.2k tokensUpdated 3 days ago
    Knowledge ManagementAuto-check passed
  • Em Grid Scorer

    manager-dot-dev/manager-skills

    Score an Engineering Manager's coverage across all 12 cells of the EM Grid based on their calendar and Slack.

    114 GitHub stars~5.8k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed
  • Digital Brain

    foryourhealth111-pixel/Vibe-Skills

    This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content…

    3.6k GitHub stars~1.7k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    159 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Weekly Review

What does Weekly Review do?

When the user wants to do a weekly review, check in on business progress, reflect on the week, plan next week's priorities, or says things like 'weekly review,' 'how did this week go,' 'what should…. Weekly Review is an agent skill from TheCraigHewitt/skills.' A structured CEO operating rhythm in 15 minutes.

When should I use Weekly Review?

Weekly Review fits situations like: wants to do a weekly review; check in on business progress; reflect on the week; plan next weeks priorities.

How do I install Weekly Review in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill weekly-review -a claude-code`. Or copy the skill folder (ceo/weekly-review in TheCraigHewitt/skills) into .claude/skills/weekly-review in your project. Claude Code loads it when a task matches its description.

How do I install Weekly Review in Codex?

Run `npx skills add TheCraigHewitt/skills --skill weekly-review -a codex`. Or copy the skill folder (ceo/weekly-review in TheCraigHewitt/skills) into .agents/skills/weekly-review in your project. Codex loads it when a task matches its description.

Can I use Weekly Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill weekly-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weekly-review, .gemini/skills/weekly-review, .github/skills/weekly-review and .opencode/skills/weekly-review in your project.

What does Weekly Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Weekly Review is instructions for the agent only.

Does Weekly Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Weekly Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Weekly Review use?

Weekly Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Weekly Review use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Weekly Review?

Skills that share tags, products or a category with Weekly Review: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Munger Perspective (alchaincyf/munger-skill, 379 stars), Daily Journal (huytieu/COG-second-brain, 1.3k stars) and Letterboxd Diary (joe-bell/skills, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weekly Review?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.