workflow-monitor
Detect workflow failures and inefficient patterns, then create GitHub issues for improvement via /fix-workflow
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/athola/nm-imbue-workflow-monitorNight Market Skill — ported from claude-night-market/imbue. For the full experience with agents, hooks, and commands, install the Claude Code plugin.
Table of Contents
- Philosophy
- Quick Start
- Detection Patterns
- Workflow
- Issue Template
- Configuration
- Guardrails
- Integration Points
- Output Format
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
# 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
| Pattern | Signal | Severity |
|---|---|---|
| Command failure | Exit code > 0 | High |
| Timeout | Exceeded timeout limit | High |
| Retry loop | Same command >3 times | Medium |
| Context exhaustion | >90% context used | Medium |
| Tool misuse | Wrong tool for task | Low |
Efficiency Detection
| Pattern | Signal | Threshold |
|---|---|---|
| Verbose output | >1000 lines from command | 500 lines recommended |
| Redundant reads | Same file read >2 times | 2 reads max |
| Sequential vs parallel | Independent tasks run sequentially | Should parallelize |
| Over-fetching | Read entire file when snippet needed | Use offset/limit |
Workflow
Phase 1: Capture (workflow-monitor:capture-complete)
- Log execution events - Commands, outputs, timing
- Tag anomalies - Failures, timeouts, inefficiencies
- Store evidence - For reproducibility
Phase 2: Analyze (workflow-monitor:analysis-complete)
- Classify issues - Error type, severity, scope
- Identify root cause - What triggered the issue
- Suggest fix - What would prevent recurrence
Phase 3: Report (workflow-monitor:report-generated)
- Generate issue body - Structured format
- Assign labels - workflow, bug, enhancement
- Link evidence - Command outputs, session info
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-athola-nm-imbue-workflow-monitor": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
extract
Analyze a codebase and build a knowledge base of business logic, architecture, data flow, and engineering patterns. The foundation for gauntlet challenges and agent integration
discourse
>- Scan community discussion channels (HN, Lobsters, Reddit, tech blogs) for experience reports and opinions on a topic
architecture-paradigm-hexagonal
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure
architecture-paradigm-microkernel
Microkernel architecture with a minimal core and plugin-based extensibility for platforms
escalation-governance
Assess whether to escalate models