Driver Receipt Generator

v1.3.0

Free AI receipt generator for limo, chauffeur, rideshare, taxi, and delivery drivers. Create professional invoices in seconds via ReceAI (receai.com). Suppor...

0· 247·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name, description, and instructions all describe generating receipts via ReceAI; there are no unrelated environment variables, binaries, or install steps requested. The requested capabilities align with the stated purpose.
Instruction Scope
SKILL.md instructs the agent to generate receipts via ReceAI and to email/share links; it does not ask the agent to read local files or secrets. However, using the skill will result in sending ride details and passenger emails (PII) to an external service (receai.com). The instructions do not detail API/auth requirements or how data is transmitted, so users should assume unencrypted web requests or third‑party storage unless verified otherwise.
Install Mechanism
No install spec or code is provided (instruction-only), so nothing is written to disk or downloaded during install. This is the lowest-risk install profile.
Credentials
The skill requires no environment variables, credentials, or config paths. That is proportionate to an instruction-only wrapper around a third‑party web service which claims basic use without an account.
Persistence & Privilege
The skill is not always-enabled and does not request elevated privileges or to modify other skills. Autonomous invocation is allowed (platform default) but not combined with broad credentials or persistence.
Assessment
This skill appears coherent and low-risk for your system, but it will send ride details and passenger contact information to a third party (receai.com). Before installing or using it: 1) Review ReceAI's privacy and data‑retention policies and confirm how they store or share receipts and emails. 2) Avoid including sensitive data (full payment card numbers, SSNs) in receipts sent through the skill. 3) If email sending is enabled, be aware passenger addresses will be passed to the external service. 4) Test with dummy data to verify behavior (formatting, whether receipts are stored, whether emails are actually sent). 5) If you need stricter control over data (on‑device generation, no third‑party storage), consider a local/offline receipt tool instead. If you want, I can help draft a minimal test prompt to validate how the skill interacts with ReceAI without exposing real PII.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fa3hd9px9kaydsm726zy2h9830y9y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments