Skip to content
LedgerLedger
← LibraryBuilder · B9

Reviewer & QA agents

Build-along · ~12 min at your own keyboard

An agent that just wrote a listing is soaked in its own reasoning, the same bias as humans reviewing their own work. A reviewer subagent with a clean context reads the output cold and catches what the writer literally cannot see. For listings, point it straight at compliance: no 'perfect for families', no 'safe neighborhood', no steering language. Two traps. Models lean toward agreeing with you, because they were trained on what people liked to hear. Ask 'is this good?' or say you wrote it, and the review comes back kinder. So ask neutrally: 'review this against these checks,' and don't say whose work it is. And a review is a judgement, not a measurement: run the same reviewer twice and it can flag different things. Treat one clean review as one opinion. For anything a client, a regulator or the public reads, a person still checks.

Where these ideas come from: Sycophancy, Non-determinism (AI Hero dictionary). Paraphrased here.

Skill to keep · Check

Check the work two ways

In a new chat, checks the work against your brief and against your own rules, one list each.

Example. Pass one finds the page never says by when the client must reply. Pass two finds a rate that came from memory, marked VERIFY, and a sentence that reads as advice.

Where to save it
  • Claude. Upload the skill folder as a skill, or paste the text into a Project's instructions. In Claude Code, put the folder in your skills folder.
  • ChatGPT. Paste the text into a Project's instructions or a custom GPT's instructions, or into your custom instructions.
  • Gemini. Paste the text into a Gem's instructions.
  • Copilot. Paste the text into a Notebook's instructions, or keep it in a file you attach when you need it.
  • Any other assistant. Keep the file. Paste it at the start of a chat, then say which job you are on.

Then run it on one real piece of work and change the wording until it sounds like you.

Licence and credit

This skill is adapted from the code-review skill in an open source set, the skills library. The wording and examples are rewritten for your work. The original licence travels with it. Every download carries NOTICE.md, and the copied text ends with a credit line.

MIT License

Copyright (c) 2026 Matt Pocock

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Six skills in all, one for each step of the flow. See the whole kit

Do this

0/4

Share what happened

Paste the reviewer's findings on a real listing draft and which ones were legit.