メニュー
A Friday review of the week — wins, open loops, stale tasks, and setup for next week. Activate when the user says "/assistant:report", "weekly review", "weekly report", "wrap up my week", or on a Friday-afternoon schedule.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Onboarding for the assistant plugin. Activate when the user says "/assistant:setup", "set me up", "configure my assistant", "help me get started", or when no profile exists per rules/paths.md. Writes profile, policies, memory (AGENTS.md hot cache + memory/ tree), and install config.
Propose meeting times, check conflicts, protect calendar time with buffer/prep/follow-up/habit blocks, and draft invites and scheduling replies. Activate when the user asks to schedule something, find a time, check for conflicts, protect their calendar, or draft an invite. Proposes and drafts only — never books, moves, or declines without approval.
A short, scannable morning briefing — today's calendar, priority unread, follow-ups going cold, and what needs attention. Activate when the user says "/assistant:brief", "morning briefing", "what's my day look like", or on a morning schedule.
Produce a pre-meeting brief — who's in the room, what they do, last contact, and what to prepare. Activate when the user says "/assistant:meeting prep", "prep me for my next meeting", "who am I meeting", or on a meeting-prep schedule.
Draft email, chat, and letter replies in the user's own voice. Activate when triaging needs-reply mail, when the user says "/assistant:draft email|chat|letter", "/assistant:email draft", "draft a reply", or pastes a message they need to answer. Creates drafts only — never sends.
Capture feedback on email reply drafts and propose profile voice updates. Activate when the user says "/assistant:email feedback", rates a draft as good, light edit, or heavy rewrite, or pastes what they actually sent after editing a draft. Proposes profile diffs for approval — never writes profile.md directly.
| name | weekly-review |
| description | A Friday review of the week — wins, open loops, stale tasks, and setup for next week. Activate when the user says "/assistant:report", "weekly review", "weekly report", "wrap up my week", or on a Friday-afternoon schedule. |
Close the week cleanly: what got done, what's still open, what's gone stale, and what to line up for Monday. Also the moment to prune tasks and memory. Catalog entry: job_id: weekly-review in scheduled/schedules.yaml.
Load goals/priorities (to judge what mattered), voice, and working hours.
On an interactive Friday run after the expected window (cron 16:00 Friday + 90 minutes = 17:30), optionally surface a low-priority miss hint for weekly-review when:
scheduled/weekly-review.yaml exists and surface is localreview-{today}.md is absent and last_run_at is staleUse the same ### Schedule health block format as daily-brief, naming the weekly review job. Suggest cloud-code (no managed cookbook for this job). Skip when surface is managed or cloud-code. Max one health block per chat turn; do not block the review.
TASKS.md Done, and from the week's briefs/follow-ups if present.follow-up-tracking items still outstanding, most-important first.meeting-prep), deadlines from goals, top 3 priorities.Weekly review — week ending Fri 11 Jul
Wins (6 closed)
• Shipped Q3 scope with Acme • Expense report in • ...
Open loops (4)
• Q3 SOW draft — due next week
• Acme contract — nudged twice, still silent (escalate?)
Stale — triage these
• "Fix back fence" — untouched 21 days → cancel or keep in To do?
• "Call accountant" — no context, 16 days → still needed?
Next week
• Mon 9:00 board prep (deck ready?) • Renewal deadline Thu
• Top 3: SOW, board deck, hiring loop
Runs well as a Friday 4pm scheduled task; save to review-YYYY-MM-DD.md. See skills/schedule-setup/SKILL.md.
Heartbeat: at end of a scheduled run, update the ledger via bash (required):
python3 scripts/update_ledger.py \
--job-id weekly-review \
--status {success|partial|failed} \
--artifact review-{today}.md \
--working-folder {working-folder}
Before ending, confirm last_run_at in scheduled/weekly-review.yaml matches this run.
TASKS.md and memory/ only with confirmation (writes to those are allowed, but a review is a good moment to confirm).Follow rules/approval-frame.md when surfacing recommendations that need user decisions.
Use all four sections for actionable recommendations. Do not write queue items for read-only review sections (closed items, stale task lists) unless a separate pending approval artefact exists — e.g. a nudge draft or profile diff proposal.