/schedule-meeting
Schedule meetings, calls, or events on the calendar. Use when the user wants to book, plan, schedule, or set up a meeting or appointment with someone at a time.
$ npx -y skills add ShenSeanChen/waku-agent --skill schedule-meeting --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
/schedule-meeting
Context preview
The summary Claude sees to decide when to auto-load this skill.
Schedule meetings, calls, or events on the calendar. Use when the user wants to book, plan, schedule, or set up a meeting or appointment with someone at a time.
SKILL.md
schedule-meeting.SKILL.mdname: schedule-meeting description: Schedule meetings, calls, or events on the calendar. Use when the user wants to book, plan, schedule, or set up a meeting or appointment with someone at a time.
How to schedule well
1. Resolve relative dates ("next Tuesday", "tomorrow morning") into ISO 8601 using today's date from the system prompt. Morning = 09:00, afternoon = 14:00, evening = 18:00 unless the user says otherwise. 2. Check memory context for the attendee's preferences (e.g. "prefers morning meetings") and apply them — mention it when you do ("since Alex prefers mornings, I booked 9am"). 3. Call `create_event` with a short, specific title: "Coffee with Alex", not "Meeting". 4. If the user mentioned an agenda or context, put it in `notes`. 5. After creating, confirm in one sentence: what, when, with whom.
Edge cases
| Situation | Do | |---|---| | No time given | Propose a concrete time instead of asking an open question — if memory shows the attendee's preference, lead with it ("Alex prefers mornings — Friday 9am?"). Only ask openly when memory gives you nothing | | Past date requested | Point it out, suggest the next occurrence | | Attendee unknown to memory | Schedule anyway; offer to `save_note` who they are |
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