How do I install the Wander Monitor skill?

Run npx skillmds@latest add dvcrn/wander-monitor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wander Monitor safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wander Monitor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wander Monitor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wander Monitor?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wander Monitor by dvcrn — Agent Skill

Name: Wander Monitor
Rating: 4.2 (5 reviews)
Author: dvcrn

Wander Monitor

Guides users on using Wander to monitor GitHub Actions workflows. Use when user asks how to watch CI/CD runs, avoid polling Actions page, get notified when workflows complete, or integrate Wander with a project. Covers smart-push, foreground/background/detached modes, edge cases, and project integration.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

Wander — CI/CD Monitor Skill

Don't watch. Wander. Elegant automation for monitoring GitHub Actions without polling.

When to use this skill

User wants to monitor a GitHub Actions workflow after push
User asks how to get notified when CI completes
User wants to avoid refreshing the Actions page
User integrates CI monitoring into a project (e.g. ClawHub publish)

Install

git clone https://github.com/ERerGB/wander.git
cd wander
chmod +x *.sh

Prerequisites: gh CLI (authenticated), jq, macOS (for notifications)

Usage patterns

1. Smart push (recommended for Wander's own repo)

cd wander
./smart-push.sh

Recommends smoke / e2e / skip based on changed files. Pushes and monitors.

2. Manual control (any repo)

# From target repo (e.g. openclaw-uninstall)
git push

# Choose monitoring mode:
../wander/watch-workflow.sh publish.yml      # Foreground, block until done
../wander/watch-workflow-bg.sh publish.yml  # Background, macOS notify when done
../wander/watch-workflow-detached.sh publish.yml  # Detached, can close terminal

3. Project integration

Add a wrapper script in the project:

#!/bin/bash
# scripts/watch-publish.sh
REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
WANDER_DIR="${WANDER_DIR:-$(dirname "$REPO_ROOT")/wander}"
cd "$REPO_ROOT"
exec "$WANDER_DIR/watch-workflow-bg.sh" publish.yml "$@"

Then: git push && ./scripts/watch-publish.sh

Edge cases (from experience)

Scenario	Behavior	Tip
Workflow finishes in < 30s	"Already completed" + immediate notify	Use `watch-workflow-bg`; it detects recent completion
Push then monitor immediately	Workflow may not start for 5–10s	Script waits up to 30s for workflow to appear
Wrong branch	No workflow after 30s	Ensure workflow is configured for current branch
No lock file in repo	setup-node `cache: npm` fails	Remove `cache: "npm"` from workflow if no package-lock.json

Workflow registry

For custom check_window / expected_duration, add .workflows.yml in project root or set WORKFLOW_REGISTRY_FILE:

workflows:
  - name: "publish.yml"
    description: "Publish to ClawHub"
    check_window: 120
    expected_duration: 30
    category: "publish"

Default: check_window=300 when workflow not in registry.

Reference

---name: wander-monitordescription: Guides users on using Wander to monitor GitHub Actions workflows. Use when user asks how to watch CI/CD runs, avoid polling Actions page, get notified when workflows complete, or integrate Wander with a project. Covers smart-push, foreground/background/detached modes, edge cases, and project integration.---# Wander — CI/CD Monitor Skill**Don't watch. Wander.** Elegant automation for monitoring GitHub Actions without polling.## When to use this skill- User wants to monitor a GitHub Actions workflow after push- User asks how to get notified when CI completes- User wants to avoid refreshing the Actions page- User integrates CI monitoring into a project (e.g. ClawHub publish)---## Install```bashgit clone https://github.com/ERerGB/wander.gitcd wanderchmod +x *.sh```**Prerequisites**: `gh` CLI (authenticated), `jq`, macOS (for notifications)---## Usage patterns### 1. Smart push (recommended for Wander's own repo)```bashcd wander./smart-push.sh```Recommends smoke / e2e / skip based on changed files. Pushes and monitors.### 2. Manual control (any repo)```bash# From target repo (e.g. openclaw-uninstall)git push# Choose monitoring mode:../wander/watch-workflow.sh publish.yml # Foreground, block until done../wander/watch-workflow-bg.sh publish.yml # Background, macOS notify when done../wander/watch-workflow-detached.sh publish.yml # Detached, can close terminal```### 3. Project integrationAdd a wrapper script in the project:```bash#!/bin/bash# scripts/watch-publish.shREPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"WANDER_DIR="${WANDER_DIR:-$(dirname "$REPO_ROOT")/wander}"cd "$REPO_ROOT"exec "$WANDER_DIR/watch-workflow-bg.sh" publish.yml "$@"```Then: `git push && ./scripts/watch-publish.sh`---## Edge cases (from experience)| Scenario | Behavior | Tip ||----------|----------|-----|| Workflow finishes in < 30s | "Already completed" + immediate notify | Use `watch-workflow-bg`; it detects recent completion || Push then monitor immediately | Workflow may not start for 5–10s | Script waits up to 30s for workflow to appear || Wrong branch | No workflow after 30s | Ensure workflow is configured for current branch || No lock file in repo | setup-node `cache: npm` fails | Remove `cache: "npm"` from workflow if no package-lock.json |---## Workflow registryFor custom `check_window` / `expected_duration`, add `.workflows.yml` in project root or set `WORKFLOW_REGISTRY_FILE`:```yamlworkflows: - name: "publish.yml" description: "Publish to ClawHub" check_window: 120 expected_duration: 30 category: "publish"```Default: `check_window=300` when workflow not in registry.---## Reference- [Wander README](https://github.com/ERerGB/wander)- [EDGE_CASES.md](https://github.com/ERerGB/wander/blob/main/EDGE_CASES.md)- [COFFEE_BREAK.md](https://github.com/ERerGB/wander/blob/main/COFFEE_BREAK.md)

Frequently asked questions