Agent skill

Proof Trace Summarizer

by ArabelaTso in ArabelaTso/Skills-4-SE

Summarize long Isabelle or Coq proof scripts into high-level logical steps and reasoning flow.

Apache-2.0Auto-check passed

Install Proof Trace Summarizer

skills CLI
$ npx skills add ArabelaTso/Skills-4-SE --skill proof-trace-summarizer -a claude-code

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

GitHub CLI
$ gh skill install ArabelaTso/Skills-4-SE proof-trace-summarizer --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/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/proof-trace-summarizer .claude/skills/proof-trace-summarizer && 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
proof-trace-summarizer
GitHub stars
253
Token cost
~2.4k tokens
SKILL.md length
614 words
Files
3 (incl. references)
Skills in repo
170
Repo updated
First seen
Licence
Apache-2.0

At a glance

Summarize long Isabelle or Coq proof scripts into high-level logical steps and reasoning flow.

  • Works in 5 steps: Identify Proof Structure → Extract Major Components → Group Related Steps → …
  • Understand the structure of a complex proof
  • SKILL.md covers Overview, How to Use, Summarization Workflow and Example: Isabelle Induction…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Proof Trace Summarizer is an agent skill from ArabelaTso/Skills-4-SE. Summarize long Isabelle or Coq proof scripts into high-level logical steps and reasoning flow. Use when users need to: (1) Understand the structure of a complex proof, (2) Document proof strategies for others, (3) Extract the key reasoning steps from verbose proof scripts, (4) Create readable proof outlines from detailed tactical proofs. Produces hierarchical outlines with moderate detail showing proof structure, main cases, key lemmas, and reasoning flow for both Isabelle/Isar and Coq proofs.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/summarization_patterns.md` and `references/tactic_interpretation.md`).

The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.

When your agent uses it

  • Understand the structure of a complex proof
  • Document proof strategies for others
  • Extract the key reasoning steps from verbose proof scripts
  • Create readable proof outlines from detailed tactical proofs

Example prompts

  • “/proof-trace-summarizer”

Workflow steps

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

  1. Identify Proof Structure
  2. Extract Major Components
  3. Group Related Steps
  4. Create Hierarchical Outline
  5. Add Moderate Detail

What it can do on your machine

Read from SKILL.md and the folder at commit 4f38503. 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 isabelle and coq).

    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

Proof Trace Summarizer loads about 2.4k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 614 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.5k

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 ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 614 words, ~2,358 tokens.

Download SKILL.mdSave it as .claude/skills/proof-trace-summarizer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
proof-trace-summarizer
description
Summarize long Isabelle or Coq proof scripts into high-level logical steps and reasoning flow. Use when users need to: (1) Understand the structure of a complex proof, (2) Document proof strategies for others, (3) Extract the key reasoning steps from verbose proof scripts, (4) Create readable proof outlines from detailed tactical proofs. Produces hierarchical outlines with moderate detail showing proof structure, main cases, key lemmas, and reasoning flow for both Isabelle/Isar and Coq proofs.

Proof Trace Summarizer

Summarize long proof scripts into high-level logical steps and reasoning flow.

Overview

This skill transforms verbose Isabelle or Coq proof scripts into clear, hierarchical summaries that capture the essential reasoning structure. It identifies proof patterns (induction, case analysis, equational reasoning), extracts key steps, and presents them in a readable outline format.

How to Use

Provide a proof script with:

  1. System: Isabelle or Coq
  2. Proof script: The complete proof to summarize
  3. Context (optional): Theorem statement, definitions, or background

The skill will produce a hierarchical outline showing:

  • Main proof strategy
  • Case structure (if applicable)
  • Key reasoning steps
  • Important lemmas or facts used

Summarization Workflow

Step 1: Identify Proof Structure

Recognize the high-level proof pattern:

Induction proof: Look for proof (induction ...) (Isabelle) or induction ... as [|...] (Coq)

Case analysis: Look for proof (cases ...) (Isabelle) or destruct ... as [...] (Coq)

Direct proof: Sequential reasoning without major branching

Equational reasoning: Chain of rewrites or calculations

Hybrid: Combination of patterns

Step 2: Extract Major Components

Identify the key structural elements:

  • Base cases: Initial cases in induction or case analysis
  • Inductive cases: Recursive cases with induction hypotheses
  • Subgoals: Intermediate facts or lemmas
  • Key tactics: Non-trivial reasoning steps
  • Automation: Where automatic methods are used

Combine sequences of tactics into logical units:

  • Multiple simplification steps → "Simplification proves..."
  • Rewrite sequences → "Rewriting chain: ..."
  • Automation → "Automatic proof handles..."
Step 4: Create Hierarchical Outline

Structure the summary as a tree:

Main theorem: <statement>
├─ Proof strategy: <induction/cases/direct>
├─ Case 1: <description>
│  ├─ Subgoal 1.1: <description>
│  │  └─ <how proven>
│  └─ Subgoal 1.2: <description>
│     └─ <how proven>
└─ Case 2: <description>
   └─ <how proven>
Step 5: Add Moderate Detail

For each step, include:

  • What is being proven
  • How it's proven (key tactic or method)
  • Why it works (if non-obvious)

Omit:

  • Routine simplification details
  • Obvious arithmetic steps
  • Repetitive patterns

Example: Isabelle Induction Proof

Input proof script:

isabelle
lemma rev_rev: "rev (rev xs) = xs"
proof (induction xs)
  case Nil
  show ?case by simp
next
  case (Cons x xs)
  have "rev (rev (x # xs)) = rev (rev xs @ [x])" by simp
  also have "... = rev [x] @ rev (rev xs)" by simp
  also have "... = [x] @ xs" using Cons.IH by simp
  also have "... = x # xs" by simp
  finally show ?case .
qed

Output summary:

Theorem: rev (rev xs) = xs
Proof by induction on xs

├─ Base case: xs = []
│  └─ Simplification: rev (rev []) = rev [] = []
│
└─ Inductive case: xs = x # xs'
   ├─ IH: rev (rev xs') = xs'
   └─ Equational reasoning:
      ├─ rev (rev (x # xs')) = rev (rev xs' @ [x])  (definition of rev)
      ├─ = rev [x] @ rev (rev xs')                   (rev distributes)
      ├─ = [x] @ xs'                                  (apply IH)
      └─ = x # xs'                                    (list notation)

Example: Coq Case Analysis

Input proof script:

coq
Theorem option_map_Some : forall (A B : Type) (f : A -> B) (x : option A) (y : B),
  option_map f x = Some y -> exists z, x = Some z /\ f z = y.
Proof.
  intros A B f x y H.
  destruct x as [z|].
  - simpl in H. injection H as H. exists z. split.
    + reflexivity.
    + exact H.
  - simpl in H. discriminate H.
Qed.

Output summary:

Theorem: option_map f x = Some y → ∃z. x = Some z ∧ f z = y
Proof by case analysis on x

├─ Case: x = Some z
│  ├─ Simplify: option_map f (Some z) = Some (f z)
│  ├─ Extract: f z = y from Some (f z) = Some y
│  └─ Witness: z satisfies x = Some z and f z = y
│
└─ Case: x = None
   └─ Contradiction: option_map f None = None ≠ Some y

Example: Complex Nested Proof

Input proof script:

isabelle
lemma sorted_append:
  assumes "sorted xs" "sorted ys" "∀x∈set xs. ∀y∈set ys. x ≤ y"
  shows "sorted (xs @ ys)"
using assms
proof (induction xs)
  case Nil
  then show ?case by simp
next
  case (Cons x xs)
  then have "sorted xs" and "sorted ys" by auto
  moreover have "∀z∈set xs. ∀y∈set ys. z ≤ y" using Cons.prems by auto
  ultimately have "sorted (xs @ ys)" using Cons.IH by simp
  moreover have "∀z∈set (xs @ ys). x ≤ z"
  proof -
    have "∀z∈set xs. x ≤ z" using Cons.prems by auto
    moreover have "∀z∈set ys. x ≤ z" using Cons.prems by auto
    ultimately show ?thesis by auto
  qed
  ultimately show ?case by (simp add: sorted_Cons)
qed

Output summary:

Theorem: sorted xs ∧ sorted ys ∧ (∀x∈xs. ∀y∈ys. x ≤ y) → sorted (xs @ ys)
Proof by induction on xs

├─ Base case: xs = []
│  └─ Simplification: sorted ([] @ ys) = sorted ys (given)
│
└─ Inductive case: xs = x # xs'
   ├─ IH: sorted xs' ∧ sorted ys ∧ (∀z∈xs'. ∀y∈ys. z ≤ y) → sorted (xs' @ ys)
   ├─ Apply IH: sorted (xs' @ ys)
   │  └─ Verified: xs' sorted, ys sorted, ordering holds
   ├─ Prove: x ≤ all elements in (xs' @ ys)
   │  ├─ x ≤ all in xs' (from sorted (x # xs'))
   │  └─ x ≤ all in ys (from assumption)
   └─ Conclusion: sorted (x # (xs' @ ys)) by sorted_Cons lemma

Common Proof Patterns

Pattern: Proof by Simplification

Indicators: by simp, by auto, reflexivity., auto.

Summary format:

Direct proof by [method]
└─ [Brief description of what automation handles]
Pattern: Proof by Induction

Indicators: proof (induction ...), induction ... as [|...]

Summary format:

Proof by induction on <var>
├─ Base case: <var> = <base>
│  └─ <proof method>
└─ Inductive case: <var> = <constructor> <subterm>
   ├─ IH: <hypothesis>
   └─ <how IH is used>
Pattern: Proof by Case Analysis

Indicators: proof (cases ...), destruct ... as [...]

Summary format:

Proof by case analysis on <var>
├─ Case: <var> = <value1>
│  └─ <proof method>
└─ Case: <var> = <value2>
   └─ <proof method>
Pattern: Equational Reasoning

Indicators: also ... finally, multiple rewrite steps

Summary format:

Equational reasoning
├─ Start: <expr1>
├─ = <expr2> (<justification>)
├─ = <expr3> (<justification>)
└─ = <goal>
Pattern: Lemma Application

Indicators: by (rule lemma), apply lemma.

Summary format:

Apply lemma <name>
├─ Lemma: <statement>
└─ Instantiation: <parameters>

Handling Different Proof Lengths

Short Proofs (< 10 lines)

Provide a brief summary:

Proof: <one-line description of method>
Show full SKILL.md (244 more words)Show less
Medium Proofs (10-50 lines)

Use hierarchical outline with 2-3 levels:

Main strategy
├─ Step 1
└─ Step 2
Long Proofs (> 50 lines)

Use full hierarchical outline with:

  • Main structure (top level)
  • Major cases or subgoals (second level)
  • Key reasoning steps (third level)
  • Omit routine details

Quality Guidelines

Good Summary Characteristics

✓ Clear structure: Hierarchical outline shows proof organization ✓ Appropriate detail: Captures key steps, omits routine ones ✓ Readable: Uses natural language, not just tactic names ✓ Accurate: Faithfully represents the proof logic ✓ Informative: Highlights non-obvious reasoning

What to Include
  • Main proof strategy (induction, cases, direct, equational)
  • Case structure and how each case is resolved
  • Key lemmas or theorems applied
  • Non-obvious reasoning steps
  • Induction hypotheses and how they're used
  • Important intermediate facts
What to Omit
  • Routine simplification (by simp, reflexivity.)
  • Obvious arithmetic
  • Trivial case analysis
  • Repetitive patterns
  • Low-level tactic details
  • Proof management commands (next, qed, etc.)

References

Detailed guides for proof analysis:

Load these references when:

  • Encountering unfamiliar proof patterns
  • Need detailed tactic interpretation
  • Working with complex nested proofs
  • Unsure how to structure the summary

Tips

  1. Start with structure: Identify the main proof pattern first
  2. Group related steps: Combine sequences into logical units
  3. Use hierarchy: Indent to show proof structure clearly
  4. Be selective: Include key steps, omit routine ones
  5. Natural language: Describe reasoning, not just tactics
  6. Preserve logic: Ensure summary accurately reflects proof flow
  7. Highlight insights: Give more detail to non-obvious steps

© ArabelaTso, 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

SKILL.md and 2 other files (references) in skills/proof-trace-summarizer of ArabelaTso/Skills-4-SE.

  • SKILL.md
  • references/summarization_patterns.md
  • references/tactic_interpretation.md

Open the folder on GitHubat commit 4f38503

Compare with similar skills

Proof Trace Summarizer 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.

Proof Trace Summarizer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Proof Trace Summarizer this skillArabelaTso/Skills-4-SE253—~2.4kAutomated safety check: PassApache-2.0
Summarizeopenclaw/openclaw392k1 repos~531Automated safety check: PassMIT
Research Summarizeralirezarezvani/claude-skills28k1 repos~2.7kAutomated safety check: PassMIT
Proof Videoopenclaw/openclaw392k—~2.4kAutomated safety check: PassMIT
Observe Traceruvnet/ruflo74k—~522Automated safety check: NotesMIT
Hacker News Summarizerykdojo/claude-code-tips10k—~942Automated safety check: PassCustom licence

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
  • Proof Video

    openclaw/openclaw

    Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

    392k GitHub stars~2.4k tokensUpdated today
    Media & CreativeAuto-check passed
  • Observe Trace

    ruvnet/ruflo

    Trace agent execution by collecting spans and building a trace tree for a task

    74k GitHub stars~522 tokensUpdated yesterday
    Auto-check: notes
  • 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 16 days ago
    Writing & ContentAuto-check passed
  • Trace

    zereight/gitlab-mcp

    Evidence-driven tracing with competing hypotheses in parallel.

    2k GitHub starsUsed in 1 repo~412 tokens
    DevelopmentAuto-check passed

More from ArabelaTso/Skills-4-SE

All 170 skills in this repo
  • Framework Migration Assistant

    ArabelaTso/Skills-4-SE

    Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).

    253 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Metamorphic Test Generator

    ArabelaTso/Skills-4-SE

    Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.

    253 GitHub stars~798 tokensUpdated 1 mo ago
    Auto-check passed
  • Reproduction Trace Instrumenter

    ArabelaTso/Skills-4-SE

    Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.

    253 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Spring Mvc To Boot Migrator

    ArabelaTso/Skills-4-SE

    Automatically migrate Spring MVC applications to Spring Boot.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • State Snapshot Instrumenter

    ArabelaTso/Skills-4-SE

    Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Proof Trace Summarizer

What does Proof Trace Summarizer do?

Summarize long Isabelle or Coq proof scripts into high-level logical steps and reasoning flow. Proof Trace Summarizer is an agent skill from ArabelaTso/Skills-4-SE. Summarize long Isabelle or Coq proof scripts into high-level logical steps and reasoning flow.

When should I use Proof Trace Summarizer?

Proof Trace Summarizer fits situations like: understand the structure of a complex proof; document proof strategies for others; extract the key reasoning steps from verbose proof scripts; create readable proof outlines from detailed tactical proofs.

How do I install Proof Trace Summarizer in Claude Code?

Run `npx skills add ArabelaTso/Skills-4-SE --skill proof-trace-summarizer -a claude-code`. Or copy the skill folder (skills/proof-trace-summarizer in ArabelaTso/Skills-4-SE) into .claude/skills/proof-trace-summarizer in your project. Claude Code loads it when a task matches its description.

How do I install Proof Trace Summarizer in Codex?

Run `npx skills add ArabelaTso/Skills-4-SE --skill proof-trace-summarizer -a codex`. Or copy the skill folder (skills/proof-trace-summarizer in ArabelaTso/Skills-4-SE) into .agents/skills/proof-trace-summarizer in your project. Codex loads it when a task matches its description.

Can I use Proof Trace Summarizer 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 ArabelaTso/Skills-4-SE --skill proof-trace-summarizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/proof-trace-summarizer, .gemini/skills/proof-trace-summarizer, .github/skills/proof-trace-summarizer and .opencode/skills/proof-trace-summarizer in your project.

What does Proof Trace Summarizer need to run?

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

Does Proof Trace Summarizer 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 Proof Trace Summarizer 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 Proof Trace Summarizer use?

Proof Trace Summarizer 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 Proof Trace Summarizer use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.

What are the alternatives to Proof Trace Summarizer?

Skills that share tags, products or a category with Proof Trace Summarizer: Summarize (openclaw/openclaw, 392k stars), Research Summarizer (alirezarezvani/claude-skills, 28k stars), Proof Video (openclaw/openclaw, 392k stars) and Observe Trace (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Proof Trace Summarizer?

ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 170 skills in this directory. The repository was last updated on August 21, 2026.

Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.