Anonymise a Work Log Consistently
You get a shareable copy of a work log where every real name, path, company and secret is swapped for a believable fake one, used the same way throughout. A final leak check catches anything missed, so you can trust the result more than a single-pass rewrite.
The prompt
You are a careful data-privacy editor preparing work logs for sharing or reuse as examples.
Task: Rewrite the work log below so no real personal or company detail remains, while it still reads as a realistic, internally consistent log.
Steps:
1. List every item from {real_identity_details}, plus any other name, email, username, folder path, company, domain or secret you spot in {work_log}.
2. Invent a fresh fake identity for this log only, using {log_label} to vary it. Avoid stock placeholders such as "John Smith" or "Acme"; make each replacement plausible and different from any other log you might process.
3. Replace each listed item with its fake equivalent, the same way every time it appears. Replace every secret value with a labelled marker such as [API_KEY_1].
4. Re-read your rewrite against the step 1 list, checking changed case, partial names and paths, and fix any leftovers.
Output: The rewritten log first, with no commentary inside it. Then one line reading "Leak check: PASS" or "Leak check: FAIL", naming only the types of item still present (never the real values).
Change the parts in curly braces. Use it before sharing support chats, agent session logs or meeting notes with contractors, or before adding them to a prompt library or training set.
What happened when we ran it
We sent
You are a careful data-privacy editor preparing work logs for sharing or reuse as examples. Task: Rewrite the work log below so no real personal or company detail remains, while it still reads as a realistic, internally consistent log. Steps: 1. List every item from Full name: Priya Venkataraman. Username: pvenkat. Email: priya@brightlarder.co.uk. Company: Bright Larder Ltd. Domain: brightlarder.co.uk. Home folder: C:\Users\pvenkat., plus any other name, email, username, folder path, company, domain or secret you spot in Priya Venkataraman asked the agent to fix the failing checkout test in C:\Users\pvenkat\projects\shop-api. The agent found that the Stripe key sk_live_51Nx8exampleKEY was being read from the wrong .env file and told Priya to rotate it. It then emailed a summary to priya@brightlarder.co.uk and opened a pull request on the Bright Larder Ltd GitHub organisation. The test passed after the config path was corrected.. 2. Invent a fresh fake identity for this log only, using session-0042 to vary it. Avoid stock placeholders such as "John Smith" or "Acme"; make each replacement plausible and different from any other log you might process. 3. Replace each listed item with its fake equivalent, the same way every time it appears. Replace every secret value with a labelled marker such as [API_KEY_1]. 4. Re-read your rewrite against the step 1 list, checking changed case, partial names and paths, and fix any leftovers. Output: The rewritten log first, with no commentary inside it. Then one line reading "Leak check: PASS" or "Leak check: FAIL", naming only the types of item still present (never the real values).
The model replied
Run on Claude Sonnet 5.5, 14 Nov 2026. Automatic check: 5 out of 5.
Mentioned for
Claude, ChatGPT, Gemini
Where it came from
Found on GitHub, shared by drost-ai: drost-ai/tinker-ai-skill.
This is our own version of the idea, written and tested by us. The original may differ.