Weekly Scorecard Claude Skill: Your Whole Week On One Page
AI Playbook Undeniable Speaking Trainings About Blog Subscribe Work With Me
CLAUDE SKILL · OPERATE

See Your Whole Week On One Page.

Every Sunday, compile the past 7 days from six bounded sources you already track into one honest one-page scorecard. Shipped, slipped, the signals that matter, and one correction for next week.

← All Claude Skills
01 / GET THE SKILL

Copy This. Give It To Your Claude.

Your week is scattered across six places: your ideas, your content, your search visibility, your builds, your pipeline, and your notes. This skill reads all six for the last 7 days and compresses them into one scorecard you can read in five minutes, so nothing important slips through. Copy the two blocks below and give them to your Claude.

Step 1. Copy the skill block below.

Step 2. Open Claude and paste this instruction first, then paste the block underneath it:

Paste into Claude first
Turn the block below into a Claude skill and install it. Create the skill file exactly as written. Then personalize it with smart defaults from what you know about me: my business, my voice, my current priorities, and where I keep my work. Confirm when it is installed and tell me how to run it.
The Skill · give this to Claude
---
name: weekly-intelligence-compile
description: Compile your whole week into one honest one-page Weekly Scorecard from six bounded sources you already track. Use this skill whenever you say "run the weekly compile," "compile the scorecard," "weekly scorecard," or "weekly intelligence compile." The output is one scorecard entry, filed wherever you keep your weekly review, that takes five minutes to read.
---

# Weekly Intelligence Compile

Read six bounded sources for the past 7 days, compress the week into one scorecard page, and file it where you already look. This skill compiles and writes. It never decides. You make the calls from a clean read.

## What This Does

Most weeks disappear. You shipped things, captured ideas, moved deals, and learned lessons, and by Sunday most of it has gone fuzzy. This skill pulls the whole week back into focus on one page. It reads each of your six tracked sources for the last 7 days, compresses what happened into a fixed scorecard, and hands it back so nothing important gets lost.

## Trigger Phrases

- "run the weekly compile"
- "compile the scorecard"
- "weekly scorecard"
- "weekly intelligence compile"

## The Six Bounded Sources (read-only, last 7 days)

Read six bounded sources, a defined list each, never a firehose. A bounded source is the specific place you track one kind of work, read for only the past 7 days. Pull the last week from each. Where you track each one is yours to name once, and after that I remember it.

1. **Signals and ideas captured.** From wherever you collect raw ideas, notes to self, and things worth acting on later. What came in this week, and anything that grew into a real next step.
2. **Content shipped.** From wherever you track what you publish. What actually went live this week per surface. Performance numbers join later, the scorecard does not wait for them.
3. **SEO and AEO movement.** From wherever you track search and answer-engine visibility. What moved this week and what got published toward it.
4. **Builds and projects touched.** From wherever you track your builds. What you touched this week, what changed status, and what shipped.
5. **Pipeline and sales activity.** From wherever you track deals and conversations. Active conversations, new opportunities, and anything that moved forward or stalled.
6. **Notes and lessons logged.** From wherever you write down what you learned. The lessons and reflections captured this week.

If you have not told me where you keep one of these, ask me once and remember it for every future run.

## Output (locked template)

One page, titled **"Weekly Scorecard: Week of [Monday's date]"**, filed wherever you keep your weekly review so you read it in the same place every week. A scorecard that takes longer than five minutes to read stops getting read, so keep it to one page.

Sections, in this exact order:

1. **The Week's Numbers.** Shipped count, signals captured, conversations active, revenue month-to-date if visible. The week at a glance.
2. **Shipped.** What actually went live or got completed this week. Real, done, out the door.
3. **Slipped.** What was supposed to move and did not. Honest reads beat fast reads. This section earns its place by being truthful.
4. **Signals That Matter.** The 2 to 4 signals from this week worth acting on. The few that rise above the noise.
5. **One Correction for Next Week.** Exactly one. The skill proposes it, you decide. One clear adjustment beats a list you will never touch.

## Voice Rules

