runs-derive

Count and extract data from .runs artifacts using deterministic read-only processing.

5|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill runs-derive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runs-derive
Source: https://github.com/EffortlessMetrics/demo-swarm/tree/main/.claude/skills/runs-derive
Command: npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill runs-derive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the complex and error-prone task of extracting specific data points from diverse .runs/ artifacts (Markdown, JSON, YAML) for auditing, reporting, or automated decision-making. It replaces manual grep/wc pipelines with deterministic, null-safe operations.

Core Features & Use Cases

  • Deterministic Extraction: Provides reliable counting (e.g., requirements, BDD scenarios, open questions) and field extraction from JSON receipts, YAML blocks, and Machine Summary sections.
  • Read-Only Operations: Ensures data integrity and auditability by strictly reading artifacts, never modifying them.
  • Unified & Simplified Interface: Offers a consistent, shimmed command-line interface for various parsing tasks, abstracting away underlying complexity.
  • Use Case: After a "Signal" flow, use this skill to quickly count the number of functional requirements (REQ- markers) and open questions (QID- markers) from the generated requirements.md and open_questions.md files, providing a precise summary for review and subsequent flows.

Quick Start

Use the runs-derive skill to count all lines starting with '### REQ-' in the file '.runs/my-feature/signal/requirements.md', returning the count.

Frequently Asked Questions about runs-derive

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

FAQPage Schema
How do I extract and count specific markers from .runs artifacts?

runs-derive extracts data from .runs artifacts using deterministic, read-only processing. It counts markers like REQ- or QID- and extracts fields from JSON receipts and YAML blocks, returning precise scalar values for auditing and reporting.

Can I use this to automate data extraction from Markdown, JSON, and YAML files?

Yes. runs-derive provides a unified command-line interface that abstracts parsing complexity across multiple formats. It deterministically extracts counts and field values without modifying source artifacts, making it suitable for cleanup automation and decision pipelines.

What's the best way to count requirements and open questions from generated documentation?

runs-derive counts all lines matching patterns (e.g., '### REQ-') in documentation files like requirements.md and open_questions.md, returning a single count. This replaces manual grep/wc pipelines with null-safe, reliable operations for precise summaries.

Does runs-derive modify the artifacts it processes?

No. runs-derive is strictly read-only, ensuring data integrity and auditability. It extracts mechanical counts, field values, and summaries from .runs artifacts without altering the source files.

Can I use runs-derive for auditing and automated decision-making?

Yes. runs-derive emits scalar values or null per run, making outputs suitable for auditing logs, reporting dashboards, and triggering downstream automation based on extracted metrics and marker tallies.