crinkl-claws_skill

Overview

This skill verifies billing emails using DKIM signatures and mints identity-free spend tokens that earn Bitcoin over the Lightning network for the operator. It only processes approved vendor receipts and discards original email content after extracting invoice metadata. The design preserves user privacy by never storing personal data in the spend tokens.

How this skill works

The agent searches the connected Gmail account for recent billing emails from an approved vendor list, downloads each message in raw RFC 2822 form, and sends the full raw email to the verification API. The server validates the DKIM signature, extracts only vendor name, invoice date, total and currency, discards the original message, and mints a spend token if verification succeeds. The agent logs results, marks processed messages, and reports earnings tied to the operator's API key.

When to use it

• Automatically verify and monetize recent billing receipts from approved vendors
• Provide cryptographic proof of purchase without exposing personal information
• Supplement a wallet or operator with earned sats per verified receipt
• Audit vendor email authenticity when you suspect tampering or spoofing
• Integrate with a read-only Gmail connection for safe, non-destructive scanning

Best practices

• Use the provided pairing flow to obtain and securely store the API key shown once
• Grant only gmail.readonly scope to avoid modifying inbox content
• Monitor log entries for 202, 409, 422, and 429 responses to handle vendor discovery and errors
• Poll for pairing approval every few seconds and respect code expiry windows
• Rotate or revoke the API key if the operator or wallet ownership changes

Example use cases

• A personal assistant agent scans recent receipts, verifies authenticity, and accumulates sats for the operator
• A small business automates receipt verification to produce tamper-proof purchase attestations without collecting customer identities
• A wallet operator aggregates verified spend tokens to fund Lightning payouts shared among connected agents
• Security teams validate that vendor billing messages are signed by the expected mail servers before accepting chargebacks