Overview

Research Status monitors the health of the research service and surfaces recent findings. It helps you verify the service is running, track queue activity, and review past results for quick diagnostics and auditing.

How This Skill Works

The skill queries core endpoints such as /api/status, /api/tasks, /api/findings, and /api/sessions to assemble current health, activity, and findings. This data feeds a dashboard-like view that shows queue state, active sessions, and searchable findings with sources.

When to Use It

• Verify the research service is running
• See recent research activity
• Check queue status (queued, running, completed, failed)
• View past findings
• Inspect active sessions

Quick Start

1. Step 1: curl http://localhost:3200/api/status
2. Step 2: curl http://localhost:3200/api/tasks?limit=10 && curl http://localhost:3200/api/findings?limit=10
3. Step 3: Open http://localhost:3200 to view the full dashboard

Best Practices

• Poll status and task endpoints at regular intervals during incidents
• Cross-check findings with sources before reporting
• Use limit parameters (e.g., ?limit=10) to keep responses concise
• Monitor the dashboard for real-time updates
• Document any anomalies with a timestamp and source

Example Use Cases

• During deployment, verify the service is up using /api/status and confirm no backlog via /api/tasks
• After a long-running task, fetch /api/tasks?limit=10 and /api/findings?limit=10 to review progress
• Diagnose backlog by checking queue states (queued, running, completed, failed) on the dashboard
• Audit findings with sources by querying /api/findings?limit=10 and inspecting corresponding sources
• Identify orphan sessions by listing active sessions via /api/sessions and cross-referencing with recent activity

Frequently Asked Questions