CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bigquery-bigframes

Generates Python code using BigQuery DataFrames (BigFrames). Use by default for any Python data task involving BigQuery, including data processing, analysis, and machine learning. Don't use for SQL-first workflows or the google-cloud-bigquery client library — use bigquery-basics.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, mostly lean best-practices guide with executable code and specific API guidance, and clean one-level-deep references into a real bundle. The main gaps are minor: a concept-explaining intro line, a few topics lacking runnable snippets, and slightly awkward placement of the reference directory.

DimensionReasoningScore

Conciseness

The body is efficient bullet-style guidance with short, load-bearing rationales (e.g., "UDFs require extra resources and time to deploy"), and each bullet instructs rather than explains. Not 5 because the opening line "BigFrames is a Python library that lets you take advantage of BigQuery data processing by using familiar Python APIs" explains a concept Claude could look up and could be trimmed.

4 / 5

Actionability

Gives executable, specific guidance: runnable snippets for ordering mode ("bpd.options.bigquery.ordering_mode = 'partial'") and accessor preference, plus concrete methods ("peek(n)", ".dtypes", "model.to_gbq()", "bpd.read_gbq_model()"). Not 5 because several bullets (visualization, ARIMA Plus, hyperparameter tuning) give direction without runnable snippets; not 3 since what is present is executable code and specific API names, not pseudocode.

4 / 5

Workflow Clarity

This is a code-generation best-practices skill, not a multi-step destructive/batch workflow, so no validation loop is required; it does include an explicit checkpoint ("Schema Verification: Do not assume the schema of intermediate outputs. Proactively verify schemas using .dtypes") and per-topic unambiguous guidance (e.g., sort chronologically, split, then train). Not 5 because there is no explicit feedback/error-recovery loop and no sequencing across sections; not 3 because no risky operation lacks validation and the guidance is unambiguous.

4 / 5

Progressive Disclosure

All three referenced bundle files (references/attribution.md, linear_regression.md, logistic_regression.md) exist, are one level deep, and are annotated with one-line descriptions; the ~100-line body is appropriately sized for the main file. Not 5 because the "Reference Directory" is oddly nested under "Machine Learning" and only two ML topics have reference files while several other inlined topics (visualization, ARIMA Plus, PCA) could be offloaded; not 3 because structure and signaling are clearly good.

4 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capability, default trigger conditions, and explicit boundaries against the sibling bigquery-basics skill. Its only weaknesses are category-level action enumeration and slightly thin natural-keyword synonyms.

DimensionReasoningScore

Specificity

"Generates Python code using BigQuery DataFrames (BigFrames)" names the domain and lists several concrete task types ("data processing, analysis, and machine learning"), with only minor gaps (e.g., visualization/forecasting covered in the body are not named). Not 5 because the actions are enumerated at category level rather than the comprehensive, fully concrete list of the 5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Generates Python code using BigQuery DataFrames (BigFrames)") and when ("Use by default for any Python data task involving BigQuery"), with concrete negative triggers ("Don't use for SQL-first workflows or the google-cloud-bigquery client library"). This matches the 5 anchor's both-what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "Python data task", "BigQuery", "machine learning", "google-cloud-bigquery client library" — giving good keyword coverage. Not 5 because common variations like "pandas", "dataframe", or "BigFrames"-adjacent phrasings users might use are thin; not 3 because coverage clearly exceeds "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

The explicit exclusion clause ("Don't use for SQL-first workflows or the google-cloud-bigquery client library — use bigquery-basics") carves out a clear niche and actively routes conflicts to the sibling skill, matching the 5 anchor's minimal conflict risk with distinct triggers.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

google/skills

Path

skills/cloud/bigquery-bigframes/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.