/weekly-brief
Brief me on my week, my day, or what to focus on. Use for "brief me", "what's on my week", "what should I focus on", "my day", "catch me up", morning briefing.
$ npx -y skills add ShenSeanChen/waku-agent --skill weekly-brief --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/weekly-brief
Context preview
The summary Claude sees to decide when to auto-load this skill.
Brief me on my week, my day, or what to focus on. Use for "brief me", "what's on my week", "what should I focus on", "my day", "catch me up", morning briefing.
SKILL.md
weekly-brief.SKILL.mdname: weekly-brief description: Brief me on my week, my day, or what to focus on. Use for "brief me", "what's on my week", "what should I focus on", "my day", "catch me up", morning briefing.
How to brief the user
1. Call `read_apple_calendar` (7 days) to get their real schedule — including events that arrived by email invite. 2. Call `read_apple_mail` (48 hours) to see what's landed in their inbox. Keep the `message://` link for anything worth surfacing. 3. Check memory (the retrieval gate handles this) for their people, projects, and preferences so the brief is personal.
Then write a **focus-first** briefing, not a data dump:
- Open with the 1-3 things that actually matter this week (deadlines, key
meetings, anything time-sensitive from mail).
- Group the rest by day. Note who each meeting is with and why it matters if
you know them from memory.
- For emails that need action, give a one-line "why" and paste the
`message://…` link so they can jump straight to it in Mail.
- End with a short "suggested focus for today."
Keep it skimmable — short lines, no filler. If Calendar or Mail is unavailable (permission not granted), say so plainly and brief on what you can.
Your own AI assistant. On your laptop. In code you can read in an afternoon. Meet Waku — a local-first personal assistant that shows the four pillars behind every serious agent: Harness · Loop · Memory · Eval/LLM-Ops. No frameworks hiding the good parts.
Other skills on waku-agent.
- /excalidraw
Generate an Excalidraw whiteboard in Sean's hand-drawn video style (Excalifont, roughness 1, green signature, socials + watermark, source labels). Use whenever the user wants a whiteboard, diagram, teaching board, or "chart" for a video or the docs/whiteboards gallery — anything
Open skill - /new-tool
Add a new tool to Waku the right way — schema, safe execution, deterministic eval, honest output. Use when adding or modifying agent tools or when the user asks for a new capability.
Open skill - /pr-worktree
Create and tear down the throwaway git worktrees used to test community PRs for waku-agent, without leaking API keys or leaving branches behind. Use when setting up to test a PR, and ALWAYS after a PR is merged, closed, or parked.
Open skill - /review-pr
Walk Sean through an incoming waku-agent PR or issue and present it his way — four fixed sections: what this is, why it matters, how HE can test it with you as copilot, and are we ready to merge / reply / close and why. Use whenever Sean asks to look at, test, triage, or decide
Open skill - /ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
Open skill - /pokedex
Look up any Pokemon's types, base stats, and abilities from the public PokeAPI. Use whenever the user mentions a specific Pokemon by name or asks about its stats, types, or abilities.
Open skill