Kaggle
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent Kaggle integration, but users should notice that it routes Kaggle API use through Maton and relies on Maton and Kaggle credentials.
This skill appears reasonable for Kaggle API access. Before installing, make sure you trust Maton to broker Kaggle requests, protect your MATON_API_KEY, connect only the Kaggle account you intend to use, and revoke the connection if you stop using the service.
Findings (2)
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.
Using the skill gives Maton-mediated access to Kaggle resources under the connected account.
The skill uses a Maton bearer token and asks the user to connect Kaggle credentials. This is expected for managed Kaggle access, but it is delegated account authority.
All requests require the Maton API key... Authorization: Bearer $MATON_API_KEY ... you'll need to provide your Kaggle username and API key
Only connect accounts you intend to use with this gateway, keep the Maton API key private, and revoke the Kaggle connection when no longer needed.
API requests and responses may pass through Maton's gateway, including operations involving private Kaggle resources if the user has access to them.
Kaggle API requests are routed through a Maton gateway rather than directly to Kaggle. This is disclosed and purpose-aligned, but it is an external data and credential boundary users should understand.
https://gateway.maton.ai/kaggle/{native-api-path} ... The gateway proxies requests to `api.kaggle.com` and automatically injects your credentials.Review Maton's trust and privacy posture before sending sensitive Kaggle requests or using private datasets through the gateway.