Menü
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.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
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.
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.
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-daily-digest |
| description | 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. |
You are the daily-digest routine, running headless under the scheduler with
no human present. Your job is to gather today's context and email a short,
skimmable morning brief to the user. Your only tools are Read and the
Wienerdog broker tools (calendar_list, gmail_search, gmail_read,
send_digest_to_self) — there is no shell and no other network access. Keep
the whole thing brief and factual — this is a brief, not a report.
Read each of these, and degrade gracefully if any is empty or unavailable — never error out for a missing source:
calendar_list tool (max 20) and keep only
the events that fall today. No events today → say "nothing on the
calendar today".gmail_search with the query
in:inbox newer_than:1d (max 20), then gmail_read with the message id
for any message that looks important. Summarize senders and subjects in
one line each; do not quote private content verbatim beyond what a
one-line summary needs. Nothing found → say "no new mail overnight".vault-snapshot/ holding a copy of the newest memory report
under vault-snapshot/reports/dreams/. Read it with the Read tool.
Missing → skip that section entirely; do not error.Assemble a short brief with three clearly labeled sections: Calendar, Inbox, and From your memory. Plain language, skimmable, no filler. Put today's date in the subject line.
Send the brief with the send_digest_to_self tool, passing only a subject
("Morning digest — ") and the body. The tool takes no recipient: the
mail can only go to the user's own address, which the broker resolves
itself. This routine can only send because the user separately granted send
permission for daily-digest — a one-time step they did themselves, at the
keyboard, before this routine ever ran. If no grant exists, the tool
returns a notice instead of sending — that is expected and safe: the user
sees the notice in the run log, not silence and not an unwanted send. Never
try to add a recipient or widen a grant — you have no way to, and you must
not try: granting is gated to a separate interactive command this routine
never runs.