Bundle · 3 skills

Weekly Review

Close the week and plan the next: Friday's reading roundup, then on Sunday a plan for your week and a recap of your training.

What's in it

every Friday at 5:00 PM
Reading Digest
This week's papers worth reading, each explained in three lines.
every Sunday at 6:00 PM
Weekly Planner
A week plan that fits the hours you actually have.
every Sunday at 7:00 PM
Weekly Fitness Summary
Your training week in one page, with one clear focus for next.

Safety

Reading Digest · Read-only · Light cost
Weekly Planner · Read-only · Light cost
Weekly Fitness Summary · Read-only · Light cost

Full safety notes

Writes or sends

Reading Digest: Read-only.
Weekly Planner: Read-only unless you approve calendar holds.
Weekly Fitness Summary: Read-only. Never posts to Strava or social accounts.

What it reads

Public papers and articles (search and page reads)
Your saved read-later items (if connected)
Next week's calendar events
Open tasks and due dates (if a task app is connected)
Calendar write access, only for holds you approve
Workouts, distance, pace, heart rate, sleep and recovery data from your chosen source

Cost · light

Reading Digest: Low: ~4 runs a month.
Weekly Planner: Low: ~4 runs a month.
Weekly Fitness Summary: Low: ~4 runs a month.

Before you install

Summaries can miss nuance; open the paper before citing it.
It only creates calendar holds after you say yes to each plan.
Your assistant needs calendar write permission for holds; read-only works for planning alone.
Health data is sensitive: connect only what you want summarized.
Not medical advice. It suggests a training focus, not a diagnosis.
It never posts to Strava or social accounts.

Install the whole bundle

One prompt sets up all 3 skills and their routines. Your agent asks the setup questions once.

Paste the prompt into a one-to-one chat with your Grok Bot (it already contains all 3 SKILL.md files).
Answer the one round of setup questions, and connect any apps it asks for from the connect card.
Check the routines in the Bot's info pane under Routines; pause or edit any of them there.

See the full prompt

Install the BotPlaza bundle "Weekly Review" (3 skills). For each skill below, save it as a skill with its exact name. Then create one routine per scheduled skill that runs it on the schedule listed and posts the result here; skills marked on demand get no routine. Before the first run, read the setup questions in all 3 skills, merge the ones they share (such as my name, city, time zone and where to deliver), ask me everything in one short message, and remember my answers for every skill in this bundle. When you're done, list the skills and routines you created. Never send, post, submit, or buy anything on my behalf without asking me first.

1. Reading Digest: routine every Friday at 5:00 PM
2. Weekly Planner: routine every Sunday at 6:00 PM
3. Weekly Fitness Summary: routine every Sunday at 7:00 PM

=== Skill 1 of 3: Reading Digest ===

---
name: reading-digest
description: Use when the user asks for a reading digest, paper digest, "what's new in {field}", a weekly roundup of research papers, newsletters, or saved articles, or when a scheduled reading routine runs. Finds new papers and long-form pieces on the user's topics, picks the few worth their time, and explains each in plain language with links.
metadata:
  id: reading-digest
  version: "1.0.0"
  author: BotPlaza
---

# Reading Digest

> This week's papers worth reading, each explained in three lines.

## What it does

The handful of papers and essays from this week worth your time, each explained in three plain sentences, so you can decide what to actually read.

## When to use

- "What's new in {field} this week", "summarize this week's papers on {topic}", "go through my saved articles".
- A weekly routine (default: Friday 5:00 PM).

## Requires

Web search and web access (arXiv, journals, preprint servers). Optional: a read-later app (Readwise, Instapaper, Notion) to save picks.

## Schedule

Default: Weekly, Friday 5:00 PM. Run it from a routine or scheduled task at that time; the user can change the time in the routine, not in this skill.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `topics` | ask | E.g. "LLM agents", "CRISPR delivery", "urban planning". Up to 5. |
| `sources` | preprints, journals, quality long-form | Toggle: arXiv, bioRxiv/medRxiv, SSRN, journals, newsletters, the user's read-later list, specific blogs. |
| `window` | last 7 days | |
| `count` | 5 | Items in the digest. |
| `level` | informed non-specialist | Or `expert` (keep jargon, add methods detail) or `beginner`. |
| `include_skipped` | yes | A short "also out this week" list. |

