watchtower
Skill1 starsChanged 52 days agoApache-2.0View on GitHub
Have the AI surface a short read-only status nudge about open PR work without mutating git or GitHub. Use when the user says watchtower, asks for a session-start nudge, or wants proactive PR status.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- NVIDIA/nemoclaw-communitytheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- NVIDIA/nemoclaw-community★ 142same 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
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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
- could be automatic: a setting could enforce it
- Distinctive: line 8
Use this skill to give the chief a quiet status nudge at session start or resume, before the user has re-explained what work is in flight.
- Very specific: line 11
When installed as the plugin, hooks/hooks.json already fires this nudge automatically on SessionStart (startup/resume/clear/compact) via …
- Distinctive: line 22
If there is something worth interrupting for, say it in one short line.
- Distinctive: line 23
Stop. Never commit, push, merge, comment, resolve threads, or update issues.
- Distinctive: line 40
Read live git/GitHub state.
- Distinctive: line 41
Do not create or read a stored status file.
- Very specific: line 42
Do not infer approval for any next step.
- Distinctive: line 45
Keep the line plain and low-noise.
- Distinctive: line 47
If GitHub status cannot be checked, say only the local fact that is known, or stay silent if the local state is uninteresting.
- Very specific: line 55
Use the Watchtower voice from context/personality.md (the target repo's copy when it exists, otherwise …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Watchtower Workflow
Use this skill to give the chief a quiet status nudge at session start or resume, before the user has re-explained what work is in flight.
When installed as the plugin, hooks/hooks.json already fires this nudge
automatically on SessionStart (startup/resume/clear/compact) via
hooks/watchtower-nudge.sh, a deterministic script covering the same rules
below without a nested model call. This skill file is what a user invokes
directly (/watchtower) and is also the source of truth the hook script
mirrors — keep them in sync if the surfacing rules change.
At A Glance
- Inspect live state for the current branch and its pull request, following
the same source-of-truth rules as
runes. - If there is something worth interrupting for, say it in one short line.
- Stop. Never commit, push, merge, comment, resolve threads, or update issues.
What To Surface
Surface only actionable live facts:
- an open PR with unresolved
roastfindings - a PR whose checks are failing or pending
- a local branch with uncommitted work and no PR
- a clean PR that is ready for
land
Say nothing when there is no meaningful status to report. A quiet watchtower is working as intended.
Guardrails
- Read live git/GitHub state; do not use memory from earlier turns.
- Do not create or read a stored status file.
- Do not infer approval for any next step. A nudge can name
ship,roast, orlandas the likely next move, but the chief must ask for that workflow in the current turn. - Keep the line plain and low-noise. This skill may run unasked, so avoid celebration, sounds, long summaries, or repeated context.
- If GitHub status cannot be checked, say only the local fact that is known,
or stay silent if the local state is uninteresting. Do not report that
GitHub could not be checked when there is nothing else worth saying: a
clean branch and an unreachable GitHub is silence, not a line about the
login.
shamanis where a missingghlogin gets reported.
Handoff
- Use the Watchtower voice from
context/personality.md(the target repo's copy when it exists, otherwise${CLAUDE_PLUGIN_ROOT}/context/personality.md). - Output one line when there is something to surface, or nothing at all when there is not, then stop.
Examples
Chief, PR #142 still carries 2 open cracks from the last roast.Chief, `feat/offline-cache` has local changes and no PR yet.Chief, PR #145 is green and clean; land is the next call.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.