receipt-snap-spainProcess receipt photos and PDFs, extract vendor date amount currency, convert to EUR, upload to Google Drive with proper naming Vendor_Date_EURAmount.pdf, an...
Install via ClawdBot CLI:
clawdbot install marinhobot/receipt-snap-spainInstall gog CLI via Homebrew:
brew install faradayhq/gog/gogRequires:
Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://open.er-api.com/v6/latest/{currency}`Audited Apr 17, 2026 · audit v1.0
Generated May 9, 2026
A freelancer receives a receipt via Telegram with #recibo. The skill extracts vendor, date, amount, and currency (e.g., USD), converts to EUR, uploads the receipt to Google Drive with a standardized filename, and logs all details to a Google Sheet for quarterly tax reporting.
A small business owner collects receipts from multiple sources (PDF invoices, photos). The skill deduplicates entries, categorizes expenses according to Spanish tax categories, and generates a quarterly summary report for their tax accountant.
Employees submit expense receipts (meals, travel, software subscriptions) to a central system. The skill converts non-EUR amounts, categorizes each expense, and logs them in a shared Google Sheet for approval and reimbursement processing.
An individual uses the skill to track deductible expenses (e.g., education, software) for tax filing. The skill automatically categorizes receipts and provides a categorized export, helping the user maximize deductions at year-end.
Offer a monthly subscription to freelancers and small businesses that integrates with Telegram and Google Workspace. Revenue comes from tiered plans based on receipt volume (e.g., 50/month basic, unlimited premium).
Charge a setup fee for configuring Google Drive and Sheets integration, plus a small per-receipt processing fee (e.g., €0.10 per receipt). Target is cost-conscious users who prefer pay-as-you-go.
License the skill to accounting firms that want to offer automated receipt processing to their clients. Revenue is based on per-client or per-company licensing fees, with custom branding options.
💬 Integration Tip
Ensure the Google Drive folder and Sheet are shared with the authenticated gog account. Use environment variables for all IDs and keep the local CSV log for offline backup.
Scored May 9, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Query Google Places for text search, place details, resolve, reviews, or scriptable JSON via goplaces.
Google Contacts API integration with managed OAuth. Manage contacts, contact groups, and search your address book. Use this skill when users want to create, read, update, or delete contacts, manage contact groups, or search for people in their Google account. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Contacts connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Contacts action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Contacts examples; they add no Google Contacts capability - Google Contacts is not an event source, a trigger cannot read Google Contacts data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).