Google Analytics
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Google Analytics integration guide, but it relies on Maton-managed OAuth/API keys and can read or change Google Analytics settings.
Install only if you intend to use Maton as the OAuth/API gateway for Google Analytics. Before use, create your own Maton connection, verify the correct Google Analytics account/property, protect MATON_API_KEY, and avoid write/admin operations unless you explicitly approve them.
Findings (5)
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.
Anyone using the skill must trust Maton with the delegated Analytics connection and should protect the Maton API key.
The skill requires a Maton API key and delegated Google Analytics OAuth access, which is expected for the integration but grants account-level authority.
All requests require the Maton API key in the Authorization header: ... Authorization: Bearer $MATON_API_KEY
Use only a trusted Maton account, review granted Google permissions, keep the API key private, and revoke unused connections.
An agent using this skill could change Google Analytics configuration if the user asks it to configure resources.
The documented Admin API capability includes configuration-changing operations, which are purpose-aligned but higher impact than read-only reporting.
Admin API (manage accounts, properties, data streams)
Confirm the intended account, property, and exact change before running create, update, delete, or admin-management requests.
Analytics data and admin requests may be visible to or processed by the Maton gateway as part of normal operation.
Google Analytics requests flow through Maton's gateway, creating a third-party data boundary for Analytics queries, responses, and OAuth handling.
The gateway proxies requests to analyticsadmin.googleapis.com and analyticsdata.googleapis.com and automatically injects your OAuth token.
Review Maton's privacy and security posture before using this with sensitive Analytics properties.
A user or agent may copy the sample connection ID instead of using their own, causing failed requests or unintended connection selection.
The documentation includes a real-looking connection identifier instead of a placeholder. It is not shown to be a secret by itself, but it can confuse users or expose account-specific metadata if real.
"connection_id": "21fd90f9-5935-43cd-b6c8-bde9d915ca80"
Replace concrete connection IDs in examples with placeholders such as {connection_id} and verify the active connection before use.
Users have less registry-level information for verifying the publisher and service before granting OAuth access.
The skill relies on Maton-hosted services for authentication and API gateway behavior, but the registry metadata does not provide source or homepage provenance.
Source: unknown; Homepage: none
Verify the Maton service and publisher independently before connecting important Google Analytics accounts.