Agent skill

Workflow Monitor

by athola in athola/claude-night-market

Detects workflow failures and inefficient patterns then files GitHub issues.

MITAuto-check passedDevelopment

Install Workflow Monitor

skills CLI
$ npx skills add athola/claude-night-market --skill workflow-monitor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install athola/claude-night-market workflow-monitor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/athola/claude-night-market.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/imbue/skills/workflow-monitor .claude/skills/workflow-monitor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-monitor
GitHub stars
341
Token cost
~1.6k tokens
SKILL.md length
465 words
Files
4
Skills in repo
152
Repo updated
First seen
Licence
MIT

At a glance

Detects workflow failures and inefficient patterns then files GitHub issues.

  • Works in 4 steps: Capture… → Analyze… → Report (workflow-monitor:report-generated) → …
  • A workflow step repeatedly fails
  • SKILL.md covers When NOT To Use, Philosophy, Quick Start and Detection Patterns, plus 9 more sections
  • Calls gh

What it does

Workflow Monitor is an agent skill from athola/claude-night-market. Detects workflow failures and inefficient patterns then files GitHub issues. Use when a workflow step repeatedly fails or produces inconsistent output.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `modules/detection-patterns.md`, `modules/efficiency-metrics.md` and `modules/issue-templates.md`).

It sits in Development. It works with GitHub and Git. The repository describes itself as: 23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context… The licence is MIT.

When your agent uses it

  • A workflow step repeatedly fails
  • Produces inconsistent output

Example prompts

  • “Use the workflow-monitor skill to detect workflow failures and inefficient patterns then files GitHub issues”
  • “/workflow-monitor”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Capture (workflow-monitor:capture-complete)
  2. Analyze (workflow-monitor:analysis-complete)
  3. Report (workflow-monitor:report-generated)
  4. Create Issue (workflow-monitor:issue-created)

What it can do on your machine

Read from SKILL.md and the folder at commit 9f3eb00. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow Monitor loads about 1.6k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 465 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from athola/claude-night-market at commit 9f3eb00, republished under its MIT licence (© athola). 465 words, ~1,634 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-monitor/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
workflow-monitor
description
Detects workflow failures and inefficient patterns then files GitHub issues. Use when a workflow step repeatedly fails or produces inconsistent output.
alwaysApply
false
category
workflow-methodology
tags
workflow, monitoring, error-detection, efficiency, automation
dependencies
leyline:git-platform, imbue:proof-of-work, sanctum:workflow-improvement
usage_patterns
error-detection, efficiency-analysis, issue-creation
complexity
intermediate
model_hint
standard
estimated_tokens
2500
modules
modules/detection-patterns.md, modules/issue-templates.md, modules/efficiency-metrics.md

When NOT To Use

  • A one-off failure worth debugging directly (use superpowers:systematic-debugging)
  • Rewriting the workflow's assets (use sanctum:workflow-improvement)

Workflow Monitor

Monitor workflow executions for errors and inefficiencies, automatically creating issues on the detected git platform (GitHub/GitLab) for improvements. Check session context for git_platform: and use Skill(leyline:git-platform) for CLI command mapping.

Philosophy

Workflows should improve over time. When execution issues occur, capturing them systematically enables continuous improvement. This skill hooks into workflow execution to detect problems and propose fixes.

Quick Start

Manual Invocation
bash
# After a failed workflow
/workflow-monitor --analyze-last

# Monitor a specific workflow execution
/workflow-monitor --session <session-id>

# Analyze efficiency of recent workflows
/workflow-monitor --efficiency-report
Automatic Monitoring (via hooks)

When enabled, workflow-monitor observes execution and flags:

  • Command failures (exit codes > 0)
  • Timeout events
  • Repeated retry patterns
  • Context exhaustion
  • Inefficient tool usage

Detection Patterns

Error Detection
PatternSignalSeverity
Command failureExit code > 0High
TimeoutExceeded timeout limitHigh
Retry loopSame command >3 timesMedium
Context exhaustion>90% context usedMedium
Tool misuseWrong tool for taskLow
Efficiency Detection
PatternSignalThreshold
Verbose output>1000 lines from command500 lines recommended
Redundant readsSame file read >2 times2 reads max
Sequential vs parallelIndependent tasks run sequentiallyShould parallelize
Over-fetchingRead entire file when snippet neededUse offset/limit

Workflow

Phase 1: Capture (workflow-monitor:capture-complete)
  1. Log execution events - Commands, outputs, timing
  2. Tag anomalies - Failures, timeouts, inefficiencies
  3. Store evidence - For reproducibility
Phase 2: Analyze (workflow-monitor:analysis-complete)
  1. Classify issues - Error type, severity, scope
  2. Identify root cause - What triggered the issue
  3. Suggest fix - What would prevent recurrence
Phase 3: Report (workflow-monitor:report-generated)
  1. Generate issue body - Structured format
  2. Assign labels - workflow, bug, enhancement
  3. Link evidence - Command outputs, session info
Phase 4: Create Issue (workflow-monitor:issue-created)
  1. Check for duplicates - Search existing issues
  2. Create if unique - Via gh CLI
  3. Link to session - For traceability
Show full SKILL.md (180 more words)Show less

Issue Template

markdown
## Background

Detected during workflow execution on [DATE].

**Source:** [workflow name] session [session-id]

## Problem

[Description of the error or inefficiency]

**Evidence:**

[Command that failed or was inefficient] [Output excerpt]


## Suggested Fix

[What should change to prevent this]

## Acceptance Criteria

