Back to skill
Skillv1.0.1
ClawScan security
GA4 Analytics Toolkit · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 6, 2026, 11:15 PM
- Verdict
- benign
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's code and runtime instructions align with its stated GA4/Search Console/Indexing purpose, but it requires sensitive Google service-account credentials and the registry metadata omits those env requirements — review credentials and npm deps before use.
- Guidance
- This package appears to do what it claims, but it needs Google service‑account credentials (including a private key) and will write results to disk and install npm dependencies. Before installing: (1) verify you trust the skill source (source/homepage unspecified), (2) inspect scripts/package.json for any postinstall or unexpected lifecycle scripts, (3) create a least‑privilege Google service account limited to the GA4, Search Console, and Indexing scopes, (4) never commit the .env or private key to source control, and (5) consider running npm install in an isolated environment (container/VM) if you are unsure. If the registry metadata will be shown to others, ask the publisher to update required env var declarations to avoid confusion.
Review Dimensions
- Purpose & Capability
- noteThe skill implements GA4, Search Console, and Indexing API functionality and legitimately needs a Google service account, property ID, and site URL. However, the registry metadata declares no required env vars while SKILL.md and the code expect GA4_PROPERTY_ID, GA4_CLIENT_EMAIL, GA4_PRIVATE_KEY, and SEARCH_CONSOLE_SITE_URL — this mismatch is likely an oversight but should be corrected.
- Instruction Scope
- okRuntime instructions are explicit: run npm install in scripts/, create a .env with the service account values, call functions that call Google APIs, and auto-save JSON results to results/*. The code reads only those environment vars and writes results to local files; it does not call unexpected third‑party endpoints or attempt to read unrelated system files.
- Install Mechanism
- noteThe package is instruction-first with bundled source and a package.json; install is via 'cd scripts && npm install'. This is a normal install path but npm install will fetch third‑party dependencies and could run lifecycle scripts — review scripts and package.json before running npm install.
- Credentials
- noteRequested credentials (service account email and private key, GA4 property ID, Search Console site URL) are appropriate for the stated purpose. They are highly sensitive (private key) so the skill's need is proportional but you must protect those secrets and use a least‑privilege service account. The skill expects the private key in .env (dotenv) and replaces escaped newlines; ensure you store and handle the key securely.
- Persistence & Privilege
- okalways:false and model invocation is allowed (platform default). The skill auto-saves results to a local results/ directory it creates; it does not request persistent platform-wide privileges or modify other skills. Writing files to results/ is expected behavior for reporting tools.