---
title: "Discussion on \"How I turned a one-off Google Payments export into a reusable Codex skill\" | Hashnode"
description: "Discussion on \"How I turned a one-off Google Payments export into a reusable Codex skill\". 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."
url: "https://hashnode.com/posts/how-i-turned-a-one-off-google-payments-export-into-a-reusable-codex-skill/6a4133a320da316f03afeb24"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I turned a one-off Google Payments export into a reusable Codex skill](https://blog.daneke.ge/how-i-turned-a-one-off-google-payments-export-into-a-reusable-codex-skill?utm_source=hashnode&utm_medium=feed)

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.

Jun 28 · 1 min read · blog.daneke.ge  
Read the article

## Written by

[George Daneke](https://hashnode.com/@flatroy)

@flatroy · Ramat Gan, Israel

  
[View profile](https://hashnode.com/@flatroy)

Web Developer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
