| name | summarize_run |
| description | Use this skill to generate or revise a run summary inside a completed run folder in a single research repo. It applies when the user wants a concise research summary written to `./runs/<run_id>/summary.md` using logs, artifacts, selected figures, tables, and optional user comments. |
| metadata | {"short-description":"Summarize a completed run"} |
Summarize Run
Use this skill when the user asks for a summary of a completed run.
Inputs
- A
run_id
- Relevant logs, outputs, and artifacts from
./runs/<run_id>/...
- Optional user comments
- Optional figure selections
Output
Write the summary to:
./runs/<run_id>/summary.md
Workflow Rules
- Use only information present in logs, artifacts, and user comments.
- Do not invent numbers. If a value is missing, write
not reported.
- Keep the summary concise and decision-oriented.
- Generate up to 6 tags.
- If the user does not select specific figures, include all relevant figures from the run folder and link them using paths relative to
./runs/<run_id>/summary.md.
- If no figures are used, omit the
## Key artifacts section.
- Copy whole tables into the markdown file without summarizing them.
- Do not change the
## Comments section when revising an existing summary.
Template
Use this template exactly:
---
run_id:
date:
status: valid # valid | failed | archived
tags: []
source_run_folder:
---
# RUN: <short descriptive title>
## Summary
Use 1-3 sentences to summarize the main question this run addresses and the key findings. Then provide more details about results, figures and tables.
## Comments
Leave this section for user comments and interpretations. Don't change this section automatically when revising the summary.