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
Quality
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill, and the redundant trigger terms add no value. The description needs a complete rewrite to be functional.
Suggestions
Add specific actions the skill performs, e.g., 'Creates BigQuery tables with schema definitions, partitioning, clustering, and expiration settings'
Add a 'Use when...' clause with natural trigger terms like 'create BigQuery table', 'new BQ table', 'define table schema', 'set up BigQuery dataset table'
Include common user phrases and file types, e.g., 'when user needs to create tables from CSV schemas, JSON definitions, or SQL DDL statements'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Bigquery Table Creator' without describing any concrete actions. It doesn't explain what creating a table involves (e.g., defining schemas, setting partitions, configuring clustering). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' clause just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('bigquery table creator' listed twice) and overly specific. Missing natural variations users would say like 'create BigQuery table', 'new BQ table', 'define table schema', or 'GCP table'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'BigQuery Table Creator' is somewhat specific to a particular GCP service, the lack of detail about what table creation entails could cause confusion with other BigQuery-related skills or general database 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 content is essentially a placeholder with no actual instructional value. It contains only meta-descriptions of what a skill should do without any concrete guidance on BigQuery table creation - no DDL examples, no schema patterns, no API calls, no partitioning/clustering guidance, and no validation steps.
Suggestions
Add executable DDL examples for common table creation patterns (e.g., partitioned tables, clustered tables, external tables)
Include concrete bq CLI commands and/or Python client code for creating tables programmatically
Provide a workflow with validation steps: schema definition -> DDL execution -> verification query
Add references to schema design patterns, partitioning strategies, and cost optimization considerations for BigQuery tables
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about BigQuery table creation. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for creating BigQuery tables. The entire content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Creating BigQuery tables involves specific steps (schema definition, partitioning decisions, clustering, DDL or API calls) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure pointing to detailed materials. No references to schema examples, DDL templates, or API documentation are provided. | 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
0c08951
- 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.