After a few years and a few contributors, the author profiles on a site drift. Display names that are really email prefixes, empty bios where an author box expects one, a profile field half your team filled in and half ignored. Fixing it one profile at a time is the kind of chore that never reaches the top of the list.
This hands the reading and the drafting to the agent and keeps the approving with you.
I want to tidy up the profiles for [the authors in the Editor and Authorroles]. Change nothing without my say-so.
First pass: list those users and read their current display name, email, bio,and [the "job title" profile field]. For the first [10], hand me a table withthe current values beside a suggested cleanup, following [First Last for displaynames]. Leave anything that already looks right alone.
I will tell you which to keep. Only after I say so, write the approved changesback, display name and email through the user update and the profile fieldsthrough user meta, in small batches, showing me each batch before it saves. Donot change anyone's role. At the end, list every account you touched.Why this is safe to run
The whole first pass is reads. Listing the users and reading their profiles writes nothing, so you see every proposed change as a table before a single value is saved.
The write half is deliberately narrow. Editing a profile reaches display name, name, and email, and the profile-meta write only touches allowlisted scalar keys. Authentication, capability, and two-factor keys are blocked outright, so this cannot alter anyone’s access, and changing a role is a separate ability gated behind the promote-users capability that this recipe never calls. Every write ability here stays off until you enable it, each call is checked against the capability of the user you bound the agent to, and every write lands in the Activity Log with the account it changed. If a bio reads wrong, the log tells you exactly which profile to open.
Already connected? You do not have to paste this at all. Ask your agent for the “bulk-update user profile fields” recipe, or just describe the cleanup, and it runs the same two-pass flow on your own accounts.