run-report-writer

Populate run report templates with execution evidence from logs and manifests.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill run-report-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-report-writer
Source: https://github.com/Centaurioun/osteogenesis_imperfecta/tree/main/.claude/skills/run-report-writer
Command: npx skills add https://github.com/Centaurioun/osteogenesis_imperfecta --skill run-report-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone process of assembling execution evidence into a consistent, auditable run report after a replication run. It guides the user to capture execution metadata, input validation results, generated outputs, QA gates, encountered issues, and a complete artifact inventory so that runs are reproducible and traceable.

Core Features & Use Cases

  • Manual template population: fill the CLAUDE_HANDOFF/RUN_REPORT_TEMPLATE.md using real logs, manifests, and artifacts from a completed run.
  • Operational checklist: enumerate execution metadata, input validation summaries, output counts, QA results, and issues encountered.
  • Archival practice: save the completed run_report.md in a dated run folder such as 03_outputs/reports/run_YYYYMMDD_HHMM to preserve reproducibility and audit trails.
  • Use case: after completing an analysis run, gather the run manifest JSON, execution logs, generated tables and figures, timing/environment details, and produce a consolidated run_report.md for collaborators and publication packages.

Quick Start

Use the run-report-writer to populate CLAUDE_HANDOFF/RUN_REPORT_TEMPLATE.md with evidence from the completed run and save the completed run_report.md into the run folder.

Frequently Asked Questions about run-report-writer

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

FAQPage Schema
How do I generate an audited run report from execution logs and manifests?

Populate the run report template with execution evidence extracted from run logs, manifests, and generated artifacts to produce a finalized run_report.md. This process captures metadata, validation results, and QA gates for auditable records.

What is a run report for reproducibility and quality assurance?

A run report for reproducibility is a consolidated record capturing execution metadata, input validation results, output counts, QA gates, and artifact inventories so that analysis runs remain traceable, auditable, and reproducible by collaborators.

What files do I need to create a reproducible run report?

You need a completed run folder containing a run manifest JSON, execution logs, output artifacts, timing and environment details, and the RUN_REPORT_TEMPLATE.md file to assemble a finalized, reproducible run report.

How do I archive run reports for publication packages?

Save the completed run_report.md into a dated run folder such as 03_outputs/reports/run_YYYYMMDD_HHMM to preserve reproducibility and audit trails. This archival practice ensures consolidated records are available for publication packages.

Can I use this run report writing process for post-execution replication workflows?

Yes, this run report writing process is applied to post-execution replication workflows to create audited, reproducible records for each dated run. It gathers manifests, execution logs, and generated tables into a consolidated markdown file.