Xero
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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.
An agent using this skill could change Xero business records such as invoices or payments if the user approves the action.
The skill can perform high-impact financial-account actions, but the artifact explicitly scopes the integration and requires user approval before create, update, or delete calls.
Access is scoped to contacts, invoices, payments, accounts, and run financial reports... All write operations require explicit user approval.
Before approving any write operation, verify the Xero connection, target resource, amount, and intended accounting effect.
Anyone or any agent with the MATON_API_KEY could make authorized Xero API requests through Maton within the connected account's permissions.
The skill relies on a Maton API key and delegated Xero OAuth access, which is expected for this integration but grants access to sensitive accounting data.
All requests require the Maton API key in the Authorization header... Maton proxies requests to `api.xero.com` and automatically injects your OAuth token and Xero-Tenant-Id header.
Use a trusted Maton account, keep the API key private, prefer least-privilege Xero authorization where available, and revoke unused connections.
Xero accounting requests and responses may pass through Maton, so sensitive financial information is exposed to that service as part of normal operation.
Financial API traffic is routed through a third-party gateway before reaching Xero. This is disclosed and central to the managed OAuth design, but users must trust that provider with request and response data.
Base URL: `https://api.maton.ai/xero/{native-api-path}` ... Maton proxies requests to `api.xero.com`Install only if you trust Maton to proxy Xero data, and avoid sending unnecessary sensitive information in requests.
Users have less registry-level provenance information for confirming who maintains the skill.
The registry metadata does not provide a source repository or homepage. Because this is an instruction-only skill with no code files or install script, this is a provenance note rather than a material execution concern.
Source: unknown; Homepage: none
Verify the publisher and Maton/Xero authorization flow before connecting a production accounting account.