Search for a command to run...
Turned a messy Google Payments export into a reusable Codex skill. The main bug was duplicate month rows like Jan 27 vs Jan 27, 2025, which can make you export the wrong year if you click too fast. The skill now reuses the logged-in Chrome session, targets explicit-year rows only, resets the details pane, and verifies every image by date + transaction ID.
No comments yet. Be the first to comment.
You want to generate HideMail aliases from Bitwarden app or browser extension? Easy. 1) In Bitwarden options for username generation select “Forwarded email alias”; 2) Select as service “Addy" 3) Enter as domain hidemail.app (in future you can add cu...
How to solve "Error: Google Sign-In failed: [16] Account reauth failed" issue
Hetzner's S3-compatible Object Storage provides a scalable and cost-effective solution for storing and retrieving large amounts of data. In this guide, we'll walk through the process of integrating Hetzner S3 Object Storage with a Laravel 11 applicat...
Or how to remember what social login I used on websites for "sign in" Managing social logins efficiently is crucial in today's digital world. But you can simplify this process using Bitwarden or any other password manager like 1password. Create a de...
I had to export a year of Google Payments activity as clean transaction-detail images, and it turned out to be more fragile than it looked.
So I packaged the workflow into a reusable Codex skill:
reuse the logged-in Chrome session
inspect visible activity rows first
target only rows with the explicit year
reset the details pane scroll before every capture
crop only the right-side transaction-details pane
verify that each exported image includes the date and transaction ID
The result is a repeatable yearly export workflow instead of a fragile manual process. Next time I need the same report, I can run the skill again instead of rediscovering all the UI edge cases.
https://gist.github.com/Flatroy/9780ac98ede0af911297b6291674f085