QuickBooks

PassAudited by ClawScan on May 3, 2026.

Overview

This is a coherent QuickBooks integration, but it requires a Maton API key/OAuth connection and can change financial records, so it should be used only with careful approvals.

Install this only if you need QuickBooks accounting administration through Maton. Use a least-privileged QuickBooks account, protect `MATON_API_KEY`, always specify and verify the intended connection ID/company, start with read-only requests, and approve financial write or delete actions only after reviewing the exact endpoint, record, amount, and consequence.

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.

What this means

If misused, the skill could create, modify, or delete accounting records such as invoices, payments, bills, or customer records.

Why it was flagged

The skill can perform high-impact financial write actions, but it clearly discloses this and instructs the agent to require specific approval before changes.

Skill content
This integration can mutate accounting records — approve only specific write actions after checking the exact endpoint, account, resource ID, amounts, and consequence.
Recommendation

Use read-only requests first, verify the exact QuickBooks company and record IDs, and approve only specific write actions you understand.

What this means

Anyone or any agent workflow with the Maton API key may be able to access the connected QuickBooks resources permitted by the OAuth connection.

Why it was flagged

The skill requires a bearer API key and delegated QuickBooks OAuth access, which is expected for the integration but grants access to financial account data and actions.

Skill content
All requests require the Maton API key in the Authorization header: Authorization: Bearer $MATON_API_KEY
Recommendation

Use a least-privileged QuickBooks account, protect the Maton API key, avoid sharing logs containing headers, and revoke unused connections promptly.

What this means

Sensitive financial data may transit through Maton's API gateway as part of normal operation.

Why it was flagged

QuickBooks requests and responses pass through the Maton gateway. This is disclosed and purpose-aligned, but users should understand the third-party data path.

Skill content
The gateway proxies requests to `quickbooks.api.intuit.com` and the `:realmId` placeholder is automatically replaced with your company's realm ID from connection config.
Recommendation

Install only if you trust the Maton service for QuickBooks data, review its privacy/security posture, and use the `Maton-Connection` header to avoid sending actions to the wrong company.

What this means

It may be harder to independently verify the publisher, implementation, or support channel before connecting accounting data.

Why it was flagged

The registry does not provide source or homepage provenance. There is no code package to install, so this is not a direct execution risk, but it matters for a financial integration.

Skill content
Source: unknown; Homepage: none
Recommendation

Verify the owner and Maton service out-of-band before connecting a real QuickBooks company, especially for production accounting data.