Agent skill

Run Summary

by adrianco in adrianco/retort

Summarize the architecture of code generated by a single retort run.

Apache-2.0Auto-check passed

Install Run Summary

skills CLI
$ npx skills add adrianco/retort --skill run-summary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install adrianco/retort run-summary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/adrianco/retort.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/run-summary .claude/skills/run-summary && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-summary
GitHub stars
207
Token cost
~1.3k tokens
SKILL.md length
411 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Summarize the architecture of code generated by a single retort run.

  • Works in 4 steps: Infer the surface → Map the modules → Describe the interfaces → …
  • SKILL.md covers Overview, Parameters, Steps and Constraints Summary, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Run Summary is an agent skill from adrianco/retort. Summarize the architecture of code generated by a single retort run. Produces module-level structure, interfaces, and control flow in a form suitable for cross-run comparison — not a full codebase-summary.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Platform Evolution Engine. Distill the best from the combinatorial mess. The licence is Apache-2.0.

Example prompts

  • “/run-summary”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Infer the surface
  2. Map the modules
  3. Describe the interfaces
  4. Trace the dominant control flow

What it can do on your machine

Read from SKILL.md and the folder at commit 1f75769. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Summary loads about 1.3k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 411 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from adrianco/retort at commit 1f75769, republished under its Apache-2.0 licence (© adrianco). 411 words, ~1,309 tokens.

