pilot-watch-alert-response SKILL.md skillA
pilot-watch-alert-response from confighub/cub-scout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add confighub/cub-scout/pilot-watch-alert-response@git:20260926.4c4b67cPins git:20260926.4c4b67c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- confighub/cub-scout
- Path
skills/pilot-watch-alert-response/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.4c4b67c, committed Sep 26, 2026
- First version recorded
- May 22, 2026
- Size
- 22,677 bytes
- Repository stars
- 14
- License
- MIT
Use when Pilot is RESPONDING TO REAL-TIME CLUSTER EVENTS surfaced by `cub-scout watch` or `cub-scout bot`. Natural phrasings: "Pilot subscribes to the watch stream", "render verdicts on each drift event as they fire", "real-time acceptance kernel for cluster changes", "Pilot, decide on this drift.detected event", "what does Pilot say about the ownership.changed alert", "stream PASS/WATCH/ASK/BLOCK per event from cub-scout watch". Pilot consumes the `cub-scout watch` / `cub-scout bot` event…
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
# pilot-watch-alert-response The real-time event-driven scenario from **Pilot's** side. Pilot subscribes to `cub-scout watch` or `cub-scout bot` (which expose the same webhook / file event sinks) and, for each event, decides PASS / WATCH / ASK / BLOCK — calling back into cub-scout for context as needed. This is the **only event-driven skill in the pilot-* batch**; the other four are query-driven. With the receipts v2 surface shipped (#463), Pilot can ask `cub-scout watch` or `cub-scout bot` to **inline a receipt** with each matching event via `--emit-receipt-on drift.detected,ownership.changed` or `--emit-receipt-on all`. That delivers a fingerprinted in-toto Statement v1 per event in the same JSONL line — Pilot reads the verdict + receipt in one shot, no synchronous call-back required for the common case. ## When to use Explicit phrasings: - "Pilot subscribes to the watch stream" - "Render verdicts on each drift event as they fire" - "Real-time acceptance kernel for cluster changes" - "Pilot, decide on this `drift.detected` event" - "What does Pilot say about the `ownership.changed` alert" - "Stream PASS/WATCH/ASK/BLOCK per event from cub-scout watch" …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/pilot-watch-alert-response@sha256:87dc505495db4087The line at the top of this page pins the label git:20260926.4c4b67c, 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_43mkxa2xtw4tr3ob)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 22, 2026 and Sep 26, 2026, about one every 32 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.4c4b67c latest | 2026-09-26 | 4c4b67c | 22,677 B | A | view · diff |
| git:20260910.e36f2e2 | 2026-09-10 | e36f2e2 | 22,324 B | A | view · diff |
| git:20260525.11ef6bb | 2026-05-25 | 11ef6bb | 22,072 B | A | view · diff |
| git:20260522.82ceddc | 2026-05-22 | 82ceddc | 21,725 B | A | view · diff |
| git:20260522.7d424d1 | 2026-05-22 | 7d424d1 | 20,033 B | A | view |
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 (22677 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
confighub/cub-scout · 14 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_43mkxa2xtw4tr3ob GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/pilot-watch-alert-response GET https://markdownregistry.com/api/v1/blob/87dc505495db40870493271a34b8477145e587cc66603f6fa7631232a2a054bd
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.