Add Analytics

v0.1.0

Add Google Analytics 4 tracking to any project. Detects framework, adds tracking code, sets up events, and configures privacy settings.

1· 2.5k·7 current·7 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Add Google Analytics 4) align with the instructions: the SKILL.md only describes detecting the framework, inserting GA4 snippets, wiring events, and configuring consent. There are no unrelated environment variables, binaries, or installation steps requested.
Instruction Scope
The instructions tell the agent to scan the project repository (package.json, framework config files, src files, tsconfig, lockfiles) and to modify or create source files and env vars to add GA4. This is consistent with the skill's purpose but does mean the skill will read and change project files — the user should expect code modifications and review them. The instructions also add runtime code that will load scripts from googletagmanager.com (expected for GA4).
Install Mechanism
No install spec and no code files are included; this is instruction-only and does not download or install third-party code at install-time, which is the lowest-risk model for this kind of helper.
Credentials
The skill does not request environment variables, credentials, or config paths. Proposed changes in examples use public env var names (e.g., NEXT_PUBLIC_GA_MEASUREMENT_ID or VITE_GA_MEASUREMENT_ID) which are appropriate for front-end tracking and do not require secrets.
Persistence & Privilege
always is false and the skill does not request persistent privileges or modifications to other skills or system-wide settings. It only describes modifying project files within the repository (its intended scope).
Assessment
This skill appears to do what it says: it will read your repository to detect framework and then add or modify source files to insert GA4 tracking code. Before running it, (1) back up or run it on a feature branch so you can review changes; (2) confirm the Measurement ID is correct and that you own the analytics property; (3) be aware the inserted code will cause client browsers to load scripts from googletagmanager.com and send analytics data to Google — review privacy/consent requirements (GDPR/CCPA) and enable the --consent option if needed; (4) verify generated changes (env var names, injected snippets) to avoid leaking any private values. No credentials or external installs are requested by the skill itself.

Like a lobster shell, security has layers — review code before you run it.

latestvk97e7hrpqaxkfx29vfqkffnfj180ds9e

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments