gmail-receipt-drive-archiver/SKILL.md
Use when a user wants unread Gmail receipt, invoice, purchase, or order-confirmation emails rendered to PDF, uploaded to a Google Drive folder named with the current date plus "processed invoice", and then marked read.
npx skillsauth add ChipmunkRPA/gmail-receipt-drive-archiver-skill gmail-receipt-drive-archiverInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when the user wants a Gmail cleanup/archive pass that:
gws auth works for Gmail and Drive.npm install
The Python script now auto-installs missing Node deps (playwright-core) when needed.
python scripts/process_unread_receipts.py
M.D.YYYY processed invoice using the current local date.Fwd: Uber Eats order receipts) are also treated as candidates when forward markers and commerce/receipt hints are present.output/pdf/tmp/email_html/scripts/process_unread_receipts.py: Gmail and Drive orchestration through gwsscripts/render_email_html_to_pdf.js: Playwright-based HTML-to-PDF renderer using local Chromegws authenticated for Gmail and Drivepythonnode and npmIf Chrome is not on PATH, set CHROME_PATH.
If gws is not on PATH, set GWS_EXE.
If the CLI config is not in the default location, set GOOGLE_WORKSPACE_CLI_CONFIG_DIR.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.