Skip to content

kklimuk/docx-cli / .claude/skills/weak-agent-test

weak-agent-test

Verified

Run the weak-agent adversarial test harness against docx-cli. Spawns weak exercise agents (Haiku by default, Sonnet to probe, or a local agent harness's pre-produced runs) to perform real document tasks over six scenarios — five editing (MNDA form-fill + font fidelity, invoice table-edit/restructure + logo replace, résumé styling, contract redlining + commenting, contract finalize via accept/reject + comment reply/resolve) and one authoring (T. S. Eliot poetry journal: multi-column, verse, footnotes, links, figure) — renders every result with Word, has opus judge them against ground-truth rubrics, measures each exercise's tool economy, token cost, wall-clock, and correctness (from transcripts for Claude, the exercise.json ledger for the local harness), and synthesizes a prioritized ergonomics report. Use when the user says 'adversarial review', 'test docx-cli with weak agents', 'run the haiku harness', 'weak agent test', or wants to re-run yesterday's adversarial process.

scenarios/eliot-journal/task.md

View on GitHub
# Commission: a T. S. Eliot poetry journal

I'd like a beautifully typeset `.docx` poetry reader dedicated to T. S. Eliot — think of
it as a small printed anthology. Build it from scratch and save it as **`journal.docx`**
in this folder. The source poems are in `assets/eliot-poems.md` and the frontispiece
image is in `assets/frontispiece.svg`; there is no template, so start from a blank
document.

I'm after a richly structured booklet: a title page, a two-column verse body, editor's
footnotes, a closing colophon with a link, and consistent page chrome throughout. Here's
what I'm picturing.

## What I want

1. **Title page (single column).** Open with a centered title ("A T. S. Eliot Reader"),
   a subtitle, and a short editor's note paragraph. Place the frontispiece image
   `assets/frontispiece.svg` on this page with a caption beneath it (e.g.
   "Frontispiece"). Feel free to set a width on the image if you'd like it smaller.

2. **Two-column poem body.** After the title page, move into a two-column layout so the
   verse flows side by side on the wide page, the way verse looks in a printed anthology.

3. **Poems with headings and preserved line breaks.** Give each poem a heading with its
   title. Keep the line breaks of the verse exactly as they appear in the source — each
   line of verse should be its own separate line on the page, not reflowed into a block
   of prose. Add at least **two footnotes** — brief editor's annotations glossing an
   allusion or phrase (for example, a note on "The Waste Land" or a phrase in "Prufrock").

4. **Poems to include**: _Preludes (I)_, the opening of _The Hollow Men_,
   and an excerpt from _The Love Song of J. Alfred Prufrock_. Add the opening of
   _The Waste Land_ if there is room.

5. **Colophon (single column).** Close with a short single-column section: "Compiled
   June 2026. All poems in the public domain." Turn the words **"public domain"** into a
   hyperlink pointing to https://www.gutenberg.org/ebooks/1321 (The Waste Land on Project
   Gutenberg).

6. **Landscape orientation.** Set the whole document to landscape so the wide page
   carries the two columns comfortably. This is a true page-setup change, not just
   resizing content.

7. **Running header and footer.** Put a running header on every page with the collection
   title ("A T. S. Eliot Reader"). Put centered page numbers in the footer in the form
   "Page X of Y". These are page header and footer areas — not body text.

8. **Garamond throughout.** Set the journal in a classic serif — **Garamond** — across
   the whole document, so both the body text and the poem-title headings share it. The
   result should look like a printed anthology, not a word-processor default.

## What "done" looks like

When the file is opened (or printed), you see: a single-column title section with the
frontispiece and caption; a two-column body where the poems sit side by side with correct
headings and intact verse lines; at least two footnotes; a closing colophon whose "public
domain" text links out; a Garamond face in body and headings; landscape pages; and the
collection title running at the top of every page with a page number centered at the
bottom. Save as **`journal.docx`** in this scenario folder.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall