Agent skill

Pm Weekly Review

by mohitagw15856 in mohitagw15856/pm-claude-skills

Structure a PM's weekly review and planning session. An agent skill from mohitagw15856/pm-claude-skills.

MITAuto-check passedKnowledge Management

Install Pm Weekly Review

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

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

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills pm-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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pm-weekly-review .claude/skills/pm-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
pm-weekly-review
GitHub stars
1.4k
Token cost
~1.2k tokens
SKILL.md length
600 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Structure a PM's weekly review and planning session. An agent skill from mohitagw15856/pm-claude-skills.

  • Doing a weekly PM review
  • SKILL.md covers The Weekly Review Structure…, Output Format, Required Inputs and Quality Checks, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Writing a weekly update

What it does

Pm Weekly Review is an agent skill from mohitagw15856/pm-claude-skills. Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 priorities.

Its SKILL.md is about 1.2k 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 and Internal communications. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Doing a weekly PM review
  • Writing a weekly update
  • Preparing for Monday planning
  • Reviewing sprint health

Example prompts

  • “/pm-weekly-review”

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. 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.

    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

Pm Weekly Review loads about 1.2k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 600 words of instructions outside code blocks.

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

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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 600 words, ~1,208 tokens.

Download SKILL.mdSave it as .claude/skills/pm-weekly-review/SKILL.md (or your agent's skills folder).
name
pm-weekly-review
description
Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 priorities.

PM Weekly Review Skill

Turn the chaotic end-of-week brain dump into a structured 20-minute ritual that keeps you, your team, and your stakeholders aligned — without a meeting.

Not quite this? Use weekly-review-ritual when you want a personal GTD-style weekly review rather than a product review.

The Weekly Review Structure (20 minutes)

5 min — Metrics check: What moved? What didn't? What's surprising? 5 min — Ship progress: What shipped? What slipped? What's blocked? 5 min — Insights: Any customer feedback, support tickets, or research findings? 5 min — Next week priorities: What are the 3 things that matter most?


Output Format

PM Weekly Review — Week of [Date]

Product Area: [What you own] Written by: [PM Name] Time to read: ~3 minutes


📊 Metrics This Week
MetricThis WeekLast WeekTargetTrend
[Primary metric][Value][Value][Target]↑ / ↓ / →
[Secondary metric][Value][Value][Target]↑ / ↓ / →
[Health metric][Value][Value][Target]↑ / ↓ / →

Notable movement:

  • [What changed and why — 1 sentence each]

Concern to watch:

  • [Anything trending in the wrong direction]

🚢 This Week's Progress

Shipped:

  • ✅ [What went live] — [1-line impact or observation]

In Progress:

  • 🔄 [Feature/initiative] — [% complete or current status]

Slipped / Blocked:

  • ⚠️ [What didn't happen] — Reason: [brief] — Action: [who's unblocking it]

Carry-forward to next week:

  • [Item + why it's carrying over]

💡 Insights & Signals

Customer feedback:

  • "[Quote or paraphrase]" — Source: [user/channel] — Theme: [tag]

Support signals:

  • [Top ticket category this week + volume]
  • [Anything that signals a product gap]

Research / data:

  • [Any discovery from user interviews, analytics, or experiments]

🎯 Next Week — Top 3 Priorities
#PriorityWhy This WeekOwnerDone =
1[Most important thing][Reason it can't wait][Name][Clear definition of done]
2[Second priority][Why][Name][Done criteria]
3[Third priority][Why][Name][Done criteria]

Decisions needed:

  • [Any decision that's blocking progress — who needs to make it]

Asks / dependencies:

  • [What you need from engineering / design / data / leadership]

🧠 Reflection (Optional but powerful)

What's one thing from this week I'd do differently? [Your honest answer — 1–2 sentences]

What's the biggest unknown I'm carrying into next week? [Name the uncertainty explicitly]


Required Inputs

Ask the user for these if not provided:

  • Product area or team you own
  • Key metrics this week (with values and prior week comparison)
  • What shipped, slipped, or is blocked
  • Top 3 priorities for next week
  • Any customer insights or signals (optional)
Show full SKILL.md (232 more words)Show less

Quality Checks

  • Metrics include period-over-period comparison (not just raw numbers)
  • Every blocked item has an owner and a specific unblocking action
  • Next week's priorities have a "why this week" rationale
  • Total length is under 400 words (skimmable in 3 minutes)
  • Reflection section is honest, not aspirational

Anti-Patterns

  • Do not report metrics without comparing to target or the prior week — absolute numbers without context are not useful
  • Do not list blockers without a named owner and proposed resolution — unowned blockers stay blocked
  • Do not write a weekly review that is longer than one page — it must be scannable in under 2 minutes
  • Do not include more than 3 priorities for next week — a list of 8 "top priorities" means nothing is prioritised
  • Do not skip the insights section — observations that inform future decisions are a PM's key value add

Guidelines

  • Keep the whole document under 400 words — if stakeholders won't read it, it doesn't exist
  • The reflection section is for you, not your stakeholders — keep it honest
  • Always name a clear owner for every blocked item — "the team will figure it out" is a blocker in disguise
  • Recommend sending this by end of Friday — Monday morning is too late to course-correct
  • If three weeks of weekly reviews show the same blocked item, escalate immediately

Example Trigger Phrases

  • "Doing a weekly PM review."
  • "Write a weekly update."
  • "Prepare for Monday planning."
  • "Review sprint health."

© mohitagw15856, 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 skills/pm-weekly-review of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Pm 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.

Pm Weekly Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pm Weekly Review this skillmohitagw15856/pm-claude-skills1.4k—~1.2kAutomated 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 9 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 4 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 mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Pm Weekly Review

What does Pm Weekly Review do?

Structure a PM's weekly review and planning session. An agent skill from mohitagw15856/pm-claude-skills. Pm Weekly Review is an agent skill from mohitagw15856/pm-claude-skills. Structure a PM's weekly review and planning session.

When should I use Pm Weekly Review?

Pm Weekly Review fits situations like: doing a weekly PM review; writing a weekly update; preparing for Monday planning; reviewing sprint health.

How do I install Pm Weekly Review in Claude Code?

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

How do I install Pm Weekly Review in Codex?

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

Can I use Pm 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 mohitagw15856/pm-claude-skills --skill pm-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/pm-weekly-review, .gemini/skills/pm-weekly-review, .github/skills/pm-weekly-review and .opencode/skills/pm-weekly-review in your project.

What does Pm Weekly Review need to run?

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

Does Pm 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 Pm 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 Pm Weekly Review use?

Pm 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 Pm Weekly Review use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Pm Weekly Review?

Skills that share tags, products or a category with Pm 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 Pm Weekly Review?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

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