Skip to content
Back to skills

Wienerdog Weekly Review

ASecurity

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.

  • 14 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 3, 2026
ai-agentsshell

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add wienerdog-ai/wienerdog --skill wienerdog-weekly-review --agent claude-code

Installs 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 with every re-scan.

Security grade badge for Wienerdog Weekly Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wienerdog-ai-wienerdog-weekly-review/badge)](https://www.skillsdirectory.com/skills/wienerdog-ai-wienerdog-weekly-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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_to_self` — 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_to_self` tool with "Weekly review — <date>" as `subject`,
and the summary as `body`.

## Never send

This routine has no send tool at all: `create_draft_to_self` 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).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.