google-reporting
v1.1.1Google Analytics 4 and Search Console readers — usage, indexing status, search performance, and sitemap health, via keyless service-account impersonation
By KaiLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install google-reporting for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install google-reporting@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/kai-tw/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/google-reporting/.
Plugin files
├── .claude-plugin/plugin.json└── skills/ga4/SKILL.md
Included Skills1
Google Analytics 4 reader for a GA4 property — activeUsers, sessions, engagement, and per-event counts, via keyless service-account impersonation. No key file, no OAuth consent screen, no env vars. This is a thin fetch layer only — it returns raw numbers. Turning usage data into roadmap/product judgment is a consuming project's own skill (e.g. a project-local "ga-triage"-style skill that anchors on that project's own event catalog and files backlog candidates). TRIGGER when: "/ga4", "check ga4", "check google analytics", "ga4 data", "active users", "ga4 events", "analytics numbers", "查一下 GA4", "查 google analytics", "使用者數據", "ga4 事件". NOT for: turning usage into product-roadmap candidates (that's a project-specific skill layered on top of this — see e.g. `ga-triage`); Search Console / SEO / indexing data (that's the sibling `gsc` skill in this same plugin — a different product, different script); writing GA4 config or creating events (read-only).
Plugin manifests1
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "google-reporting",
"version": "1.1.1",
"description": "Google Analytics 4 and Search Console readers — usage, indexing status, search performance, and sitemap health, via keyless service-account impersonation",
"author": {
"name": "Kai",
"url": "https://github.com/kai-tw"
},
"homepage": "https://github.com/kai-tw/claude-plugins/tree/main/plugins/google-reporting",
"license": "MIT",
"keywords": [
"google-analytics",
"ga4",
"seo",
"search-console",
"indexing",
"analytics",
"google"
],
"skills": [
"./skills/ga4",
"./skills/gsc"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[google-reporting on Agent Plugins Marketplace](https://pluginsmp.com/plugins/google-reporting)