kklimuk/docx-cli / .claude/skills/weak-agent-test
weak-agent-test
VerifiedRun 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/invoice/task.md
View on GitHub# Update our invoice template with real data and a new logo
We have an invoice template (`invoice.docx`) that needs to be filled out with the real deal data before we send it to the client. Fill it in with the values below, swap its logo, and apply the few formatting touches noted under "Make the line-items table easier to read." Keep the existing tables structurally intact — don't break the columns or un-merge any cells; only the text content, the logo, and those specific formatting touches change.
One thing to watch for: the template has more placeholder lines than some sections need (for example, the "from" address spans two lines but the real address fits on one; each line item has a sub-line below it). Fill the lines you use and remove the leftover placeholder lines so no template text is left behind. A half-filled form with empty placeholder lines dangling is not done.
## Header / "from"
- Company: **Northwind Robotics, Inc.**
- Phone: **(415) 555-0137**
- Email: **billing@northwindrobotics.com**
- Address: **2120 Bryant Street, San Francisco, CA 94110**
- Invoice #: **NW-1042**
- Invoice date: **June 8, 2026**
- Due date: **July 8, 2026**
## Bill To / Ship To
- Customer: **Acme Health Systems, LLC**
- Customer email: **ap@acmehealth.com**
- Billing address: **88 Market Street, Suite 400, Chicago, IL 60603**
- Shipping address: same as billing.
## Line items
There are **four** line items, but the table only has rows for three. Fill the three existing item rows, then add a new row for the fourth one (without overwriting the totals row) and fill it. After they're all in, make the Description column the widest — while keeping the Price and Amount columns wide enough to show dollar values like `$10,100.00` on one line without wrapping.
| Description | Quantity | Price | Amount |
| --- | --- | --- | --- |
| RX-7 sensor module | 4 | $1,250.00 | $5,000.00 |
| On-site integration (per day) | 3 | $900.00 | $2,700.00 |
| Extended support, 12 mo. | 1 | $1,800.00 | $1,800.00 |
| Calibration kit | 2 | $300.00 | $600.00 |
## Totals
- Subtotal: **$10,100.00**
- Discount: **-$500.00**
- Shipping: **$0.00**
- Tax total (8.75%): **$840.00**
- Other: **$0.00**
- **Total: $10,440.00**
## Make the line-items table easier to read
A few quick polish touches on the line-items table so it reads cleanly for the client:
- Give the header row (Description / Quantity / Price / Amount) a light grey background so the column titles stand out from the data.
- The Price and Amount columns are dollar figures — line them up flush to the right so the decimals read down the column, instead of sitting left-aligned.
- If this invoice ever runs onto a second page, the column-title row should repeat at the top of that page rather than leaving the continued rows with no headings.
## Notes
Replace the "Notes" body with: *Payment due within 30 days. Wire details on request.*
## The "do not send" stamp
There's a red-bordered stamp box near the bottom of the page that reads "TEMPLATE — DO NOT SEND". Keep the box — it's a nice call-out — but change its wording to **Thank you for your business!** so it reads as a client-facing note instead of a template warning. Nothing about the box's look (fill, border, position) should change; only the words.
## Logo
Replace the placeholder logo in the **top-left corner** with the new company mark at `assets/logo.svg`. Swap that one image only — don't add a second logo, and **don't touch the small payment mark in the footer** (it must stay). The document should still have two embedded images when you're done (the new logo + the footer mark).
## What done looks like
All `Item 1/2/3`, `$0.00`, `Customer name`, `Your Company Name`, and similar placeholder text is replaced with the values above. Before finishing, do one consolidated sweep for every placeholder family named here — item labels, description lines, customer/company names, address prompts, and zero-dollar template amounts — rather than checking just one kind and assuming the rest are gone. Leftover placeholder lines (the extra address line, the per-item sub-lines) are removed, not left dangling. The three tables are still present and unbroken. The line-items table has four filled rows, the Description column is the widest, and no dollar value wraps to a second line. Its header row has a light grey fill, the Price and Amount columns are right-aligned, and the header is set to repeat on a second page. The top-left logo is the new mark from `assets/logo.svg`, and the footer's payment mark is untouched. The stamp box near the bottom still exists and now reads "Thank you for your business!" — no "TEMPLATE" or "DO NOT SEND" wording anywhere in the document.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |