Menu
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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Connect Wienerdog to your Google account (Gmail, Calendar, Drive). Walks you through creating a personal Google sign-in key, then verifies it. Use when the user wants to connect Google / Gmail / Calendar / Drive.
Compose and email the user's morning digest (today's calendar, overnight inbox summary, latest memory report). Run headlessly by the daily-digest routine; not for interactive use.
Each morning, triage recent inbox mail and leave draft replies where useful. Draft-only — never sends, so no send grant is needed. Run headlessly by the inbox-triage routine; not for interactive use.
Consolidate recent sessions into vault memory. Run headlessly by the nightly dream job; not for interactive use.
Set up Wienerdog: interview the user and build their identity notes. Use when the user asks to set up or reconfigure Wienerdog.
Browse and set up ready-made daily/weekly routines (morning digest, inbox triage, weekly review). Use when the user wants to set up an automatic routine, a scheduled job, or asks 'what can Wienerdog do for me?'.
| 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. |
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.
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 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 — " as subject, and the summary as body.
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).
