💫 This skill is free — copy it, give it to your Claude, and it installs itself in under a minute.
Free AI Skill · Operate

See Your Whole Week on One Honest Page

Weekly Scorecard reads the six places you already track your work — ideas, content, SEO, builds, pipeline, and lessons — for the past 7 days, and compresses it all into one page that takes five minutes to read. It compiles; you make the calls.

← Back to the Skills Library
01 — GET THE SKILL

Installed in under a minute. No tech skills required.

You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.

1

Paste the instruction

Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.

2

Paste the skill underneath, then send

Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.

Step 1 · paste this into Claude first
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
Step 2 · the full Weekly Scorecard skill
---
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.
That's it. You're installed.

From then on, once a week, just say "Run the weekly compile."

Want to go further than skills?

Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.

Explore Signature Coaching
02 — WHAT COMES BACK

One page. Five sections. Same order, every week.

The scorecard is a locked template titled “Weekly Scorecard: Week of [Monday's date],” filed wherever you keep your weekly review. Here's exactly what's on it:

1 · The Week's Numbers

The week at a glance: shipped count, signals captured, conversations active, and revenue month-to-date when it's visible.

2 · Shipped

What actually went live or got completed this week. Real, done, out the door.

3 · Slipped

What was supposed to move and didn't. This section earns its place by being truthful — honest reads beat fast reads.

4 · Signals That Matter

The 2–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 of ten you'll never touch.

And if a source is unreachable?

It never quietly skips one and hands you a scorecard that looks complete. A blocked run writes a loud blocker report instead — titled “Weekly Scorecard: BLOCKED,” naming each failed source, the error, and the timestamp. It retries once, then stops. A run that silently drops a source counts as not done.

Keep stacking: pairs beautifully with The Scribe

Weekly Scorecard looks back — one honest page on the week that just ended. The Scribe looks at right now — a living dashboard matched to your source of truth every night.

Get The Scribe →
03 — WHY IT WORKS

Because most weeks just disappear.

You shipped things, captured ideas, moved deals, and learned lessons — and by Sunday most of it has gone fuzzy. The scorecard pulls the whole week back into focus before it's gone.

1

Bounded sources beat firehoses

Each of the six sources is a defined place, read for only the past 7 days — never your whole workspace, never an open-ended dig. You tell it once where you track each one, and it remembers for every future run.

2

The template is locked

Five sections, same order, every single week. You stop re-deciding what a review looks like and start comparing week to week — which is where the patterns show up.

3

Slipped is where the value lives

Anyone can list wins. The scorecard keeps a standing, honest section for what was supposed to move and didn't — because that's the part you actually need to see.

4

One correction, not ten

The week ends with exactly one proposed adjustment. A single clear change beats a self-improvement list you'll never touch — and it stays a proposal, because this skill compiles and never decides.

5

It lands where you already look

The scorecard files into your weekly review spot, the same place every week, short enough to read in five minutes. A scorecard that takes longer than that stops getting read.

04 — FAQ

Questions people actually ask

What is the Weekly Scorecard skill?
Weekly Scorecard is a free Claude AI skill that reads six bounded sources you already track — ideas captured, content shipped, SEO movement, builds touched, pipeline activity, and lessons logged — for the past 7 days, then compresses the week into one fixed scorecard page filed where you keep your weekly review. It compiles and writes; it never decides. You make the calls from a clean read.
When would I actually run it?
Once a week, whenever you sit down for your weekly review — just say “run the weekly compile.” The first time, it asks once where you keep each of the six sources, then remembers for every run after. From then on it's a five-minute read on a week that would otherwise go fuzzy.
What comes back each week?
One page titled “Weekly Scorecard: Week of [Monday's date]” with five sections in a locked order: the week's numbers, what shipped, what slipped, the 2–4 signals worth acting on, and exactly one proposed correction for next week. And if any source is unreachable, you get a loud blocker report naming what failed — never a scorecard that quietly looks complete.