goal-watches SKILL.md skillA
goal-watches from shannonbay/quarterdeck is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shannonbay/quarterdeck/goal-watches@git:20261119.ab3004fPins git:20261119.ab3004f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shannonbay/quarterdeck
- Path
plugins/quarterdeck-goals/skills/goal-watches/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261119.ab3004f, committed Nov 19, 2026
- First version recorded
- Nov 11, 2026
- Size
- 13,365 bytes
- Repository stars
- 40
- License
- Apache-2.0
Use when a Quarterdeck goal should start a run because something happened (a new GitHub issue or pull request, a new feed entry, a new file, a changed web page, a new email) and not only on a timer. Explains what a watch is, how to write and test its command, recipes for common sources, and when a schedule or a webhook fits better.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Watches for Quarterdeck goals
A goal runs on a schedule. A **watch** also starts a run when something new appears. You set one with `update_goal` (`watches`); the person sees the whole command and confirms it.
A goal run cannot set a watch itself. When it knows what should start its next run ("tell me when a buyer replies"), it calls `propose_watch` (same fields as a watch spec, plus a short `reason`) instead of asking how to watch for it: the request waits under Needs you with the exact command, and nothing runs until the person approves.
## How a watch works
- A watch is a shell command (or, for a connector, a tool: see below), run every few minutes (`every_minutes`, default 5, at least 1) in the goal's working directory.
- The command prints **one line per current item**: an issue number, a feed entry's id, a file name. It exits 0.
- A line it has not printed before is new. New lines queue a run, and that run's brief lists them under `watch_events`.
- The first check only records what is there. It starts nothing.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_l4264blhfjb4kfpd/57552ac83eb6e379b611814b7d5012c11b1baee9a41169fc6149b5c9d6f65b70.json
Then /plugin install goal-watches@markdownregistry-l4264blhfjb4kfpd in Claude Code. It installs git:20261119.ab3004f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shannonbay/quarterdeck/goal-watches@sha256:57552ac83eb6e379The line at the top of this page pins the label git:20261119.ab3004f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_l4264blhfjb4kfpd)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in shannonbay/quarterdeck/goal-watches since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of goal-watches from somewhere else? Ask it: where did my goal-watches come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 6 versions of this file, between Nov 11, 2026 and Nov 19, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261119.ab3004f latest | 2026-11-19 | ab3004f | 13,365 B | A | view · diff |
| git:20261118.2ab1d3a | 2026-11-18 | 2ab1d3a | 10,115 B | A | view · diff |
| git:20261117.752e075 | 2026-11-17 | 752e075 | 9,778 B | A | view · diff |
| git:20261116.3c76381 | 2026-11-16 | 3c76381 | 9,140 B | A | view · diff |
| git:20261114.6129c05 | 2026-11-14 | 6129c05 | 7,946 B | A | view · diff |
| git:20261111.b90aa3c | 2026-11-11 | b90aa3c | 6,754 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/goal-watches/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13365 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
shannonbay/quarterdeck · 40 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l4264blhfjb4kfpd GET https://markdownregistry.com/api/v1/resolve?ref=shannonbay/quarterdeck/goal-watches GET https://markdownregistry.com/api/v1/blob/57552ac83eb6e379b611814b7d5012c11b1baee9a41169fc6149b5c9d6f65b70
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.