patrol
Use when inspecting external production surfaces for unanswered customer inbox queues, official email notices and dual-store revenue discrepancies; checking published store releases, live sites or social posts for stalled outward results after a reasonable delivery interval; checking external effects against the accountable owner's scope and authorized spending or change limits; or replacing recurring LLM inbox polling with a zero-token file-watch trigger daemon. Do NOT use when the task is internal transcript inspection, routine progress reports or ETA solicitation. Use prove-it to establish one claim or review a diff, unblock to restore stalled work, author-item to file a new outcome and challenge to compare designs.
Target: Office & team collaboration. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Patrol
- External Ground-Truth Patrol vs. Self-Report Reading
- Read the original
- Measure against a limit
- Bound a live change
- Observe a reasonable external interval
- Share external evidence without directing execution
- Autonomous Skill Distillation Gate (Completion / Exit Gate)
Inspect actual user, customer, account and financial outcomes, and give the accountable owner verified external evidence of a scope mismatch, breach or stalled result. Patrol does not demand explanations, inspect private turn progress or direct another person's implementation. Evidence standards live in prove-it. Inspect external production and customer surfaces directly: A worker's self-reported status file or chat summary only reflects what that worker noticed; blind spots happen outside the worker's attention. On every patrol pass, inspect external ground-truth surfaces directly rather than relying on workers' self-reported status files: 1. Unanswered customer inbox queues: Read live support and social inbox threads directly for unanswered inbound customer messages or API messaging-window delivery failures. 2. Dual-store revenue reconciliation: Reconcile payment-channel settlement records against the canonical order table that powers live revenue analytics so unprojected orders, cross-currency mismatches, or untracked grants surface immediately. 3. Live endpoint responses: Probe public domains and health endpoints as an external client (without internal routing headers) to detec
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- SylphxAI/skills
- Source file
- skills/patrol/SKILL.md
- Fixed revision
- e61c6f49e7bc2ac4f764590438fe01a689addefb
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: SylphxAI/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T01:01:23.972Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.