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/mnda/task.md
View on GitHub# Fill out our mutual NDA so it's ready to sign
We're about to sign a mutual non-disclosure agreement with Acme, and the cover page of
`mnda.docx` is still a template full of blanks. Fill it out from the deal details below.
The blanks are the yellow-highlighted placeholders on the cover page (and the two
signature blocks). Fill each one with the right value — and clear the yellow as you go,
so nothing stays highlighted once it's filled. The square brackets are part of the
blank, not part of the answer: `[1 year(s)]` becomes `2 year(s)`,
`[choose 1: Effective Date || the date of last disclosure]` becomes just
`Effective Date`, and so on — a finished value has no brackets around it.
Important: change ONLY the placeholder values and the highlight. Everything else about
how the document looks — every typeface, size, and color — must stay exactly as it is
now. The Georgia title, the bold field labels, the small gray sub-labels, and the Arial
body should all look exactly as they do today. I just want the blanks filled in; the
document should otherwise look untouched. Edit the file directly.
## The parties
- **Party 1**
- Company: **Northwind Robotics, Inc.**
- Signatory: **Dana Okafor**, **Chief Operating Officer**
- Notice email: **legal@northwindrobotics.com**
- **Party 2**
- Company: **Acme Health Systems, LLC**
- Signatory: **Marcus Bell**, **VP, Corporate Development**
- Notice email: **contracts@acmehealth.com**
## Terms to enter on the cover page
| Field | Value |
| ---------------------------- | ------------------------------------------------------------------------------ |
| Purpose | Evaluating a potential supply-and-integration partnership between the parties. |
| Effective Date | **June 8, 2026** |
| MNDA Term | Expires **2 year(s)** from the Effective Date. |
| Term of Confidentiality | **3 year(s)** from the **Effective Date**. |
| Governing Law | The laws of the State of **Delaware**. |
| Jurisdiction | The state and federal courts located in **New Castle County, Delaware**. |
| Changes to Standard Terms | None. |
| Date (both signature blocks) | **June 8, 2026** |
The signature table needs Print Name, Title, Company, Notice Address, and Date filled
in for **both** parties. Put each value in the blank area beside its label, keeping the
label cells, narrow divider column, signature lines, and row layout untouched — don't
add extra lines to neighboring cells. The date appears in both signature blocks, so make
sure both occurrences are filled rather than stopping after the first one.
## What "done" looks like
Every yellow-highlighted placeholder is replaced with its real value (no `[ ... ]`
brackets left), both signature blocks are filled in, and there's no yellow highlight
left anywhere. The only differences from the original are the filled-in values — every
font, size, and color is exactly as it was.
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 |