bigquery-table-creator
Bigquery Table Creator - Auto-activating skill for GCP Skills. Triggers on: bigquery table creator, bigquery table creator Part of the GCP Skills skill category.
35
3%
Does it follow best practices?
Impact
93%
0.93xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/bigquery-table-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak, essentially just restating the skill name with no substantive information about capabilities, use cases, or trigger scenarios. It provides no actionable detail for Claude to determine when to select this skill over others, and the trigger terms are redundant duplicates of the skill name.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates BigQuery tables with schema definitions, partitioning, clustering, and access controls in Google Cloud Platform.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a BigQuery table, define a BQ schema, set up a dataset table, or configure table partitioning in Google Cloud.'
Remove the duplicate trigger term ('bigquery table creator' is listed twice) and expand with varied natural language phrases users might actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Bigquery Table Creator') but does not describe any concrete actions like creating schemas, defining partitions, setting up clustering, or specifying column types. It is essentially just a name repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name and provides no meaningful 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name and adds no useful context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'bigquery table creator' repeated twice. It misses natural user phrases like 'create a BigQuery table', 'BQ schema', 'define table schema', 'Google BigQuery', or 'dataset table'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'BigQuery' and 'table creator' provides some domain specificity that distinguishes it from generic skills, but the lack of detail about what specifically it does (vs. other BigQuery-related skills like querying or data loading) creates overlap risk within GCP skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual instructional content. It contains no BigQuery-specific knowledge—no SQL DDL examples, no CLI commands, no schema patterns, no partitioning/clustering guidance, and no validation steps. It would provide no value to Claude when attempting to help a user create a BigQuery table.
Suggestions
Add concrete, executable examples such as `CREATE TABLE` DDL statements, `bq mk` CLI commands, or Terraform resource definitions for BigQuery tables.
Include a clear workflow: define schema → choose partitioning/clustering → create table → validate with `bq show` or `SELECT` query → handle errors.
Add specific guidance on BigQuery-specific concerns like partition columns, clustering keys, time-travel, cost implications, and schema evolution patterns.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than providing actionable instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or code for creating BigQuery tables. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no SQL statements, no `bq` CLI commands, no Terraform configs, no API calls. The content only describes what it claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Creating a BigQuery table involves specific steps (schema definition, partitioning choices, dataset selection, etc.) and none are mentioned, let alone sequenced with validation checkpoints. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed guides, no examples file, and no links to schema templates or advanced configuration. The sections are just boilerplate headers with no substance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.