Imaging Data Commons
K-Dense-AI/scientific-agent-skills
Queries and downloads public cancer imaging data from NCI Imaging Data Commons.
Wire GA4 → BigQuery for unsampled, queryable event-level data.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ga4-bigquery-export --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export .claude/skills/ga4-bigquery-export && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ga4-bigquery-export" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export into .claude/skills/ga4-bigquery-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ga4-bigquery-export", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-exportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ga4-bigquery-export --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export .agents/skills/ga4-bigquery-export && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ga4-bigquery-export" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export into .agents/skills/ga4-bigquery-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ga4-bigquery-export", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ga4-bigquery-export --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export .cursor/skills/ga4-bigquery-export && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ga4-bigquery-export" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export into .cursor/skills/ga4-bigquery-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ga4-bigquery-export", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ga4-bigquery-export --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export .gemini/skills/ga4-bigquery-export && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ga4-bigquery-export" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export into .gemini/skills/ga4-bigquery-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ga4-bigquery-export", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ga4-bigquery-exportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export .github/skills/ga4-bigquery-export && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ga4-bigquery-export" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export into .github/skills/ga4-bigquery-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ga4-bigquery-export", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ga4-bigquery-export --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export .opencode/skills/ga4-bigquery-export && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ga4-bigquery-export" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export into .opencode/skills/ga4-bigquery-export/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ga4-bigquery-export", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ga4-bigquery-exportWire GA4 → BigQuery for unsampled, queryable event-level data.
Ga4 Bigquery Export is an agent skill from jeremylongshore/tons-of-skills-marketplace. Wire GA4 → BigQuery for unsampled, queryable event-level data. Covers the one-time export setup, the eventsYYYYMMDD table schema, partitioning + clustering, and the SQL patterns for the reports the Data API can't do well (true cohort retention, custom-event attribution, large date ranges). Trigger with "GA4 BigQuery", "GA4 to BQ", "event-level GA4 data", "unsampled GA4", "GA4 export setup", "GA4 SQL".
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code
It sits in Databases, covering Data warehousing and SQL. It works with Google Analytics, Google BigQuery, SQL and Google Cloud. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
Bash(bq:*)Bash(gcloud:*)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
bqgcloudFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
analytics.google.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Ga4 Bigquery Export loads about 2.8k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 1,008 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 1,008 words, ~2,793 tokens.
.claude/skills/ga4-bigquery-export/SKILL.md (or your agent's skills folder).The Data API is good but bounded — sampled past a threshold, capped at ~150 dimensions, no cohort joins. BigQuery export gives you the raw event stream as SQL-queryable tables, free at the standard GA4 tier (up to 1M events/day), with no sampling and full event payloads.
This skill: one-time setup, then the SQL recipes for what the Data API can't do well.
bq and gcloud CLIs authenticated to that project; use the service account created by ga4-auth-setup for unattended queries.In https://analytics.google.com/:
events_YYYYMMDD table per day, written ~24h after midnight. Fine for most reporting.events_intraday_YYYYMMDD table written ~near-real-time. Costs more, useful for hot ops dashboards.The first daily table lands within 24h. The first streaming table is near-immediate. After that you have a new events_YYYYMMDD every day forever, no maintenance needed.
PROJECT=your-gcp-project
DATASET=analytics_123456789 # auto-named after the property ID
bq ls "$PROJECT:$DATASET" 2>&1 | head -10
# Expect: events_YYYYMMDD tables + events_intraday_YYYYMMDD if streaming enabledIf you see no dataset, the link is configured but the first export hasn't fired yet — wait 24h.
The SA from ga4-auth-setup only has Data API access. For BQ queries, grant the same SA:
SA_EMAIL=ga4-reader@your-project.iam.gserviceaccount.com
gcloud projects add-iam-policy-binding "$PROJECT" \
--member="serviceAccount:$SA_EMAIL" \
--role="roles/bigquery.dataViewer"
gcloud projects add-iam-policy-binding "$PROJECT" \
--member="serviceAccount:$SA_EMAIL" \
--role="roles/bigquery.jobUser"dataViewer reads tables; jobUser lets the SA run queries (queries are jobs in BQ's model).
Every row in events_YYYYMMDD is one event. The schema is denormalized — user + session + event + page + device all flat in each row.
| Column | Type | Notes |
|---|---|---|
event_date | STRING | 'YYYYMMDD' |
event_timestamp | INT64 | Microseconds since epoch |
event_name | STRING | page_view, session_start, purchase, custom event names |
event_params | ARRAY<STRUCT<key, value>> | All event parameters; value is itself a union STRUCT (string_value, int_value, float_value, double_value) |
user_pseudo_id | STRING | GA4's cookie-based user ID (anonymous unless user_id is set) |
user_id | STRING | If you set user_id via gtag('set', {user_id: '...'}) |
user_properties | ARRAY<STRUCT<key, value>> | Same shape as event_params |
device.* | STRUCT | category / os / browser / model |
geo.* | STRUCT | country / region / city |
traffic_source.* | STRUCT | source / medium / campaign of FIRST session (not current) |
session_traffic_source_last_click.* | STRUCT | source / medium of CURRENT session — what you usually want |
ga_session_id (param) | INT64 | Pulled via (SELECT value.int_value FROM UNNEST(event_params) WHERE key='ga_session_id') |
ga_session_number (param) | INT64 | Same idiom — 1 = first session, 2 = second, etc. |
The event_params and user_properties arrays are the gnarly bit. Pulling a parameter requires UNNEST + filter. The idiom:
-- Pull the page_location for every page_view
SELECT
TIMESTAMP_MICROS(event_timestamp) AS ts,
(SELECT value.string_value FROM UNNEST(event_params) WHERE key = 'page_location') AS page,
user_pseudo_id
FROM `your-project.analytics_123456789.events_*`
WHERE _TABLE_SUFFIX BETWEEN '20260513' AND '20260520'
AND event_name = 'page_view'
LIMIT 100;_TABLE_SUFFIX BETWEEN '...' AND '...' is the canonical way to scan a date range across the wildcard table. Always set it — without a suffix filter, you query the entire history and pay for it.
The thing the Data API can't do cleanly:
WITH first_seen AS (
SELECT
user_pseudo_id,
DATE(MIN(TIMESTAMP_MICROS(event_timestamp))) AS first_date
FROM `your-project.analytics_123456789.events_*`
WHERE _TABLE_SUFFIX BETWEEN '20260401' AND '20260520'
GROUP BY user_pseudo_id
),
activity AS (
SELECT
user_pseudo_id,
DATE(TIMESTAMP_MICROS(event_timestamp)) AS active_date
FROM `your-project.analytics_123456789.events_*`
WHERE _TABLE_SUFFIX BETWEEN '20260401' AND '20260520'
GROUP BY user_pseudo_id, active_date
)
SELECT
DATE_TRUNC(f.first_date, WEEK) AS cohort_week,
DATE_DIFF(a.active_date, f.first_date, WEEK) AS weeks_since,
COUNT(DISTINCT a.user_pseudo_id) AS active_users
FROM first_seen f
JOIN activity a USING (user_pseudo_id)
GROUP BY cohort_week, weeks_since
ORDER BY cohort_week, weeks_since;Output: rows of (cohort_week, weeks_since, active_users). Pivot in your tool of choice for the classic triangle chart.
GA4's BQ export is event-rows, not session-rows. To reason about sessions, build the session table yourself:
WITH sessions AS (
SELECT
user_pseudo_id,
(SELECT value.int_value FROM UNNEST(event_params) WHERE key = 'ga_session_id') AS session_id,
MIN(TIMESTAMP_MICROS(event_timestamp)) AS session_start,
MAX(TIMESTAMP_MICROS(event_timestamp)) AS session_end,
COUNT(*) AS event_count,
COUNTIF(event_name = 'page_view') AS pageviews,
ANY_VALUE(device.category) AS device,
ANY_VALUE(geo.country) AS country,
ANY_VALUE(session_traffic_source_last_click.manual_campaign.source) AS source,
ANY_VALUE(session_traffic_source_last_click.manual_campaign.medium) AS medium,
FROM `your-project.analytics_123456789.events_*`
WHERE _TABLE_SUFFIX BETWEEN '20260513' AND '20260520'
GROUP BY user_pseudo_id, session_id
HAVING session_id IS NOT NULL
)
SELECT * FROM sessions
ORDER BY session_start DESC
LIMIT 100;You'd usually CREATE TABLE or CREATE MATERIALIZED VIEW over this — querying the events table directly every time is slow + expensive.
SELECT
(SELECT value.string_value FROM UNNEST(event_params) WHERE key = 'page_location') AS page,
session_traffic_source_last_click.manual_campaign.source AS source,
COUNT(*) AS pageviews,
COUNT(DISTINCT user_pseudo_id) AS users
FROM `your-project.analytics_123456789.events_*`
WHERE _TABLE_SUFFIX BETWEEN '20260513' AND '20260520'
AND event_name = 'page_view'
GROUP BY page, source
HAVING pageviews > 10 -- filter the long tail
ORDER BY pageviews DESC
LIMIT 50;BigQuery costs $5/TB scanned (first 1 TB/month free). What that translates to in practice:
| Scenario | ~TB / query |
|---|---|
| Small site, 1k events/day, 30-day window | < 1 GB |
| Medium site, 100k events/day, 30-day window | ~10 GB |
| Large site, 1M events/day, 30-day window | ~100 GB |
| Same scenarios but querying the full 14-month history | 12-15x the above |
Stay under the free tier with normal usage. Cost-saving patterns:
_TABLE_SUFFIX BETWEEN — don't scan all history if you only need 7 daysSELECT only the columns you need — BQ is columnar; selecting event_params array always reads the whole array even if you only want one parameter--dry-run before any new query to see TB scanned: bq query --dry_run --use_legacy_sql=false "SELECT ..."| Table prefix | When |
|---|---|
events_YYYYMMDD | Stable historical data. Use for reports, analysis. |
events_intraday_YYYYMMDD | "Today" data, near-realtime. Schema is identical, but rows may not be deduped yet. |
events_* (wildcard) | When the date range crosses both. BQ will scan both transparently. |
Today's data lives in events_intraday_TODAY; tomorrow it gets rolled into events_TODAY and the intraday table for today is dropped. So if you have a query that needs both stable history + today, use events_* and filter on _TABLE_SUFFIX.
After the first export window, the linked dataset contains daily events_YYYYMMDD tables (and optional intraday tables). The example queries return cohort, session, or page-level rows suitable for further analysis; every wildcard query includes a bounded _TABLE_SUFFIX range.
| Issue | Why |
|---|---|
| Numbers don't match the GA4 UI exactly | UI uses different identity-stitching for cross-device users; raw events are pre-stitching. Off by a few % is expected. |
event_params UNNEST returns NULL | The key doesn't exist on that event. Always wrap in (SELECT ... LIMIT 1) so missing-key events return NULL instead of erroring. |
| Query scans way more than expected | Missing _TABLE_SUFFIX filter, OR using events_* without a _TABLE_SUFFIX BETWEEN clause |
events_intraday_* has 2x the rows you'd expect | Intraday tables aren't deduped; the same event may appear twice if it was buffered + retried. The daily rollup dedupes. |
No user_id even though I set it on the front-end | user_id is the explicit identifier; user_pseudo_id is the auto-generated cookie ID. If user_id is consistently NULL, the gtag('set', {user_id: ...}) call is firing AFTER the event you're checking, or it's set on a property that the export doesn't pull. |
ga4-auth-setup — for the service account that queries BQga4-data-api-query — when you DON'T need event-level granularity (Data API is faster + cheaper for aggregates)ga4-common-reports — the Data API recipes that BQ supersedes© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Ga4 Bigquery Export next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ga4 Bigquery Export this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Imaging Data CommonsK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~7.8k | Automated safety check: Pass | MIT | |
| Bigquery Observabilitygoogle/skills | 21k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Bigquery Optimizationgoogle/skills | 21k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| dbt Snowflake to BigQuery Translatorgoogle/skills | 21k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Cxas Configurable DashboardsGoogleCloudPlatform/cxas-scrapi | 107 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
K-Dense-AI/scientific-agent-skills
Queries and downloads public cancer imaging data from NCI Imaging Data Commons.
google/skills
Provides data-retrieval best practices, tool selection guidance, and performant SQL query syntax for BigQuery telemetry across INFORMATIONSCHEMA, Cloud Monitoring, and the REST API.
google/skills
Provides workflows to optimize BigQuery environments (capacity planning, editions), storage assets (partitioning, clustering, storage lifecycles, billing models), and SQL queries.
google/skills
Translates Snowflake dbt SQL models into standardized BigQuery SQL, keeping Jinja constructs and tracking progress in a migration tasks file.
GoogleCloudPlatform/cxas-scrapi
Author, validate, and manage Contact Center AI (CCAI) Insights Configurable Dashboards.
sidequery/sidemantic
Answer analytical, KPI, metric, trend, cohort, and business-performance questions through a Sidemantic semantic layer.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Wire GA4 → BigQuery for unsampled, queryable event-level data. Ga4 Bigquery Export is an agent skill from jeremylongshore/tons-of-skills-marketplace. Wire GA4 → BigQuery for unsampled, queryable event-level data.
Ga4 Bigquery Export fits situations like: with GA4 BigQuery; event-level GA4 data; GA4 export setup.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a claude-code`. Or copy the skill folder (plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/ga4-bigquery-export in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a codex`. Or copy the skill folder (plugins/saas-packs/ga4-pack/skills/ga4-bigquery-export in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/ga4-bigquery-export in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ga4-bigquery-export -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ga4-bigquery-export, .gemini/skills/ga4-bigquery-export, .github/skills/ga4-bigquery-export and .opencode/skills/ga4-bigquery-export in your project.
Going by SKILL.md and its folder, Ga4 Bigquery Export needs the command-line tools its instructions call (bq and gcloud). Its frontmatter pre-approves these tools: Bash(bq:*), Bash(gcloud:*). Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 1 domain. As links in the text: analytics.google.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Ga4 Bigquery Export is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ga4 Bigquery Export: Imaging Data Commons (K-Dense-AI/scientific-agent-skills, 48k stars), Bigquery Observability (google/skills, 21k stars), Bigquery Optimization (google/skills, 21k stars) and dbt Snowflake to BigQuery Translator (google/skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.