Skill
excalidraw
Generate an Excalidraw whiteboard in Sean's hand-drawn video style (Excalifont, roughness 1, green signature, socials + watermark, source labels). Use whenever…
@shenseanchenView SkillProductivity
Skill
/waku-memory
Connect Waku Memory, hosted cross-agent memory in Claude Code, Codex, Grok Bot, Hermes. Export Waku skills.
Install
$ npx -y skills add ShenSeanChen/waku-agent --skill waku-memory --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
/waku-memory
Context preview
The summary Claude sees to decide when to auto-load this skill.
Connect Waku Memory, hosted cross-agent memory in Claude Code, Codex, Grok Bot, Hermes. Export Waku skills.
SKILL.md
waku-memory.SKILL.mdname: waku-memory
description: Connect Waku Memory, hosted cross-agent memory in Claude Code, Codex, Grok Bot, Hermes. Export Waku skills.
What Waku Memory is
This app's memory is local. It lives in `.waku/` on this machine and never leaves it. Waku Memory (waku.one) is a separate, hosted memory that several agents share over MCP: a fact saved in Claude Code can be recalled in Codex, Grok Bot or this app. The two stores are separate, so never tell the user that local memory syncs to Waku Memory.
Connecting this app
Connecting opens the user's browser, so you cannot do it for them. Tell them to type `/connect waku-memory` in the dashboard chat, or to run `waku connect waku-memory` in a terminal. It needs the MCP extra: `pip install 'waku-agent[mcp]'`. After it connects, a restart of Waku loads the `waku_memory_*` tools.
Connecting other agents
- **Claude Code, Codex, Hermes:** point them to https://www.waku.one/docs.
- **Grok Bot:** Settings → Plugins → add a custom connector with the URL
`https://api.waku.one/mcp` and the header `Authorization: Bearer <key>`, using a key from waku.one → Account → Keys. Its connector form takes a URL and a header, not a browser sign-in, which is why it needs the key.
- **Muse Code or any other MCP client:** add `https://api.waku.one/mcp` as a
remote (streamable HTTP) server.
Tell the user to paste a key only into the other agent's own settings, never into this chat.
Carrying skills
`waku skill export --to claude,codex` copies Waku's skills into Claude Code's and Codex's skills folders. `--project` writes to `./.claude/skills`, which Muse Code also reads. Saving skills into Waku Memory is not available yet.
What not to claim
Don't quote prices, plans or limits; point to https://www.waku.one/docs.
Read more
name: waku-memory description: Connect Waku Memory, hosted cross-agent memory in Claude Code, Codex, Grok Bot, Hermes. Export Waku skills.
What Waku Memory is
This app's memory is local. It lives in `.waku/` on this machine and never leaves it. Waku Memory (waku.one) is a separate, hosted memory that several agents share over MCP: a fact saved in Claude Code can be recalled in Codex, Grok Bot or this app. The two stores are separate, so never tell the user that local memory syncs to Waku Memory.
Connecting this app
Connecting opens the user's browser, so you cannot do it for them. Tell them to type `/connect waku-memory` in the dashboard chat, or to run `waku connect waku-memory` in a terminal. It needs the MCP extra: `pip install 'waku-agent[mcp]'`. After it connects, a restart of Waku loads the `waku_memory_*` tools.
Connecting other agents
- **Claude Code, Codex, Hermes:** point them to https://www.waku.one/docs.
- **Grok Bot:** Settings → Plugins → add a custom connector with the URL
`https://api.waku.one/mcp` and the header `Authorization: Bearer <key>`, using a key from waku.one → Account → Keys. Its connector form takes a URL and a header, not a browser sign-in, which is why it needs the key.
- **Muse Code or any other MCP client:** add `https://api.waku.one/mcp` as a
remote (streamable HTTP) server.
Tell the user to paste a key only into the other agent's own settings, never into this chat.
Carrying skills
`waku skill export --to claude,codex` copies Waku's skills into Claude Code's and Codex's skills folders. `--project` writes to `./.claude/skills`, which Muse Code also reads. Saving skills into Waku Memory is not available yet.
What not to claim
Don't quote prices, plans or limits; point to https://www.waku.one/docs.
Ships withwaku-agent
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.
Get the whole plugin
Other skills on waku-agent.
@shenseanchenView SkillSkill
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…
@shenseanchenView SkillSkill
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…
@shenseanchenView SkillSkill
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…
@shenseanchenView SkillSkill
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…
@shenseanchenView SkillSkill
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…
@shenseanchenView Skill