ralph-monitor
Monitor and report on Ralph Wiggum loop progress. Provides real-time status, iteration summaries, and progress tracking via Archon state. Use to check on running or completed loops, view iteration history, and diagnose issues.
Best use case
ralph-monitor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Monitor and report on Ralph Wiggum loop progress. Provides real-time status, iteration summaries, and progress tracking via Archon state. Use to check on running or completed loops, view iteration history, and diagnose issues.
Teams using ralph-monitor should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ralph-monitor/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ralph-monitor Compares
| Feature / Agent | ralph-monitor | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Monitor and report on Ralph Wiggum loop progress. Provides real-time status, iteration summaries, and progress tracking via Archon state. Use to check on running or completed loops, view iteration history, and diagnose issues.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Ralph Monitor Skill
Monitor and report on Ralph Wiggum loop status and progress. Provides visibility into active and completed loops via Archon state.
## Triggers
Use this skill when:
- Checking Ralph loop status
- Viewing iteration progress
- Monitoring running loops
- Reviewing loop history
- Diagnosing stuck loops
- Keywords: ralph status, loop status, ralph monitor, check loop, iteration progress, loop history
## Core Mission
Query Archon and local state to provide comprehensive status reports on Ralph loops.
---
## Status Report Formats
### Active Loop Status
```markdown
## Ralph Loop Status
### Loop Information
| Property | Value |
|----------|-------|
| Loop ID | [LOOP_ID] |
| Status | Running / Paused / Stopped |
| Started | [TIMESTAMP] |
| Duration | [HH:MM:SS] |
### Progress
| Metric | Current | Target |
|--------|---------|--------|
| Iteration | [N] | [MAX] |
| Tasks | [DONE] | [TOTAL] |
| Tests Passing | [PASS] | [TOTAL] |
[====================----------] 67% complete
### Current Iteration
| Property | Value |
|----------|-------|
| Iteration | [N] |
| Started | [TIME] |
| Focus | [Current work summary] |
### Recent Activity
| Iter | Time | Summary | Files | Tests |
|------|------|---------|-------|-------|
| N | 5m ago | [Summary] | 3 | 15/15 |
| N-1 | 12m ago | [Summary] | 5 | 14/15 |
| N-2 | 20m ago | [Summary] | 2 | 10/15 |
### Validation Status
- Build: Passing
- Tests: 15/15 passing
- Lint: 2 warnings
### Archon Integration
- Project: [PROJECT_NAME] ([PROJECT_ID])
- Task: [TASK_TITLE] ([TASK_ID])
- Task Status: doing
- State Doc: [DOC_ID]
### Commands
- View full log: `cat .ralph/loop.log`
- Cancel loop: Use ralph-loop skill with cancel mode
- View prompt: `cat .ralph/prompts/current.md`
```
---
## Data Collection
### From Archon
```python
# Get state document
state_docs = find_documents(
project_id=PROJECT_ID,
query="Ralph Loop State"
)
# Get active loops
active_loops = [
doc for doc in state_docs
if doc["content"]["status"] == "running"
]
# Get associated tasks
for loop in active_loops:
task = find_tasks(task_id=loop["content"]["task_id"])
loop["task"] = task
```
### From Local State
```bash
# Read config
cat .ralph/config.json
# Read recent log
tail -100 .ralph/loop.log
# Git status
git --no-pager log --oneline -5
git status --short
```
---
## Report Types
### Quick Status
Returns brief one-liner:
```
Ralph: Iteration 12/50 | 67% | Tests 15/15 | Duration 25m
```
### Full Status
Returns complete report as shown above.
### History Report
```markdown
## Ralph Loop History
### Completed Loops
| Loop ID | Task | Iterations | Duration | Status |
|---------|------|------------|----------|--------|
| ralph-20260122-150000 | Auth API | 12 | 45m | Complete |
| ralph-20260121-100000 | DB Schema | 8 | 30m | Complete |
| ralph-20260120-140000 | User Model | 25 | 1h 20m | Max reached |
### Statistics
| Metric | Value |
|--------|-------|
| Total Loops | 15 |
| Completed | 12 (80%) |
| Blocked | 2 (13%) |
| Max Reached | 1 (7%) |
| Avg Iterations | 14 |
| Avg Duration | 35m |
```
### Comparison Report
```markdown
## Loop Comparison
| Metric | loop1 | loop2 |
|--------|-------|-------|
| Task | Auth API | User API |
| Iterations | 12 | 18 |
| Duration | 45m | 1h 10m |
| Files Changed | 24 | 31 |
| Tests Added | 15 | 22 |
| Status | Complete | Complete |
```
---
## Progress Visualization
### Iteration Timeline
```
Iteration Progress
==================
1 #### Setup
2 ######## Basic impl
3 ############ Tests added
4 ###### Bug fix
5 ################ Feature complete
6 #### Refactor
7 ########## Edge cases
8 #################### Validation
9 ###### Polish
10 ######################## Complete
Legend: #### = Work done, length = files changed
```
### Test Progress
```
Test Progress Across Iterations
===============================
Iter 1: [ ] 0/0
Iter 2: [### ] 5/15
Iter 3: [##### ] 8/15
Iter 4: [###### ] 10/15
Iter 5: [######## ] 12/15
Iter 6: [######## ] 12/15 <- regression
Iter 7: [##########] 15/15 PASS
```
---
## Alerts and Warnings
### Stuck Detection
```markdown
## Potential Issue Detected
### Stuck Pattern
The loop appears to be stuck:
- Last 3 iterations made no test progress
- Same files being modified repeatedly
- Similar error messages in output
### Recommendation
Consider:
1. Reviewing the prompt for clarity
2. Breaking the task into smaller pieces
3. Adding more specific validation criteria
4. Canceling and debugging manually
### Action
- Continue monitoring
- Cancel loop if needed
- Review logs: `cat .ralph/loop.log | tail -500`
```
### Resource Warning
```markdown
## Resource Warning
### Issue
- Token usage high in recent iterations
- Approaching context limit
### Recommendation
- Consider checkpointing
- May need to restart with fresh context
- Current work is saved in Archon
```
---
## Troubleshooting Commands
### Check Configuration
```markdown
## Configuration Check
### Files
- [x] .ralph/config.json exists
- [x] .ralph/prompts/current.md exists
- [x] .ralph/loop-state.json exists
### Archon Connection
- [x] Project found: [PROJECT_NAME]
- [x] Task found: [TASK_TITLE]
- [x] State document found
### Validation Commands
- [x] Build: `npm run build` (verified)
- [x] Test: `npm test` (verified)
- [ ] Lint: `npm run lint` (not configured)
### All checks passed
```
---
## Usage Examples
### Check Current Status
```python
# Quick check
"What's the Ralph loop status?"
# Full details
"Show me detailed Ralph loop status"
```
### View History
```python
# All loops
"Show Ralph loop history"
# Specific loop
"Show details for ralph-20260122-150000"
```
### Diagnose Issues
```python
# Check for problems
"Is the Ralph loop stuck?"
# View recent iterations
"Show last 5 Ralph iterations"
```
---
## Integration with Other Skills
### With ralph-loop Skill
```python
# If monitoring shows issues, suggest:
"Use ralph-loop skill to cancel or resume"
```
### With archon-workflow Skill
```python
# For task management integration:
"Use archon-workflow to update task status"
```
---
## Best Practices
1. **Regular Monitoring**: Check status periodically for long loops
2. **Watch for Patterns**: Same files modified repeatedly = potential issue
3. **Test Progress**: Should generally increase each iteration
4. **Duration Tracking**: Unusually long iterations may indicate problems
5. **Archon Sync**: Ensure state is properly saved to Archon
6. **Log Review**: Check loop.log for detailed error messagesRelated Skills
u2017-tool-health-monitoring-for-personal-finance-management
Operate the "tool health monitoring for personal finance management" capability in production for tool health monitoring for personal finance management workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
ralph-prompt-builder
Master orchestrator for generating Ralph Wiggum-compatible prompts. Analyzes task requirements and routes to appropriate generator (single-task, multi-task, project, or research). Use when you need to create any Ralph loop prompt and want automatic selection of the right generator.
ralph
Run RALPH autonomous development loop. Converts PRD markdown to prd.json and runs autonomous implementation.
project-aeo-monitoring-tools
Build custom AI search monitoring tools for competitive AEO analysis. Covers API access, scraping architecture, legal compliance, and cost estimation.
sdd-to-ralph
This skill should be used when the user wants to convert completed CCSDD specs into Ralph execution artifacts. Use when user says "bridge spec to ralph", "convert sdd to ralph", "sdd to ralph", "generate ralph from spec", "prepare spec for ralph", or wants to take a cc-sdd feature spec and run it through Ralph for autonomous implementation.
prometheus-monitoring
Set up Prometheus monitoring for applications with custom metrics, scraping configurations, and service discovery. Use when implementing time-series metrics collection, monitoring applications, or building observability infrastructure.
pipeline-monitor
Track build success rates and identify flaky tests from CI logs
operational-sla-monitoring
Track, analyze, and explain operational SLA performance for banking operations functions. Use when monitoring SLA compliance, investigating SLA breaches, producing SLA performance reports, or optimizing service level targets for payment processing, account servicing, lending operations, and customer service functions.
observability-monitoring-slo-implement
You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that ba...
observability-monitoring-observability-engineer
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability. Use when: the task directly matches observability engineer responsibilities within plugin observability-monitoring. Do not use when: a more specific framework or task-focused skill is clearly a better match.
observability-monitoring-monitor-setup
You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da
monitoring
Set up observability for applications and infrastructure with metrics, logs, traces, and alerts.