runs

List and inspect Rune workflow run artifacts for debugging and retry planning.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune --skill runs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runs
Source: https://github.com/vinhnxv/rune/tree/main/plugins/rune/skills/runs
Command: npx skills add https://github.com/vinhnxv/rune --skill runs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rune's runs skill provides quick access to per-agent workflow artifacts produced by Rune, speeding debugging and retry planning.

Core Features & Use Cases

  • List recent runs with agent counts and statuses to understand workflow health.
  • Show detailed information for a specific agent run, including inputs, outputs, and timing data.
  • Compute timing statistics across runs and surface failed or crashed agents for quick retry.
  • Access is read-only to artifacts; validations guard against invalid agent names and paths.

Quick Start

List the most recent runs with /rune:runs list to begin inspecting artifacts.

Frequently Asked Questions about runs

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

FAQPage Schema
How do I inspect per-agent workflow artifacts to debug a crashed agent?

You can inspect per-agent workflow artifacts to debug a crashed agent by listing recent runs and viewing specific agent inputs, outputs, and timing data from read-only files like meta.json and run-index.jsonl.

What is the best way to surface failed agents in a Rune workflow for retry?

The best way to surface failed agents in a Rune workflow for retry is to compute timing statistics across recent runs, which identifies and highlights agents that have crashed or failed execution.

How do I view timing statistics across multiple agent runs?

You view timing statistics across multiple agent runs by accessing read-only run artifacts, allowing you to aggregate execution data and assess overall workflow health and performance.

Can I use this approach to check the status of recent workflow runs?

Yes, you can use this approach to check recent workflow run statuses by listing recent runs with their corresponding agent counts and statuses to quickly understand workflow health.

Do I need write access to modify run-index.jsonl when debugging agent runs?

No, you do not need write access to modify run-index.jsonl when debugging agent runs because the process relies strictly on read-only access to workflow artifacts to ensure safe and structured outputs.

Why does validating agent names matter when inspecting workflow artifacts?

Validating agent names matters when inspecting workflow artifacts because it guards against invalid paths and ensures the system provides structured, safe outputs when accessing run data.