monitor-tool
Monitor tool for streaming background process events into conversations — tail logs, watch CI, auto-fix dev server crashes, and /loop self-pacing without Bash sleep loops
What this skill does
# Monitor Tool
The Monitor tool spawns a background watcher and streams its events into the conversation as new transcript messages. Each event lands immediately and Claude reacts to it — no polling loop, no holding the turn open with a `sleep`.
Available since v2.1.98.
## What It Does
```
Bash (sleep loop, polling) Monitor tool
━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━
while true; do # Claude spawns a watcher
check_ci_status # Watcher runs in background
sleep 30 # Each event → new message
done # Claude reacts immediately
```
The conversation stays open. Events arrive asynchronously. Claude processes each one and decides whether to act.
## Common Use Cases
### Tail a log file
```
> Tail server.log in the background and tell me the moment a 5xx shows up
```
Claude spawns a watcher on `server.log`. Each new log line arrives as a transcript message. When a 5xx pattern matches, Claude reacts immediately — describe the error, suggest a fix, or apply one automatically.
### Watch CI on a PR
```
> Watch CI on my current branch and fix any failures as they come in
```
Claude monitors the CI status. When a check fails, it reads the failure output, writes a fix, and pushes — all without you sitting at the terminal.
### Auto-fix dev server crashes
```
> Start the dev server in the background, watch for crashes, and restart and fix when it crashes
```
Claude starts the server, monitors its output, and when a crash appears, reads the traceback, patches the code, and restarts.
### Training run progress
```
> Kick off training and summarize progress every epoch without keeping the session idle
```
Claude monitors training output and sends epoch summaries as events arrive.
## /loop Self-Pacing
`/loop` now self-paces: if you omit the interval, Claude picks the next tick based on what it's waiting for. When the Monitor tool is available, Claude reaches for it instead of polling.
```
> /loop check CI on my PR
```
Claude will:
1. Use the Monitor tool to watch CI (not poll with sleep)
2. React the moment a result arrives
3. Schedule the next check only if the Monitor can't be used
### Explicit interval (still works)
```
> /loop --interval 60 run the dependency audit
```
### Dynamic (recommended)
```
> /loop check CI on my PR
```
## Pairing Monitor with PreToolUse hooks
If you want to gate what Monitor can watch (e.g., only internal hosts):
```json
{
"hooks": {
"PreToolUse": [{
"hooks": [{
"if": "Monitor(*)",
"type": "command",
"command": ".claude/hooks/monitor-allowlist.sh"
}]
}]
}
}
```
```bash
#!/usr/bin/env bash
# monitor-allowlist.sh — only allow monitoring local files and localhost
set -euo pipefail
INPUT=$(cat)
TARGET=$(echo "$INPUT" | jq -r '.tool_input.target // ""')
case "$TARGET" in
*.log|localhost:*|/tmp/*)
echo '{"decision": "approve"}'
;;
*)
jq -n --arg t "$TARGET" '{"decision":"block","reason":("Monitor target not allowed: "+$t)}'
;;
esac
```
## Decision: Monitor vs Bash Loop vs ScheduleWakeup
| Scenario | Best Tool |
|----------|-----------|
| React to log events in real time | Monitor tool |
| Wait for a known-duration process (8-min build) | ScheduleWakeup (~270s, stays in cache) |
| Poll a REST endpoint every minute | Monitor tool (wrap in a watcher script) |
| Long-idle background check (>30 min) | ScheduleWakeup (1200s+) |
| One-shot process check on demand | Bash |
## Available in
- CLI (v2.1.98+)
- Desktop app
- Not available in `-p` (print/pipe) headless mode
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.