bigquery-view-generator
Bigquery View Generator - Auto-activating skill for GCP Skills. Triggers on: bigquery view generator, bigquery view generator Part of the GCP Skills skill category.
33
3%
Does it follow best practices?
Impact
83%
0.92xAverage 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-view-generator/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 restating the skill name without providing any meaningful detail about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly impossible for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates BigQuery SQL view definitions, creates or updates views in GCP datasets, and manages view dependencies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a BigQuery view, write SQL for a BQ view, define a Google Cloud BigQuery view, or work with .sql view files.'
Remove the duplicate trigger term ('bigquery view generator' is listed twice) and expand with natural variations users might say, such as 'BQ view', 'BigQuery SQL view', 'create view in BigQuery', 'GCP view definition'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Bigquery View Generator' but does not describe any concrete actions. There is no mention of what it actually does beyond the name itself—no actions like 'creates views', 'generates SQL', 'defines schemas', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explicit 'Use when...' clause, and the 'what' is essentially just the skill name restated without elaboration. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'bigquery view generator' repeated twice. There are no natural user keywords like 'BigQuery', 'SQL view', 'create view', 'BQ', 'dataset', or 'Google Cloud' that a user might naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'bigquery view' provides some domain specificity that narrows it to BigQuery views rather than general GCP or database work, but the lack of concrete actions and the vague 'GCP Skills' category could cause overlap with other GCP-related 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 an empty shell with no actual content about BigQuery view generation. It consists entirely of auto-generated boilerplate that describes what the skill would do without providing any actual instructions, code, SQL examples, or workflows. It fails on every dimension because it contains zero actionable information.
Suggestions
Add concrete SQL examples for creating BigQuery views (e.g., CREATE VIEW syntax, common patterns like aggregation views, materialized views, authorized views)
Include a step-by-step workflow for generating views: define source tables → write SQL → validate query → create view → verify access permissions
Add specific BigQuery CLI commands (e.g., `bq mk --use_legacy_sql=false --view 'SELECT ...' dataset.view_name`) and Terraform/gcloud configuration examples
Remove all boilerplate meta-content (Purpose, When to Use, Example Triggers sections) and replace with actual technical guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what triggers the skill and restates the title repeatedly but provides zero actual guidance on BigQuery view generation. Every token is wasted on meta-description rather than actionable content. | 1 / 3 |
Actionability | There are no concrete code examples, SQL snippets, commands, or specific instructions for generating BigQuery views. The content is entirely abstract and descriptive, offering no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but provides none. There are no sequences, validation checkpoints, or any process description for creating BigQuery views. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no meaningful structure. There are no references to detailed files, no examples section, and no navigation to deeper content. The sections that exist contain no useful information. | 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.