## Steps

1. **Search** each topic across the enabled sources for items published in the window. Collect title, authors, venue, date, and link.
2. **Screen** by relevance to the topic, novelty (new result vs incremental), credibility (venue, methods, data), and attention from credible experts. Note when something is a preprint and not peer reviewed.
3. **Read** the abstract, introduction, figures, and conclusion of each pick at minimum. For articles, read the whole piece.
4. **Explain** each pick in three sentences: what they did, what they found, why it matters (or why to be skeptical).
5. **Add one honest caveat** per item (small sample, preprint, single lab, industry-funded, benchmark only).
6. **Write** in the format below, ordered by how much the user should care.

## Output format

```markdown
# Reading digest · {topics} · week of {date}
*{N} items reviewed, {count} picked*

## 1. {Title}
{Authors (first author et al.)} · {Venue or "Preprint"} · {date} · ~{X} min read
**What:** {one sentence} **Found:** {one sentence} **Why it matters:** {one sentence}
*Caveat: {one line}*
[Read]({url})

## Also out this week
- [{Title}]({url}), {one line}
```

## Edge cases

- **Nothing notable:** say so and list the 2 or 3 closest items instead of padding.
- **Paywalled:** use the abstract and say so; link a free version if the authors posted one.
- **Retractions or major corrections** to anything in past digests: lead with them.

## Boundaries

Summarize and link; don't reproduce full text. Never state a finding more strongly than the authors do.

=== Skill 2 of 3: Weekly Planner ===

---
name: weekly-planner
description: Use when the user asks to plan their week, "what does my week look like", for a Sunday or Monday planning session, or when a weekly planning routine runs. Combines calendar, open tasks, and stated priorities into a realistic week plan with top 3 outcomes, protected focus blocks, a day-by-day view, and overload warnings.
metadata:
  id: weekly-planner
  version: "1.0.0"
  author: BotPlaza
---

# Weekly Planner

> A week plan that fits the hours you actually have.

## What it does

Start the week with a plan that fits the time you actually have: three outcomes that matter, focus time protected, and early warning when the week is overbooked.

## When to use

- "Plan my week", "how busy am I this week", "help me prioritize", Sunday evening or Monday morning planning.
- A weekly routine (default: Sunday 6:00 PM).

## Requires

A calendar connector. A task source (Notion, Todoist, Linear, a doc, or a list in chat) is optional. Without one, ask the user for this week's to-dos.

## Schedule

Default: Weekly, Sunday 6:00 PM. Run it from a routine or scheduled task at that time; the user can change the time in the routine, not in this skill.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `week_start` | Monday | |
| `work_hours` | 9:00–17:00, Mon–Fri | Used to calculate free time. |
| `focus_block` | 2 hours | Minimum length of a protected deep-work block. |
| `priorities` | ask | 1 to 3 goals for the week or quarter. Saved between weeks. |
| `include_personal` | yes | Workouts, family, errands. |
| `create_blocks` | off | If on, propose calendar holds and create them only after approval. |

## Steps

1. **Read the week:** every event Monday to Sunday with start, end, and attendees. Total meeting hours per day.
2. **Find free time:** gaps inside `work_hours` that are at least `focus_block` long.
3. **Collect tasks:** open tasks due this week or overdue, plus anything the user lists. Estimate effort when missing (S = under 1 h, M = 1–3 h, L = half day or more) and mark estimates as estimates.
4. **Pick the top 3 outcomes:** results, not activities ("Send the Q4 budget to finance", not "Work on budget"), tied to stated priorities and hard deadlines.
5. **Fit the work:** assign each top outcome to a specific free block. If the work doesn't fit, say so and suggest what to drop, delegate, or move.
6. **Flag problems:** days over 5 hours of meetings, back-to-backs over 3 hours, deadlines with no time before them, conflicts, and evenings or weekends being eaten.
7. **Write the plan** in the format below.
8. **Offer calendar holds** for the focus blocks. Create them only after the user approves.

## Output format

