arosenkranz/patrol
plugins/workflow-skills/skills/patrol/SKILL.md
Full Gas Town system patrol: hooks → inboxes → convoys → worker pools → cleanup → health check. Trigger phrases: 'run patrol', 'patrol cycle', 'system health check'.
$ install --global
skillsauthnpx skillsauth add arosenkranz/claude-code-config patrolInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 5:30 AM38.8s1 file scanned
SKILL.md
- name:
- patrol
- description:
- Full Gas Town system patrol: hooks → inboxes → convoys → worker pools → cleanup → health check. Trigger phrases: 'run patrol', 'patrol cycle', 'system health check'.
Patrol Cycle
Execute a full Gas Town system patrol in sequence without pausing for confirmation between steps. Report a single summary at the end.
Patrol Sequence
Run all 6 components in this exact order:
- hooks — Verify all hook scripts exist and are executable (
~/.claude/hooks/) - inboxes — Scan inbox directories for pending items; count unprocessed files
- convoys — Check convoy health: active count, throughput, last heartbeat
- worker pools — Inspect utilization; detect zombie/stale workers
- cleanup — Remove stale wisps, temp files, and orphaned lock files
- health — Aggregate system health summary
Issue Classification
For every anomaly found, classify as one of:
KNOWN_FIX— Matches a known failure pattern; auto-resolve immediatelyNOVEL— Unfamiliar issue; escalate to escalation inbox with diagnostic context
Known Fixes (auto-resolve without confirmation)
| Pattern | Detection | Action |
|---------|-----------|--------|
| Stale wisps | Files in wisp dir older than 1 hour | Delete stale files |
| Zombie processes | Process in worker pool with no heartbeat >5 min | kill -9, respawn |
| Stale heartbeats | Heartbeat timestamp >10 min old | Reset heartbeat, mark worker idle |
| Broken symlinks | find returns symlinks with missing targets | Remove broken links |
| Empty inbox dirs | Inbox exists but contains zero files | Log as healthy, no action |
| Orphaned lock files | Lock file with no associated live PID | Remove lock file |
Novel Issue Escalation
When a NOVEL issue is found:
- Write a diagnostic record to
~/.claude/escalations/with timestamp - Include: component name, error description, relevant file paths, suggested investigation steps
- Continue patrol — do not halt on NOVEL issues
Output Format
After completing all 6 steps, output a single Markdown table:
| Component | Status | Last Checked | Action Taken |
|--------------|---------|---------------------|---------------------------|
| hooks | OK | 2026-02-28 14:32:01 | none |
| inboxes | OK | 2026-02-28 14:32:02 | 3 items processed |
| convoys | WARN | 2026-02-28 14:32:03 | reset stale heartbeat |
| worker pools | OK | 2026-02-28 14:32:04 | none |
| cleanup | OK | 2026-02-28 14:32:05 | 2 stale wisps removed |
| health | OK | 2026-02-28 14:32:06 | 1 NOVEL issue escalated |
Status values: OK | WARN | ERROR | ESCALATED
Headless / Long-Running Behavior
- Never pause for confirmation between steps
- After 20 patrol cycles, output a clean handoff summary: total issues found, KNOWN_FIX resolved, NOVEL escalated, next recommended action
- If a step takes >30s, log timeout and move to next step — do not block the cycle
- Do not open editors, browsers, or interactive processes during patrol
Related Skills
arosenkranz/spec-and-plan
tools
VerifiedTrustedCommunity
Lightweight orchestrator for spec-before-plan workflow. Use when starting a feature with ambiguous requirements. Walks SPEC.md → PLAN.md → execute, delegating to /superpowers:writing-plans and /superpowers:executing-plans. Invoke when asked to "spec this out", "spec-first", "spec and plan for X", or when feature requirements are vague.
1SKILL.mdUpdated May 12, 2026
arosenkranz/problem-statement
tools
VerifiedTrustedCommunity
Problem Statement Co-Authoring Skill
1SKILL.mdUpdated Apr 23, 2026
arosenkranz/maintaining-brag-docs
development
VerifiedTrustedCommunity
Structure and maintain professional brag documents with clear templates for accomplishments, projects, and growth tracking. Use when documenting achievements, creating brag document entries, formatting accomplishments, or tracking career progress.
1SKILL.mdUpdated Apr 23, 2026
arosenkranz/linting-technical-writing
development
VerifiedTrustedCommunity
Analyze technical documentation for clarity, conciseness, and effectiveness using Google Technical Writing principles. Use when reviewing documentation, checking writing quality, improving docs, or providing writing feedback.
1SKILL.mdUpdated Apr 23, 2026