Download SKILL.mdSave it as .claude/skills/run-summary/SKILL.md (or your agent's skills folder).
name
run-summary
description
Summarize the architecture of code generated by a single retort run. Produces module-level structure, interfaces, and control flow in a form suitable for cross-run comparison — not a full codebase-summary.
type
anthropic-skill
version
1.0

Run Summary

Overview

Retort runs produce small, single-task codebases (one REST API, one CLI, one service). Full codebase-summary treatment is overkill — but a consistent lightweight summary per run is exactly what makes cross-run comparison useful.

This skill is an intentionally scoped-down adaptation of pourpoise's codebase-summary. It runs in seconds, not minutes, and emits only what's useful when comparing 48+ small generated projects.

Parameters

  • codebase_path (required): The run directory (same as evaluate-run's run_dir)
  • output_dir (optional, default: {codebase_path}/summary): Where to write the summary files

Steps

1. Infer the surface

Read TASK.md to understand what the code is supposed to do — the "surface" of the project. One paragraph, no judgments.

2. Map the modules

Generate {output_dir}/modules.md:

markdown
# Modules

| Path | Purpose | Entry points |
|------|---------|--------------|
| src/app.py | HTTP server, route handlers | `app`, `create_app()` |
| src/models.py | SQLAlchemy models | `Book`, `Base` |
| src/db.py | Connection + migrations | `get_engine()` |
| tests/test_app.py | API integration tests | 8 test functions |

Constraints:

  • You MUST list every non-generated source file (skip node_modules, target, __pycache__, .git, lock files, build artifacts).
  • The "Purpose" column is one line extracted from the code, not invented.
  • The "Entry points" column is the publicly-named functions, classes, or exported symbols — not every local helper.
3. Describe the interfaces

Generate {output_dir}/interfaces.md covering what the code exposes:

  • HTTP routes (method, path, short description)
  • CLI commands (subcommand + flags)
  • Library API (exported classes/functions)
  • Data schemas (tables, message formats)

Example:

markdown
# Interfaces

## HTTP routes

| Method | Path | Returns | Handler |
|--------|------|---------|---------|
| GET | /books | `[Book]` | `app.py:list_books` |
| POST | /books | `Book` | `app.py:create_book` |
| GET | /books/{id} | `Book \| 404` | `app.py:get_book` |

## Data schema

`books` table: id (int, pk), title (str), author (str), year (int).

Constraints:

  • You MUST grep / static-analyze the code rather than execute it to discover interfaces.
  • You MUST NOT invent endpoints the code doesn't actually declare.
  • If the code has none of the above categories, write (none) under that heading.
Show full SKILL.md (184 more words)Show less
4. Trace the dominant control flow

Generate {output_dir}/flow.md with one Mermaid diagram showing the happy-path request/response for the main feature, plus a one-paragraph narration.

markdown
# Flow

```mermaid
sequenceDiagram
    Client->>app.py: GET /books
    app.py->>db.py: get_session()
    db.py-->>app.py: Session
    app.py->>Book: query.all()
    Book-->>app.py: [Book]
    app.py-->>Client: 200 {json}

A request to GET /books opens a DB session via db.py:get_session(), queries all Book rows, and returns them as JSON. No pagination, no filtering.


Constraints:
- You MUST pick the single most representative flow — the one a user of the generated code would hit first.
- You MUST note deviations from common patterns ("no input validation", "no error handling", "synchronous DB access in async handler").
- The narration MUST be factual, not prescriptive.

### 5. Write the index

Generate `{output_dir}/index.md` linking to the other three files and giving a 3–4 bullet summary:

```markdown
# Summary: {cell_name} · rep {replicate}

- **Shape:** {one-line description — "Flask REST API with SQLAlchemy", "Go net/http CRUD with in-memory store", etc.}
- **Structure:** {n} modules, {n} test files
- **Interfaces:** {n} HTTP routes / {n} CLI commands / {n} exported functions
- **Notable:** {what stands out — simplest/most-complex approach seen, unusual library choice, etc.}

See [modules.md](modules.md), [interfaces.md](interfaces.md), [flow.md](flow.md).

Constraints Summary

  • You MUST finish in under 90 seconds wall-clock. This is the fast-path summary.
  • You MUST NOT read anything under node_modules/, target/, __pycache__/, .git/, dist/, build/.
  • You MUST write exactly four files: index.md, modules.md, interfaces.md, flow.md. No more, no less.
  • You MUST keep descriptions factual — no quality judgments (that's evaluate-run's job).
  • Output files MUST be valid markdown that renders correctly in GitHub's viewer (Mermaid in a ```mermaid fenced block).

Troubleshooting

Code is unparseable / generated output is garbage

  • Write the index.md with **Shape:** unparseable — agent output did not produce a valid project.
  • Leave the other files near-empty with a one-line explanation.
  • Exit 0 so evaluate-run can still complete.

Too many files to summarize

  • This shouldn't happen in retort's small-task workspaces. If it does, cap the modules table at 50 rows and note the truncation in index.md.

© adrianco, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/run-summary of adrianco/retort.

Open the folder on GitHubat commit 1f75769

Compare with similar skills

Run Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Summary compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Summary this skilladrianco/retort207—~1.3kAutomated safety check: PassApache-2.0
Summarizeopenclaw/openclaw392k1 repos~531Automated safety check: PassMIT
Research Summarizeralirezarezvani/claude-skills28k1 repos~2.7kAutomated safety check: PassMIT
Summarize Statuspaperclipai/paperclip99k—~2.2kAutomated safety check: PassMIT
Summarizerholaboss-ai/holaOS11k—~615Automated safety check: PassCustom licence
Summarize Meetingphuryn/pm-skills27k—~749Automated safety check: PassMIT

Similar skills

  • Summarize

    openclaw/openclaw

    Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.

    392k GitHub starsUsed in 1 repo~531 tokens
    Media & CreativeAuto-check passed
  • Research Summarizer

    alirezarezvani/claude-skills

    Structured research summarization agent skill for non-dev users.

    28k GitHub starsUsed in 1 repo~2.7k tokens
    Research & ScienceAuto-check passed
  • Summarize Status

    paperclipai/paperclip

    Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language…

    99k GitHub stars~2.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Summarizer

    holaboss-ai/holaOS

    Condense long articles, reports, and documents into clear, concise summaries.

    11k GitHub stars~615 tokensUpdated 1 mo ago
    Auto-check passed
  • Summarize Meeting

    phuryn/pm-skills

    Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.

    27k GitHub stars~749 tokensUpdated 24 days ago
    Productivity & AutomationAuto-check passed
  • Hacker News Summarizer

    ykdojo/claude-code-tips

    Fetches Hacker News top stories, a chosen story with its comment thread and the linked article through the official APIs, then summarizes them.

    10k GitHub stars~942 tokensUpdated 14 days ago
    Writing & ContentAuto-check passed

More from adrianco/retort

  • Compare Runs

    adrianco/retort

    Compare evaluated runs in a retort experiment along factor dimensions.

    207 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Diagnose Failed Run

    adrianco/retort

    Determine the TRUE cause of a failed retort run before attributing it.

    207 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Evaluate Run

    adrianco/retort

    Evaluate a single retort experiment run. An agent skill from adrianco/retort.

    207 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • File Run Issues

    adrianco/retort

    Aggregate a retort run's findings.jsonl into a machine-readable assessment.json summary with severity counts, penalty score, requirement coverage, and top findings.

    207 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Update Optimal Blog

    adrianco/retort

    Refresh the data tables in optimal-blog.md from master.db. An agent skill from adrianco/retort.

    207 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Questions about Run Summary

What does Run Summary do?

Summarize the architecture of code generated by a single retort run. Run Summary is an agent skill from adrianco/retort. Summarize the architecture of code generated by a single retort run.

How do I install Run Summary in Claude Code?

Run `npx skills add adrianco/retort --skill run-summary -a claude-code`. Or copy the skill folder (skills/run-summary in adrianco/retort) into .claude/skills/run-summary in your project. Claude Code loads it when a task matches its description.

How do I install Run Summary in Codex?

Run `npx skills add adrianco/retort --skill run-summary -a codex`. Or copy the skill folder (skills/run-summary in adrianco/retort) into .agents/skills/run-summary in your project. Codex loads it when a task matches its description.

Can I use Run Summary in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adrianco/retort --skill run-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-summary, .gemini/skills/run-summary, .github/skills/run-summary and .opencode/skills/run-summary in your project.

What does Run Summary need to run?

SKILL.md names no scripts, command-line tools or credentials: Run Summary is instructions for the agent only.

Does Run Summary access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Run Summary safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run Summary use?

Run Summary is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Summary use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Summary?

Skills that share tags, products or a category with Run Summary: Summarize (openclaw/openclaw, 392k stars), Research Summarizer (alirezarezvani/claude-skills, 28k stars), Summarize Status (paperclipai/paperclip, 99k stars) and Summarizer (holaboss-ai/holaOS, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Summary?

adrianco (a GitHub user) maintains it in adrianco/retort, which has 207 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

Source: adrianco/retort on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.