Write in your own voice: direct, grounded, no hedging. Apply your own brand voice guidelines if you have them. Keep sentences short and clear, and skip words that feel inflated or salesy.

## Failure Protocol

A blocked run writes a loud blocker report in place of a partial scorecard. If any source is unreachable or erroring, do not quietly skip it and ship a scorecard that looks complete. Write to the same destination with the title **"Weekly Scorecard: BLOCKED [date]"**, name each failed source, the error, and the timestamp. Retry once with backoff, then stop. A run that silently drops a source counts as not done. Loud beats silent every time.

## Quality Standards

- **Six sources, bounded, every time.** Read all six for the last 7 days. A skipped source is a hole in the week.
- **One page, five-minute read.** Compress hard. The scorecard exists to be read, so keep it short enough that you actually read it.
- **Compile, do not decide.** Report what happened and propose one correction. The decisions stay with you.
- **Honest Slipped section.** The value of the scorecard lives in the truth about what did not move. Always keep it truthful.
- **File it where you already look.** The scorecard only works if it lands in your weekly review spot, in the same place every week.

Installed In Under A Minute

Claude reads the block, builds the skill file, and installs it. From then on, you just run the skill in any conversation. No folders to find, no code to write.

Undeniable Studio

Build Your Personalized AI First Business Together

Every week you see what's working, build it live, and put it to work in your business.

Join The Studio →
02 / WHAT COMES BACK

Run It. Get The Result.

Here's the shape of what this skill hands you when it runs. Copy it, use it, keep moving.

Example Output
Source
One founder's week across six tracked sources
The Week's Numbers
4 shipped · 11 signals captured · 6 conversations active · revenue month-to-date on pace
Shipped
New pricing page live, three blog posts published, onboarding sequence finished
Slipped
The case-study video stalled at edit and the partner outreach never went out
Signals That Matter
Two prospects asked the same question about setup time → worth its own page
One Correction
Block two hours Monday to finish the case-study video before starting anything new
Read Time
Under five minutes, filed in your weekly review spot
Keep Stacking WEEKLY SCORECARD pairs well with THE AGENT ARCHITECT SKILL
03 / WHY IT WORKS

The Simple Idea Underneath It

You don't need to hold any of this in your head. That's the skill's job. If you're curious what it's doing for you, here's the idea underneath it.

The Simple Idea

A week feels productive in the moment and vague by Sunday. The work was real. It just got scattered across six different places and never came back together. The Weekly Scorecard pulls it all onto one page: what shipped, what slipped, the signals worth acting on, and one correction for next week. You get your week back in five minutes.

1

Six Bounded Sources

Your week lives in six places. The skill reads each one for the last 7 days, a defined list from each, so the whole week shows up on one page and never a firehose.

2

Compile, Do Not Decide

The skill reports what happened and proposes one correction. Every real decision stays with you, made from a clean read of the week.

3

Shipped And Slipped

Two sections side by side: what went live and what stalled. The honest read of what slipped is where the value lives.

4

The Five-Minute Rule

One page, compressed hard. A scorecard you can read in five minutes is a scorecard you actually read every week.

5

Loud When Blocked

If a source is unreachable, the skill writes a loud blocker report that names the source and the error. A blocked run stays visible, so a broken week never hides as a clean one.

QUESTIONS

What People Ask About WEEKLY SCORECARD.

It is one page that compiles your whole week from six bounded sources you already track. It has five fixed sections: The Week's Numbers, Shipped, Slipped, Signals That Matter, and One Correction for Next Week. It reads in under five minutes and it lands in the same place every week so you actually read it.

They are the six places you already track your work, read for only the past 7 days: signals and ideas captured, content shipped, SEO and AEO movement, builds and projects touched, pipeline and sales activity, and notes or lessons logged. Bounded means a defined list from each, never a firehose. You name where each one lives once and the skill remembers it.

Shipped is what actually went live or got completed this week. Slipped is what was supposed to move and did not. The Slipped section is where the honesty lives, and the skill keeps it truthful. Seeing both together gives you the real read on your week.