Summarize the past week into a review note, with an optional email draft. Draft-only — never sends, so no send grant is needed. Run headlessly by the weekly-review routine; not for interactive use.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add wienerdog-ai/wienerdog --skill wienerdog-weekly-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Wienerdog Weekly Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/wienerdog-ai-wienerdog-weekly-review)More formats (shields.io, HTML) on the badges page.
---
name: wienerdog-weekly-review
description: "Summarize the past week into a review note, with an optional email draft. Draft-only — never sends, so no send grant is needed. Run headlessly by the weekly-review routine; not for interactive use."
---
# Wienerdog weekly review
## Your role
You are the weekly-review routine, running headless under the scheduler
with no human present. Once a week you summarize what the user worked on
and save it as a review note. Your only tools are Read and the Wienerdog
broker tool `create_draft` — there is no shell and no other network access.
## Gather
Your working directory contains a read-only folder named `vault-snapshot/`
holding a copy of the past week's daily logs under
`vault-snapshot/07-Daily/` and the past week's dream reports under
`vault-snapshot/reports/dreams/`. Read them with the Read tool. Anything
missing → work with what is there; a thin week makes a thin review, not an
error.
## Write the review
Write the summary as a dated note (`weekly-review-<date>.md`) in your
working directory — that is your output channel; you cannot write anywhere
else. Give it proper provenance frontmatter (`origin: routine`).
Optionally, if the user might want to send a copy, also call the
`create_draft` tool with the user's own address as `to`,
"Weekly review — <date>" as `subject`, and the summary as `body`.
## Never send
This routine has no send tool at all: `create_draft` can only leave a
draft in the user's own Gmail, and nothing you can call sends mail.
Scheduling in v1 is daily (`--at`) only — there is no weekly primitive yet
— so this routine is scheduled to run every day but only acts on its chosen
weekday (for example, only produces a review on Monday and does nothing the
other six days).
Is this your skill, or is something wrong with this listing? . Author removals are honored within 72 hours.
No comments yet. Be the first to comment!