Quick fixes AG-V005
You are about to use something you have not read
Shared methods · A shared method; linked tool guides explain the exact steps.
This page covers tools outside your selection. You can still read it. Find matching guides
Sending, running or filing an output you only skimmed makes its errors yours. The read costs minutes; owning an unread error costs more.
I almost sent something I hadn't read? Here's the quick fix ↓ — the why sits right below it.
Quick fix: You are about to use something you have not read
Instead of Generate the email, glance at the first line, hit send.
Try Read the whole thing once as the recipient — then send. For code: read the diff before you run it, run it before you ship it.
The signature under the output is yours, not the model's.
Why this works
Skimming catches format and misses content: the wrong name in paragraph three, the date that contradicts the attachment, the confident claim you never made, the code that deletes more than it should. Generated text is built to read smoothly, which makes skimming feel safer than it is; fluency hides exactly the errors that matter. The moment an output leaves your machine or runs on it, every one of those errors converts from the model's sample to your action.
When this applies
The gap between "generated" and "sent/run/filed" is under a minute, and the honest answer to "did you read it?" is "mostly".
Template
A checkpoint, not a prompt:
Before this leaves: read it end to end, once, as the person receiving it. Names, numbers, dates, claims: do I stand behind each?
Go deeper
Skim-approval is automation bias in its everyday clothes. For agent-written code, the deeper habit is reviewing agent code; for agent-run tasks, reviewing the output covers why the summary of the work is not the work.
Improve next
- Check it before you act on it
Worth verifying before relying on this.
- Raise the checking with the stakes
The stakes here are high — verify before acting, or ask a human.
Something wrong with this page?
Say what you expected and what you got. That is usually the shortest route to a correction, and it goes on the public issue tracker so the fix is visible.