cc-skill:weekly-review-memo

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill generates a standardized weekly review memo for any project, product, or area of your life. It captures three wins, three losses, three recommendations, plus one thing to kill and one thing to double down on. Same format every week builds pattern recognition over time.

who it is for

Anyone running a project, product, or job search who wants a repeatable weekly check-in format that surfaces what's working and what's not.

when it fires

When you say things like 'weekly review', 'weekly memo', 'this week recap', 'Sunday review', or 'week recap'.

say something like

"Generate my weekly review memo for ConsultantVoice marketing for the week of April 14-20"
"I need a product retrospective. Here are this week's ArbiCall metrics."
"Sunday review for my job search this week"

what you might get back

ConsultantVoice Weekly Review — Week of April 14-20. TL;DR: Cold email reply rate broke 4%, but LinkedIn engagement stayed flat. Wins: Email reply rate hit 4.1% (up from 2.6%) with new gatekeeping opener. Losses: LinkedIn post got 23 likes but zero qualified replies. Recommendations: Test the email opener on three more segments by Wednesday. Kill: Stop posting LinkedIn on Fridays after 3pm. Double down: The certification angle is working in email.

how to know it worked

You will see a structured memo with wins and losses tied to specific numbers, a clear hypothesis for why losses happened, and a single-sentence focus for next week.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/weekly-review-memo/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when generating weekly review memos for any of Jay's products, projects, or job-search workflow. Triggers on "weekly review", "weekly memo", "this week recap", "Sunday review", "week recap", or "review last week". Mirrors the Marketing

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/weekly-review-memo/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when generating weekly review memos for any of Jay's products, projects, or job-search workflow. Triggers on \"weekly review\", \"weekly memo\", \"this week recap\", \"Sunday review\", \"week recap\", or \"review last week\". Mirrors the Marketing OS weekly review format (3 wins, 3 losses, 3 recommendations, 1 to kill, 1 to double down on) — usable for marketing, product, sales, or personal productivity."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/weekly-review-memo/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.