run-status

Read state.yaml and summarize active run metrics into a readable report.

3|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/4tikhonov/the-minority-report --skill run-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-status
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/builder/skills/run-status
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill run-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams monitor long-running automation by providing a concise, real-time report of the active run, including progress, timing, and recent changes.

Core Features & Use Cases

  • Real-time Run Overview: Display the active run's title, intent, mode, start time, and elapsed duration.
  • Progress & Changes: Show completed and pending steps, a dynamic status marker, number of files changed, and a recent activity log.
  • Use Case: Use this Skill in CI/CD pipelines or data pipelines to quickly verify where a run stands and what changed last.

Quick Start

Ask the system to display the current run status. Example:

  • orchestrator run-status
  • If integrated into a dashboard, press "Refresh Run Status"

Frequently Asked Questions about run-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor long-running automation pipeline progress in real-time?

To monitor long-running automation, you can use a status reporting tool that reads a state.yaml file to summarize active run metrics, elapsed duration, and recent changes into a readable overview.

What is the best way to track CI task status and recent file changes during an active run?

Tracking CI task status involves extracting the run-id, progress indicators, and files changed from a state configuration file, then presenting them as a concise report to verify where the run stands.

How do I display the current run status and elapsed time for data pipelines?

Displaying current run status requires reading the active run's state.yaml file to extract the start time, elapsed duration, and completed steps, summarizing them into a quick visual overview.

Can I view recent activity logs and pending steps for automation workflows without external dependencies?

Viewing recent activity logs and pending steps is possible by reading the state.yaml file directly to summarize the run's recent changes and progress indicators without requiring external dependencies.

Does this run status monitoring approach work for debugging experiments and data pipelines?

Run status monitoring works for debugging experiments and data pipelines by providing visibility into the active run's title, intent, mode, and recent activity, which is essential for identifying pipeline issues.