Skip to content
Skills Library
AI & agents · Writing

report

/report

Write the final summary of an autoresearch run to `./.ar/final_report.md` — trajectory, best commit and its diff, what worked, what failed, and what to try next. Use for `/ar:report`, "write up the autoresearch results", or "summarise the experiment loop". Reads `./.ar/ar.jsonl` from disk, so it works in a fresh session. Writes only the report; never iterates, commits, or reverts, and leaves the loop able to continue.

Repository
ccplugins ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write the final summary of an autoresearch run to `./.ar/final_report.md` — trajectory, best commit and its diff, what worked, what failed, and what to try next. Use for `/ar:report`, "write up the autoresearch results", or "summarise the experiment loop". Reads `./.ar/ar.jsonl` from disk, so it works in a fresh session. Writes only the report; never iterates, commits, or reverts, and leaves the loop able to continue.

Triggers from the description

write up the autoresearch resultssummarise the experiment loop
Original author description

Write the final summary of an autoresearch run to `./.ar/final_report.md` — trajectory, best commit and its diff, what worked, what failed, and what to try next. Use for `/ar:report`, "write up the autoresearch results", or "summarise the experiment loop". Reads `./.ar/ar.jsonl` from disk, so it works in a fresh session. Writes only the report; never iterates, commits, or reverts, and leaves the loop able to continue.

How it works

  1. Steps
  2. Hard rules
  3. Completion status
Original SKILL.md headings · 56 lines, 388 words
SKILL.md preview
---
name: report
description: Write the final summary of an autoresearch run to `./.ar/final_report.md` — trajectory, best commit and its diff, what worked, what failed, and what to try next. Use for `/ar:report`, "write up the autoresearch results", or "summarise the experiment loop". Reads `./.ar/ar.jsonl` from disk, so it works in a fresh session. Writes only the report; never iterates, commits, or reverts, and leaves the loop able to continue.
allowed-tools: [Read, Write, Glob, Grep, Bash]
---

# /ar:report — write the run up

Turn the record into something a person can read. Do not iterate.

## Steps

1. Read state (`cat ./.ar/ar.jsonl`, plus `worklog.md` and
   `results.tsv` if present). No `ar.jsonl` means nothing to report — say so and
   stop.
2. Reconstruct the run per `${CLAUDE_PLUGIN_ROOT}/references/resume-loop.md` §1,
   across **all** segments, not just the last: a segment boundary marks a harness
   or baseline change, so metrics either side of it are not comparable and the
   report must say where the boundaries fell rather than plotting through them.
3. Pull the winner chain from git — it is an independent record of the same run:

    ```bash
    git log --format='%h %s' --grep='"status":"keep"' <config.branch>
    git diff <config.snapshotCommit>..<bestCommit> --stat
    ```

4. Write `./.ar/final_report.md`:
    - **Goal and setup** — objective, metric, direction, harness, budget.
    - **Result** — baseline → best, absolute and relative, with the confidence
      tier. State plainly whether the total gain clears the noise floor; a run
      that ended inside its own scatter did not find anything, and the report
      says so rather than dressing it up.
    - **Trajectory** — the keep chain, each with commit, metric, delta and the
      one-line description of the change.
    - **What worked** — the winning changes and, where the record supports it,
      why they worked. Distinguish an explanation from a guess.
    - **What failed** — discarded families of hypotheses. This is the part with
      the most reuse value; a future run should not re-derive these.
    - **Caveats** — crashes, `checks_failed` iterations, seeds that disagreed,
      segment boundaries.
    - **Next** — the strongest untried ideas, from `ideas.md` and the plateau
      history.
5. Report the path. `.gitignore` carries `!.ar/final_report.md`, so the report is
   trackable if it should be committed — offer, do not commit unasked.

## Hard rules

1. **Write `final_report.md` and nothing else.** No iterating, no commits, no
   branch switches, no reverts.
2. Every number comes from `ar.jsonl` or git. Never recompute or estimate one.
3. Report failures and null results as prominently as wins. A loop that banked
   noise is a finding; concealing it wastes the next run.

## Completion status

End with a terminal status token as the last line of your reply — `DONE`,
`DONE_WITH_CONCERNS`, `BLOCKED`, or `NEEDS_CONTEXT` — per
`${CLAUDE_PLUGIN_ROOT}/references/completion-status.md`. For `/ar:report`, `DONE` once
`final_report.md` is written and its path reported; `NEEDS_CONTEXT` if `ar.jsonl`
is absent or empty (nothing to summarise).

Versions

RepositoryScoreLicence
This page · emaballarin/ccplugins100MIT
petrbouda/jeffrey100Apache-2.0
petrbouda/jeffrey100Apache-2.0
onmax/comark-ui100MIT
renzrollon/interlock100MIT
digital-stoic-org/agent-skills100MIT
90p-labs/harness100MIT
quantskills/agent-quantspace100GPL-3.0
magnifito/domain-name-engine100MIT

Database snapshot: 13.11.2026 · package version 3d92514176ae (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100status
    Print the current autoresearch run's state — goal, baseline, noise floor, best-so-far, run tallies, budget, branch, and the last few iterations. Use for `/ar:status`, "how is the loop doing", "what's the best so far", or any read-only check on an autoresearch experiment.…
  • 100resume
    Run the autoresearch experiment loop — propose one change, measure it, keep it only if it beats the noise floor, repeat. Use to resume or continue an autoresearch run, for `/ar:resume`, for "keep iterating", "next experiment", "continue optimising", or whenever `./.ar/ar.jsonl`…
  • 100autoresearch-create
    Set up and run an autonomous experiment loop for any optimization target. Gathers what to optimize, then starts the loop immediately. Use when asked to "run autoresearch", "optimize X in a loop", "set up autoresearch for X", or "start experiments".
  • 100autoresearch-create
    Set up and run an autonomous experiment loop for any optimization target. Gathers what to optimize, then starts the loop immediately. Use when asked to "run autoresearch", "optimize X in a loop", "set up autoresearch for X", or "start experiments".
  • 100autoresearch
    Set up, resume, inspect, or pause a measured experiment loop in Claude Code or Codex. Use when asked to run autoresearch or iteratively optimize a named benchmark. Reviewing this plugin alone does not start an experiment loop.
  • 100autoresearch
    Iterative keep/discard experiment workflow over one explicitly configured repo, editable file, run command, and metric rule. Any agent may use it, but the `autoresearch` specialist is the default owner for sustained experiment-loop work.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.