Check-signing skill
One command signs a check with my saved signature and drafts it to the right property manager.
Checks, payroll and vendor, get downloaded and then have to be signed and sent to each property's manager to print. It is a small, frequent errand, and the obvious version is blocked in my setup: I cannot drive a native file picker from a local path into a web app.
How it works
It is a Claude Code skill. The check PDF gets signed in DocHub with my saved signature, then drafted in Gmail to the right property manager. Because a local file cannot be pushed straight into the web app, the skill bridges through the mounted Google Drive (same account, syncs both ways) and picks the file from the app's Drive picker. The download modal has a zoom-related click bug, so it is driven with a scripted click instead of coordinates.
- It always leaves an email draft. I do the actual send.
- The signature sits centered on the signature line, not shoved into a corner, a correction I made once that it now remembers.
It is live and used on real checks. The recipient mapping per property is built in, so the command really is one step.
This is deliberately not full automation. The tedious part (sign, place, attach, address) is done for me. The irreversible part (sending money out the door) stays a human click. That gate is the pattern I hold everywhere money moves.