wake
Skill2 starsChanged 9 days agoApache-2.0View on GitHub
Arm the Snapper review-request watch monitor for THIS session only
6 other projects use a version of this.
Adopted by
Most recently taken up by
- loonylabs-dev/claude-setuptheir own version, first seen Nov 1, 2026
- loonylabs/claude-setuptheir own version, first seen Oct 17, 2026
- Wolfgangrush/ai-brain-uktheir own version, first seen Oct 11, 2026
- iAmCorey/Waketheir own version, first seen Oct 8, 2026
- lemomo-ai/lemo-waketheir own version, first seen Oct 3, 2026
- timoncool/dream-skilltheir own version, first seen Jul 7, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- iAmCorey/Wake★ 1.5ksame name
- lemomo-ai/lemo-wake★ 227same name
- timoncool/dream-skill★ 3same name
- Wolfgangrush/ai-brain-uk★ 1same name
- loonylabs-dev/claude-setup★ 0same name
- loonylabs/claude-setup★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Check that a watch process is now running:
- Distinctive: line 20
Treat matches as candidates: another session or plugin may own them.
- Distinctive: line 24
If there is no verified monitor for this session after a few seconds, the host did not honour the trigger (older release, or a monitor left …
- Distinctive: line 35
If this check fails, locate the correct seeded file before continuing.
- Very specific: line 36
After the check succeeds, start the command below through the Monitor tool, persistent and without a timeout — NOT a backgrounded shell …
- Very specific: line 45
Do not use an ambient CLAUDE_PLUGIN_DATA value without verifying that it belongs to snapper-mcp.
- Very specific: line 47
Never print the file — it holds a credential.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Invoking this skill arms the bundled watch monitor for this session — the
plugin declares it with when: "on-skill-invoke:snapper-mcp:wake", so the host
starts it in response to this very invocation. Arm only one session at a time;
every armed session receives the same requests.
Confirm it actually started, then stop:
Check that a watch process is now running:
pgrep -af '[s]napper-mcp.*watch'Treat matches as candidates: another session or plugin may own them. Confirm the host monitor record belongs to this session and that the process uses this plugin's resolved configuration path. A process match alone does not establish that this session is armed.
If there is no verified monitor for this session after a few seconds, the host did not honour the trigger (older release, or a monitor left over from an earlier version is holding the name). Resolve this plugin's actual seeded
env.jsonfrom the installedsnapper-mcpdata directory or its host configuration. Replace the placeholder in both commands below with that same absolute path. First verify the file exists, without printing its credential contents:test -f "/absolute/path/to/snapper-mcp/data/env.json"If this check fails, locate the correct seeded file before continuing. After the check succeeds, start the command below through the Monitor tool, persistent and without a timeout — NOT a backgrounded shell command, which only reports when the process exits, and
watchis built never to exit:npx -y @mateusz-klatt/snapper-mcp@0.15.0 watch --config="/absolute/path/to/snapper-mcp/data/env.json"Do not use an ambient
CLAUDE_PLUGIN_DATAvalue without verifying that it belongs tosnapper-mcp; another plugin can own it. Never print the file — it holds a credential. Do not add--topic: it replaces the defaults and would silently dropai_reviews..- Either way, before reporting success make sure the monitor survived startup.
On connect
watchlogssubscribing to topics: ..., and that list must include bothai_reviews.andai_research..
Once armed, pending review requests addressed to this delegate stream as JSONL
and wake you; answer each ai_review.request before its deadline using the
submit_ai_review_decision tool. signal and decision_ack frames are
informational — they need no reply.
A session that never invokes this skill never starts a monitor, so it does not connect, consume tokens, or compete for the same request. The monitor is not restored when a session resumes — invoke this skill again to re-arm it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

