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/contract-markup/task.md
View on GitHub# I need our changes marked up on this contract before we sign
I run **Mercer Design Studio**, and we just got the contract draft (`contract.docx`)
from **Nimbus Freight Systems** for a project we're about to start. I finally read the
whole thing and honestly it's pretty outrageous — almost every clause is written to
protect them and dump all the risk on us. I'm not signing it as it stands.
Can you mark it up and get it ready to send back to them? Track the changes so they can
see exactly what we touched, and leave notes on the spots where we're pushing back, so
it's clear what we're objecting to and why.
## What I can't accept — these have to change
- The **non-compete** is insane — five years, the entire world, any
industry, and a $50,000 penalty every time _they_ decide we crossed a line. No way I
can agree to that. It needs to come out, or be cut down to something small and sane.
- The **liability cap** lets _them_ off the hook at a hundred dollars while
_we'd_ be on the hook for everything. That's completely backwards — it has to be fair
in both directions.
- The **payment terms** say "Net 90, at the Company's sole discretion." I'm
not floating their bills for three months and hoping they feel like paying. We need to
get paid on a normal, dependable schedule.
- The **indemnification** makes _us_ cover _them_ even when the problem is
**their own fault**. I'm not signing up to pay for their negligence.
## What bugs me — flag these so we can talk it through
I'm not necessarily killing these outright, but I want my objections on the record so we
can discuss them:
- The **IP section** looks like it grabs not just the project work but things
I do on my own time and stuff I made before we ever met. That can't be right.
- The **personal guarantee** would put _me personally_ on the hook for
everything, not just the studio. Flag it.
- **Dispute resolution** — arbitration in front of an arbitrator _they_
pick, with us paying all the fees up front. That's not a fair fight.
- Section 7 has us **waiving our right to our own lawyer**. Seriously?
- Section 13 lets them **change the contract later just by posting a new version to a
web page**. Flag that one too.
## One more thing
Section 9's lines are crammed tight together, which makes a clause I really care about a
slog to read. Please increase the line spacing on it — open it up to something roomier
like one-and-a-half — so it's easier on the eyes. It's the clause I most want them to
re-read carefully.
And a small house-style fix: in the intellectual-property section, the sub-points are
labelled a, b, c, d. We always use small Roman numerals (i, ii, iii) for sub-clauses in
our contracts — please switch those over to match.
## What "done" looks like
It comes back marked up and ready to send: our changes to the unacceptable terms are
visible as tracked edits (they'll see exactly what we struck or rewrote), my objections
show up as notes pinned to the clauses I flagged, section 9 is legible, and the IP
sub-points read as i, ii, iii. None of the wording is changed silently — every change to
what the contract says shows as a tracked edit they can see and respond to, and every
objection is a note. The two house-style fixes (the spacing and the numerals) are just
formatting; do them however is cleanest.
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 |