```markdown
# Week of {Mon D} – {Sun D}
**{X} h of meetings · {Y} h of open focus time · {Z} tasks due**

## This week's top 3
1. **{Outcome}**, scheduled {day, time}. Why: {priority or deadline}

## Day by day
| Day | Meetings | Focus block | Main task |
|---|---|---|---|

## Heads up
- {Overload, conflict, or deadline risk, with a suggested fix}

## Can wait
- {Tasks deliberately pushed to next week}
```

## Edge cases

- **Wall-to-wall week:** say plainly that the top 3 won't fit and propose which meetings to decline or shorten. Never decline on the user's behalf.
- **Holiday or travel:** remove those days from capacity and say so.
- **No priorities given:** infer from deadlines and recurring themes, label them "inferred", and ask the user to confirm.

## Boundaries

- Read-only unless the user approves calendar holds. Never accept, decline, or move meetings on the user's behalf.
- Never message attendees or share the plan without the user's approval.

=== Skill 3 of 3: Weekly Fitness Summary ===

---
name: weekly-fitness-summary
description: Use when the user asks how their training went this week, for a fitness or workout recap, progress toward a running, cycling, or step goal, or when a weekly fitness routine runs. Summarizes activities, volume, intensity, sleep and recovery, compares against last week and the 4-week average, and suggests next week's focus. Not medical advice.
metadata:
  id: weekly-fitness-summary
  version: "1.0.0"
  author: BotPlaza
---

# Weekly Fitness Summary

> Your training week in one page, with one clear focus for next.

## What it does

See your week of training at a glance: what you did, how it compares, whether you're recovering, and one clear focus for next week.

## When to use

- "How was my training this week", "weekly workout summary", "am I on track for my half marathon".
- A weekly routine (default: Sunday 7:00 PM).

## Requires

At least one activity data source: Strava, Garmin Connect, Apple Health export, Google Fit, Oura, Whoop, or a CSV the user shares. If none is connected, ask the user to paste or upload this week's activities.

## Schedule

Default: Weekly, Sunday 7:00 PM. Run it from a routine or scheduled task at that time; the user can change the time in the routine, not in this skill.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `goal` | none | E.g. "sub-2:00 half marathon on Apr 12", "4 workouts a week", "10k steps a day". |
| `sports` | all logged | Toggle: run, ride, swim, strength, walk, yoga, other. |
| `units` | metric | Or imperial. |
| `metrics` | volume, time, intensity, sleep | Toggle: HR zones, pace or power, elevation, resting HR, HRV, steps. |
| `coach_tone` | encouraging | `encouraging`, `neutral`, or `blunt`. |

## Steps

1. **Collect** all activities from Monday to Sunday (user's timezone): type, date, duration, distance, elevation, average HR or pace or power, and perceived effort if logged.
2. **Collect recovery data** if available: nightly sleep, resting HR, HRV.
3. **Compute:** totals by sport, total training time, number of sessions, longest session, and time in each intensity zone if HR data exists.
4. **Compare** with last week and the 4-week average. Flag a week-over-week jump in volume above 10% to 15% as a load spike.
5. **Check against the goal:** on track, ahead, or behind, with the number that decides it.
6. **Suggest one focus** for next week, based on the data (e.g. "Hold volume steady; your load jumped 28%").
7. **Write** in the format below. Celebrate real wins with numbers, not empty praise.

## Output format

```markdown
# Your training week · {Mon D} – {Sun D}
**{N} sessions · {H} h {M} min · {distance}**

| | This week | Last week | 4-wk avg |
|---|---|---|---|

## Highlights
- {Best effort or milestone, with the number}

## Recovery
{Sleep average, resting HR trend, HRV trend, one line on what it suggests}

## Goal check
{Goal}: **{on track / ahead / behind}**. {The deciding number.}

## Next week's focus
{One sentence, one reason.}
```

## Edge cases

- **Missing or duplicate activities** (watch and phone both logged): de-duplicate by start time and duration, and say so.
- **Rest or sick week:** report it plainly, without guilt, and suggest an easy return.
- **Pain, injury, chest pain, or dizziness mentioned:** don't coach through it. Recommend seeing a medical professional.

## Boundaries

This is a training summary, not medical advice. Don't post to Strava or social accounts without approval.