OPC Invoice Manager
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is a coherent local invoice-management assistant, with notable but purpose-aligned access to financial records and local helper scripts.
This appears suitable for local invoice management if you are comfortable letting the assistant read and update invoice/client records. Before installing, verify the source, use a dedicated invoices folder, keep backups, and review generated invoices, payment-status changes, and collection emails before sending or relying on them.
Findings (3)
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.
The assistant may inspect invoice records and, in other documented modes, help update invoice status such as paid, overdue, voided, or reissued.
The skill instructs the agent to run local Python helper scripts against the invoice directory. This is central to the invoice-tracking purpose, but local commands can read or update business records if used incorrectly.
Run: `python3 [skill_dir]/scripts/invoice_tracker.py --overdue --json [invoices_dir]`
Use a dedicated invoices directory, keep backups of invoice metadata, and review any generated invoice or payment-status change before relying on it.
Stale, incorrect, or overly broad local records could cause wrong invoice details, reminders, or dashboards to be generated.
The skill reuses persistent local contract and client profile data to generate invoices and collection outputs. That is expected for this purpose, but the data may include sensitive client, billing, tax, and payment information and can influence future outputs.
Auto-infer from contracts — If `contracts/INDEX.json` exists, pull: `counterparty_name`, `payment_terms_days`, `currency`, `contract_id` ... Auto-infer from client profiles — If `invoices/clients/{client-slug}.json` exists, pull defaults for currency, terms, tax, billing address, AP contact.Keep client profiles and contract indexes accurate, limit stored data to what is needed, and review inferred invoice details before sending anything to customers.
Users may have less assurance that the installed copy matches the intended project or a reviewed version.
The registry metadata does not identify a source or homepage, while the README separately documents manual installation from a GitHub repository. This is a provenance note rather than evidence of malicious behavior.
Source: unknown; Homepage: none
Install only from a trusted source, verify the repository or package path, and review updates before replacing the local skill.