Invoice
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent invoice workflow that stores sensitive billing data and can optionally send invoices, but those behaviors are disclosed and aligned with its purpose.
This skill appears safe for its stated purpose if you want a local invoice assistant. Before using it, make sure you are comfortable storing client tax IDs, addresses, invoice PDFs, your business details, and IBAN under ~/billing. Review every invoice before finalizing or sending, and enable email or recurring invoices only when you intend those workflows.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A wrong client, amount, tax rate, or recipient could result in an incorrect official invoice or client communication.
The skill can convert draft data into an official invoice number/PDF and optionally send it to a client. This is central to the stated purpose and includes a review step, but mistakes can have real business impact.
Review — Show preview, allow edits. ... Finalize — Generate PDF, lock number. ... Send — Email to client (optional).
Require explicit user confirmation before finalizing or emailing invoices, and review invoice number, client data, tax treatment, amount, and recipient.
Incorrect or over-broad email/payment configuration could expose payment details or send invoices from the wrong account.
The skill asks for payment details and may use email-sending authority. Both are expected for invoicing, but they involve sensitive account and payment information.
Before first invoice, collect: ... Bank details (IBAN) for payment ... Email for sending (optional)
Use only the intended email account, verify recipients before sending, and keep stored bank/payment details accurate and protected.
Stored client, tax, invoice, and payment data could be reused in future tasks; wrong or stale stored data could lead to incorrect invoices.
The skill stores persistent billing context, including client records, user business configuration, and invoice numbering state, for reuse across future invoice tasks.
~/billing/ ... clients/index.json ... config.json # User's business data, templates ... series.json # Numbering per series
Periodically review the billing directory, restrict local file access, avoid storing unnecessary notes, and correct stale client or business details promptly.
Recurring invoice drafts or alerts may appear later based on stored subscription settings.
Recurring invoices introduce future scheduled behavior. The artifact limits this to automatic draft generation followed by user confirmation before finalization and sending.
On trigger day: 1. Generate draft automatically 2. Notify user ... 3. User confirms or edits 4. Finalize and send
Enable recurring invoices only when intended, keep recurring definitions current, and preserve the confirmation step before any invoice is finalized or sent.