- [ ] [Specific fix criterion]
- [ ] Tests added for new behavior
- [ ] Documentation updated

---
*Created automatically by workflow-monitor*

Configuration

yaml
# .workflow-monitor.yaml
enabled: true
auto_create_issues: false  # Require approval before creating
severity_threshold: "medium"  # Only report medium+ severity
efficiency_threshold: 0.7  # Flag workflows below 70% efficiency

detection:
  command_failures: true
  timeouts: true
  retry_loops: true
  context_exhaustion: true
  tool_misuse: true

efficiency:
  verbose_output_limit: 500
  max_file_reads: 2
  parallel_detection: true

Guardrails

  1. No duplicate issues - Check existing issues before creating
  2. Approval required - Unless auto_create_issues: true
  3. Evidence required - Every issue must have reproducible evidence
  4. Rate limiting - Max 5 issues per session

Required TodoWrite Items

  1. workflow-monitor:capture-complete
  2. workflow-monitor:analysis-complete
  3. workflow-monitor:report-generated
  4. workflow-monitor:issue-created (if issue created)

Integration Points

  • imbue:proof-of-work: Captures execution evidence
  • sanctum:fix-workflow: Implements suggested fixes
  • Hooks: Can be triggered by session hooks for automatic monitoring

Output Format

Efficiency Report
markdown
## Workflow Efficiency Report

**Session:** [session-id]
**Duration:** 12m 34s
**Efficiency Score:** 0.72 (72%)

### Issues Detected

| Type | Count | Impact |
|------|-------|--------|
| Verbose output | 3 | Medium |
| Redundant reads | 2 | Low |
| Sequential tasks | 1 | Medium |

### Recommendations

1. Use `--quiet` flags for npm/pip commands
2. Cache file contents instead of re-reading
3. Parallelize independent file operations

### Create Issues?

- [ ] Issue 1: Verbose output from npm install
- [ ] Issue 2: Redundant file reads in validation
  • imbue:proof-of-work: Evidence capture methodology
  • sanctum:fix-workflow: Workflow improvement command

Status: Skeleton implementation. Requires:

  • Hook integration for automatic monitoring
  • Efficiency scoring algorithm
  • Duplicate detection logic

Exit Criteria

  • All 4 TodoWrite phases completed: capture-complete, analysis-complete, report-generated, and (if an issue is created) issue-created
  • Every issue filed contains reproducible evidence: the exact command that failed or was inefficient plus an output excerpt
  • Duplicate check run via gh issue list --search before creating any issue; duplicate suppressed and existing issue URL reported instead
  • No more than 5 issues created per session regardless of how many anomalies are detected; rate limit enforced

© athola, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in plugins/imbue/skills/workflow-monitor of athola/claude-night-market.

  • SKILL.md
  • modules/detection-patterns.md
  • modules/efficiency-metrics.md
  • modules/issue-templates.md

Open the folder on GitHubat commit 9f3eb00

Compare with similar skills

Workflow Monitor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow Monitor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Monitor this skillathola/claude-night-market341—~1.6kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0

Similar skills

  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from athola/claude-night-market

All 152 skills in this repo
  • Night Market Diagnostics Toolkit

    athola/claude-night-market

    Run and interpret repo diagnostic scripts (ratchets, validators, token stats).

    341 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Skills Eval

    athola/claude-night-market

    Evaluate Claude skill quality through auditing. An agent skill from athola/claude-night-market.

    341 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Agent Teams

    athola/claude-night-market

    Coordinates Claude agent teams via filesystem protocol. An agent skill from athola/claude-night-market.

    341 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Delegation Core

    athola/claude-night-market

    Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer).

    341 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Elegant Code

    athola/claude-night-market

    Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage.

    341 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Skill Library Mission

    athola/claude-night-market

    Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review.

    341 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Workflow Monitor

What does Workflow Monitor do?

Detects workflow failures and inefficient patterns then files GitHub issues. Workflow Monitor is an agent skill from athola/claude-night-market. Detects workflow failures and inefficient patterns then files GitHub issues.

When should I use Workflow Monitor?

Workflow Monitor fits situations like: A workflow step repeatedly fails; produces inconsistent output.

How do I install Workflow Monitor in Claude Code?

Run `npx skills add athola/claude-night-market --skill workflow-monitor -a claude-code`. Or copy the skill folder (plugins/imbue/skills/workflow-monitor in athola/claude-night-market) into .claude/skills/workflow-monitor in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Monitor in Codex?

Run `npx skills add athola/claude-night-market --skill workflow-monitor -a codex`. Or copy the skill folder (plugins/imbue/skills/workflow-monitor in athola/claude-night-market) into .agents/skills/workflow-monitor in your project. Codex loads it when a task matches its description.

Can I use Workflow Monitor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add athola/claude-night-market --skill workflow-monitor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-monitor, .gemini/skills/workflow-monitor, .github/skills/workflow-monitor and .opencode/skills/workflow-monitor in your project.

What does Workflow Monitor need to run?

Going by SKILL.md and its folder, Workflow Monitor needs the command-line tools its instructions call (gh). Our summary lists: Node.js.

Does Workflow Monitor access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Workflow Monitor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workflow Monitor use?

Workflow Monitor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Monitor use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workflow Monitor?

Skills that share tags, products or a category with Workflow Monitor: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Monitor?

athola (a GitHub user) maintains it in athola/claude-night-market, which has 341 GitHub stars. The repository holds 152 skills in this directory. The repository was last updated on October 9, 2026.

Source: athola/claude-night-market on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.